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

[Xen-users] TAP adapter created for windows domU but not linux?

  • To: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Beasley, Julien" <Julien.Beasley@xxxxxxx>
  • Date: Fri, 26 Aug 2011 17:35:13 -0500
  • Accept-language: en-US
  • Acceptlanguage: en-US
  • Delivery-date: Fri, 26 Aug 2011 15:37:21 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcxkQAzgT3LfDPWdRaGSqKU+Kqpozw==
  • Thread-topic: TAP adapter created for windows domU but not linux?



I have a dom0 running in SuSE. My first domU is  also suse, and I noticed after running ifconfig that a vif1.0 entry showed up in ifconfig. This is what I expected after reading the Xen networking wiki page. My second domU is windows 7. I noticed when running ifconfig that vif2.0 entry was created, as expected. But, there is also a tap2.0 entry. Why is this created for windows and not linux? I’ve tried to look for documentation but I could not find a reference to this in the xen networking page (http://wiki.xensource.com/xenwiki/XenNetworking). Could anyone help clarify why tap2.0 is created, and why only for windows domU and not linux domU?





Xen-users mailing list



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