Xen devel - Oct 2007 - HVM Windows - handover from qemu network drivers to PV network drivers

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? 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?

Thanks

James

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

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.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel