From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Biggadike Subject: Re: [PATCH][RFC] vmchannel a data channel between host and guest. Date: Wed, 15 Oct 2008 07:18:52 -0700 Message-ID: <20081015141852.GA19554@vmware.com> References: <20081012124534.GK11435@redhat.com> <48F39443.4070203@codemonkey.ws> <20081014090540.GB13153@redhat.com> <48F4A3B8.8050603@us.ibm.com> <20081014175900.GA18344@redhat.com> <48F4E1F3.3050606@codemonkey.ws> <20081015125837.GQ11435@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Anthony Liguori , "kvm@vger.kernel.org" , Rusty Russell , virtualization , Zach Amsden , Anupam Chanda To: Gleb Natapov Return-path: Received: from smtp-outbound-2.vmware.com ([65.115.85.73]:53784 "EHLO smtp-outbound-2.vmware.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751815AbYJOOS3 (ORCPT ); Wed, 15 Oct 2008 10:18:29 -0400 Content-Disposition: inline In-Reply-To: <20081015125837.GQ11435@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Gleb Natapov 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. The link you referenced was experimental and is actually now deprecated in favor of the sockets interface.