Gleb Natapov <gleb@xxxxxxxxxx> wrote: > On Wed, Oct 15, 2008 at 07:18:52AM -0700, Andrew Biggadike wrote: > > Gleb Natapov <gleb@xxxxxxxxxx> wrote: > > > > Of course, you should also take a look at VMware's VMCI. If we're going > > > > to have a socket interface, if we can have a compatible userspace > > > > interface, that would probably be a good thing. > > > > > > I looked at what I could find about VMCI (http://pubs.vmware.com/vmci-sdk/index.html). > > > > I believe Anthony intended for you to look at the sockets interface to > > VMCI: http://www.vmware.com/pdf/ws65_s2_vmci_sockets.pdf. > > > Using VMCI socket requires loading kernel module in a guest and in a host. > Is this correct? Yes, any context (in VMCI terms) that wants to allow for VMCI Socket endpoints needs both the vmci and the vsock kernel modules loaded. In case you're asking because you're going to try it out, note that our currently released version of VMCI Sockets (with Workstation 6.5) does not yet support SOCK_STREAM on the host, just guests. That gets a lot of people at the moment. _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
