[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] HVM Windows - handover from qemu network drivers to PV network drivers


  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
  • Date: Sat, 6 Oct 2007 19:49:58 +1000
  • Delivery-date: Sat, 06 Oct 2007 02:50:40 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcgH/kHjXkSMj1y7TbSOVMzkAIMGSg==
  • Thread-topic: 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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.