From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LL4Gb-00007d-7E for qemu-devel@nongnu.org; Thu, 08 Jan 2009 18:26:21 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LL4Ga-00006P-9n for qemu-devel@nongnu.org; Thu, 08 Jan 2009 18:26:20 -0500 Received: from [199.232.76.173] (port=42524 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LL4Ga-000067-2h for qemu-devel@nongnu.org; Thu, 08 Jan 2009 18:26:20 -0500 Received: from yx-out-1718.google.com ([74.125.44.155]:20678) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LL4GZ-0005uQ-Nb for qemu-devel@nongnu.org; Thu, 08 Jan 2009 18:26:19 -0500 Received: by yx-out-1718.google.com with SMTP id 3so3408407yxi.82 for ; Thu, 08 Jan 2009 15:26:19 -0800 (PST) Message-ID: <49668B91.3000705@codemonkey.ws> Date: Thu, 08 Jan 2009 17:26:09 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] mark nic as trusted References: <4964D98B.6030404@codemonkey.ws> <20090107165050.GI3267@redhat.com> <4964EC2B.1080406@codemonkey.ws> <4964EC55.4000507@codemonkey.ws> <20090107184103.GA19406@redhat.com> <496501CD.8060202@codemonkey.ws> <20090107194633.GB19406@redhat.com> <49665AE7.3000708@codemonkey.ws> <20090108212652.GB22504@redhat.com> <49667330.5070001@codemonkey.ws> <20090108224942.GA12848@shareable.org> In-Reply-To: <20090108224942.GA12848@shareable.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Jamie Lokier wrote: > Anthony Liguori wrote: > >> Are we going to have a standard way of doing this in Linux distros such >> that these nics are treated differently from other nics? Have we gotten >> the appropriate distro folks to agree to this? >> > > That wouldn't work for older distros and Windows anyway. But you > might reasonably want to run apps doing guest-host communication on > older guest distros too, simply as an app, not requiring guest > customisation. > That's probably going to be difficult. > Is there some way to mark a PCI device so it will be ignored at boot > time generically? No. > Changing the PCI ID will do that for all guests, > but is it then feasible for the vmchannel guest admin software to bind > a NIC driver to a non-standard PCI ID, on the major OSes? > I don't see how changing the PCI ID (I presume you mean vendor/device ID?) would help. > Suppose you start a guest with two "trusted" nics, because you want to > run two unrelated vmchannel-using admin apps. How does each app know > which nic to use - or do they share it? > Unrelated vmchannel apps will use different ports on the same nic. There will only ever be one trusted nic. > As the guest OS's TCP is being used, what do you do about IP address > space conflicts? > The user can choose what address is used for the host. > Perhaps vmchannel will only use IPv6, so it can confidently pick a > unique link-local address? > slirp only supports IPv4. Regards, Anthony Liguori > -- Jamie > > >