From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Edmondson Subject: Re: HVM Windows - handover from qemu network drivers to PV network drivers Date: Mon, 8 Oct 2007 08:23:54 +0100 Message-ID: <20071008072354.GP1326@enoexec.uk.sun.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: James Harper Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Sat, Oct 06, 2007 at 07:49:58PM +1000, James Harper wrote: > If I understand correctly, a HVM domain's network adapter gets a > tapX device created for it in Dom0 for qemu to talk to, and a vifY.Z > device for the PV drivers (which probably aren't there) to talk to. > > How can I stop the qemu code creating the virtual Realtek driver? Set the 'type' of the vif to 'ioemu'. > What will happen if I try and use PV and Realtek drivers at the same > time? Will the Realtek driver just talk to the tapX interface and > the PV drivers to the vifY.Z interface, and there will be no > problems? They should be connected up that way, yes. Though, perhaps they will end up with the same MAC address, which will cause other oddities.