HVM虚拟机的tap和vif网卡

http://asearcher.info/index.php/hvm%E8%99%9A%E6%8B%9F%E6%9C%BA%E7%9A%84tap%E5%92%8Cvif%E7%BD%91%E5%8D%A1/

PV虚机只有一个vifX.N，而HVM虚机不安装PV Driver的时候会有两个网络接口vifX.N和tapX.N，而且实际上使用的是tapX.N。HVM虚机安装PV Driver并重启后，tapX.N会消失，使用vifX.N（若不重启还是使用tapX.N）

tap interfaces -> qemu-emulated NICs (realtek model by default), used 
when no PV drivers installed (using OS’ own driver for that model) 
vif interfaces (the one that you can rename) -> xen network frontend 
NICs, used when you have PV drivers installed (like GPLPV, 
http://meadowcourt.org/downloads/) 

the vif is a virtual interface that works with pv drivers in domU.  The tap is a Qemu interface that is used with HVMs that don’t have pv drivers.  So, if you start a HVM domU, you’ll
have the vif that Xen creates and the tap that Qemu creates, if pv drivers are available, then once they are loaded Domu uses them and the tap goes away, but if not then both remain, but only the tap interface is being used.  Obviously, if you need more detailed explaination, then I’m of no further use.:)

关于pvdriver：

linux pvdriver：

http://wiki.xen.org/wiki/Xen_Linux_PV_on_HVM_drivers

windows pvdriver：

http://hi.baidu.com/bwarkkntslbdnwd/item/5c15a0c695095752bdef6984

http://wiki.univention.de/index.php?title=Installing-signed-GPLPV-drivers