RE: [PATCH] vsock: only load vmci transport on VMware hypervisor by default
From: Dexuan Cui <decui@microsoft.com>
Date: 2017-08-29 02:36:51
Also in:
lkml
From: Dexuan Cui <decui@microsoft.com>
Date: 2017-08-29 02:36:51
Also in:
lkml
From: Dexuan Cui Sent: Tuesday, August 22, 2017 21:21quoted
... ... The only problem here would be the potential for a guest and a host apptoquoted
have a conflict wrt port numbers, even though they would be able to operate fine, if restricted to their appropriate transport. Thanks, JorgenHi Jorgen, Stefan, Thank you for the detailed analysis! You have a much better understanding than me about the complex scenarios. Can you please work out a patch? :-)
Hi Jorgen, Stefan, May I know your plan for this?
IMO Linux driver of Hyper-V sockets is the simplest case, as we only have the "to host" option (the host side driver of Hyper-V sockets runs on Windows kernel and I don't think the other hypervisors emulate the full Hyper-V VMBus 4.0, which is required to support Hyper-V sockets). -- Dexuan
Thanks, -- Dexuan