From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LLiVu-0003eR-3N for qemu-devel@nongnu.org; Sat, 10 Jan 2009 13:24:50 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LLiVs-0003dl-Dh for qemu-devel@nongnu.org; Sat, 10 Jan 2009 13:24:49 -0500 Received: from [199.232.76.173] (port=44346 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LLiVs-0003df-8N for qemu-devel@nongnu.org; Sat, 10 Jan 2009 13:24:48 -0500 Received: from yw-out-1718.google.com ([74.125.46.155]:5365) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LLiVs-0004V4-08 for qemu-devel@nongnu.org; Sat, 10 Jan 2009 13:24:48 -0500 Received: by yw-out-1718.google.com with SMTP id 6so3764328ywa.82 for ; Sat, 10 Jan 2009 10:24:47 -0800 (PST) Message-ID: <4968E7E7.10209@codemonkey.ws> Date: Sat, 10 Jan 2009 12:24:39 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] mark nic as trusted References: <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> <49668B91.3000705@codemonkey.ws> <20090110023113.GL1972@shareable.org> In-Reply-To: <20090110023113.GL1972@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: > >>> 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. >> > > It would stop the OS from loading a NIC driver for it. > > Then later, then vmchannel-using guest app would force the OS to load > a NIC driver for the alternative PCI ID. E.g. by loading a module on > Linux with an alternative name and some module arguments. It's > probably not feasible without changes to OSes. > It isn't. Drivers don't work that way. Regards, Anthony Liguori >>> 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. >> > > So the vmchannel will need some guest-specific configuration before > the guest-host apps work? (And I don't mean OS-version-specific, but > specific to individual guest configs?) > > -- Jamie > > >