Hey,
I've been searching this for quite a while now, and am just curious, why did the VMCI module name end up as "vmw_vmci", but the VSOCK module became "vsock" (same name as the original Workstation bundled one).
Thanks for your time,
Poloisfej
I forwarded your question on to our vsock/vmci experts, and they came back with the answer: vsock is a hypervisor-independent interface. vmci is a VMware-specific interface which is used as a transport for vsock.
Hence vsock has no "vmw_" prefix, but vmw_vmci does.
I hope this is a satisfactory explanation. It cleared things up for me.
Cheers
--
Darius
I forwarded your question on to our vsock/vmci experts, and they came back with the answer: vsock is a hypervisor-independent interface. vmci is a VMware-specific interface which is used as a transport for vsock.
Hence vsock has no "vmw_" prefix, but vmw_vmci does.
I hope this is a satisfactory explanation. It cleared things up for me.
Cheers
--
Darius
dariusd Fantastic, thank-you.