[Xen-users] qemu-ifup script not called in Xen 4.2-unstable

["Michael A. Collins" <mike.a.collins@xxxxxxxxxxx>]

Iâve seen where this has been referred to out on the web, but never saw the 
reasoning.  I am running xen-unstable on a couple of boxes and have a single 
HVM Windows 2008 64bit domU.  I have noticed that a tap device is added to my 
bridge, which is openvswitch, but I don't think that the device is real.  I 
can't see it in an ip link.  The domU works as far as the network goes, but I 
don't understand how it gets added to by bridge.  I've gone over the scripts, 
but I haven't seen anything that points itself out.  Is the tap device even 
needed anymore?  Also, I do see this in my dmesg:
 [ 7288.966168] device vif4.0 entered promiscuous mode
[ 7288.976406] ADDRCONF(NETDEV_UP): vif4.0: link is not ready
[ 7289.206650] tun: Universal TUN/TAP device driver, 1.6
[ 7289.206654] tun: (C) 1999-2004 Max Krasnyansky <maxk@xxxxxxxxxxxx>
[ 7289.363726] device tap4.0 entered promiscuous mode
[ 7299.442069] tap4.0: no IPv6 routers present
[ 7301.478366] xen-blkback:ring-ref 16383, event-channel 7, protocol 1 
(unspecified, assuming native)
[ 7307.500449] ADDRCONF(NETDEV_CHANGE): vif4.0: link becomes ready
[ 7318.370076] vif4.0: no IPv6 routers present


It sure seems like a tap device is created, but why does it disappear?  I am 
using GPLPV drivers, does the xennet driver write something to the xenstore 
that causes Xen to destroy the tap device?
Thanks
Mike


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