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

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

On Fri, Aug 26, 2011 at 05:35:13PM -0500, Beasley, Julien wrote:
>    Hello,
>    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
>    ([1]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?

tap devices are created by Xen qemu-dm for *emulated* virtual nics,
so when you run Windows as Xen HVM (fully virtualized/emulated) VM,
you get realtek or intel emulated vnic in the VM, and thus you get tap device 
in dom0.

-- Pasi

Xen-users mailing list



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