From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MQb0n-0005AS-U4 for qemu-devel@nongnu.org; Tue, 14 Jul 2009 01:57:10 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MQb0i-00056W-Ne for qemu-devel@nongnu.org; Tue, 14 Jul 2009 01:57:08 -0400 Received: from [199.232.76.173] (port=51044 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MQb0i-000567-B8 for qemu-devel@nongnu.org; Tue, 14 Jul 2009 01:57:04 -0400 Received: from mx2.redhat.com ([66.187.237.31]:33872) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MQb0h-00061Q-QZ for qemu-devel@nongnu.org; Tue, 14 Jul 2009 01:57:04 -0400 Date: Tue, 14 Jul 2009 06:54:45 +0100 From: "Richard W.M. Jones" Subject: Re: [Qemu-devel] bidirectional data exchange between guest and host without network Message-ID: <20090714055445.GA27551@amd.home.annexia.org> References: <20090707090213.GB5690@shareable.org> <53352.89.3.148.243.1246972290.squirrel@webmail.aql.fr> <20090707141204.GL15751@csclub.uwaterloo.ca> <20090707143925.GA14392@shareable.org> <42816.89.3.148.243.1247047400.squirrel@webmail.aql.fr> <20090708135722.GB21508@shareable.org> <42331.89.3.148.243.1247125873.squirrel@webmail.aql.fr> <20090711000400.GG30322@shareable.org> <20090712090220.GA17003@amd.home.annexia.org> <20090713223832.GD28136@shareable.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090713223832.GD28136@shareable.org> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jamie Lokier Cc: Lennart Sorensen , Anthony Lannuzel , qemu-devel@nongnu.org, Paul Brook On Mon, Jul 13, 2009 at 11:38:32PM +0100, Jamie Lokier wrote: > Richard W.M. Jones wrote: > > There is no IPv4 address you can give to the new interface which won't > > have the potential to conflict with some other IPv4 address already in > > use. Extra network devices require special handling in firewall rules > > and changes to the configuration of every network daemon in the > > system. > > A network interface with no IPv4 or IPv6 addresses assigned would > avoid most daemon problems. Using a non-ethernet MAC type and > point-to-point would probably avoid the rest, even routing daemons, > NetworkManager and the like. Use raw sockets over the interfaces. Can you give a precise description of how to configure this with qemu? > > While it's possible to configure the guest specially to avoid this, > > that doesn't look much like our promise to run any vanilla guest as a > > virtual machine. > > I don't see how "any vanilla guest" can use vmchannel, since it > requires specific kernel support doesn't it, and therefore the guest > tools can only use vmchannel on new guest kernels built for it? Point taken, but a vanilla guest + a support package, as with VMWare Tools or Linux fullvirt + virtio drivers. Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://et.redhat.com/~rjones/libguestfs/ See what it can do: http://et.redhat.com/~rjones/libguestfs/recipes.html