From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LLTd6-0005M3-Te for qemu-devel@nongnu.org; Fri, 09 Jan 2009 21:31:16 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LLTd6-0005Kr-DH for qemu-devel@nongnu.org; Fri, 09 Jan 2009 21:31:16 -0500 Received: from [199.232.76.173] (port=42801 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LLTd6-0005Kj-2q for qemu-devel@nongnu.org; Fri, 09 Jan 2009 21:31:16 -0500 Received: from mail2.shareable.org ([80.68.89.115]:37850) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LLTd5-0002cb-9X for qemu-devel@nongnu.org; Fri, 09 Jan 2009 21:31:15 -0500 Received: from jamie by mail2.shareable.org with local (Exim 4.63) (envelope-from ) id 1LLTd4-0001lU-5y for qemu-devel@nongnu.org; Sat, 10 Jan 2009 02:31:14 +0000 Date: Sat, 10 Jan 2009 02:31:14 +0000 From: Jamie Lokier Subject: Re: [Qemu-devel] [PATCH] mark nic as trusted Message-ID: <20090110023113.GL1972@shareable.org> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49668B91.3000705@codemonkey.ws> 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 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. > >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