[Xen-devel] HVM networking in Xen 3.4-rc3

[Gary Grebus <ggrebus@xxxxxxxxxxxxxxx>]

I'm trying to understand how networking is intended to work for HVM
domains in Xen 3.4-rc3.  My domain config file contains:

vif = [ 'type=ioemu, mac=00:16:3e:5b:f8:ed, bridge=eth2' ] 

and the bridge is correctly configured on eth2.  But the xm create
command gets hung waiting for something to happen with the vif, and
eventually fails with:

Error: Device 0 (vif) could not be connected. Hotplug scripts not
working.

xend.log shows it's waiting for something to be written to xenstore:

[2009-04-28 15:33:37 5592] DEBUG (XendDomainInfo:1708) 
XendDomainInfo.handleShutdownWatch
[2009-04-28 15:33:37 5592] DEBUG (DevController:139) Waiting for devices vif.
[2009-04-28 15:33:37 5592] DEBUG (DevController:144) Waiting for 0.
[2009-04-28 15:33:37 5592] DEBUG (DevController:629) hotplugStatusCallback 
/local/domain/0/backend/vif/4/0/hotplug-status.

which seems to be related to the udev hotplug rules.

But what happens with the vif is that qemu has
invoked /etc/xen/qemu-ifup, and that has added the tap device to the
bridge:

# brctl show                                           
bridge name     bridge id               STP enabled     interfaces              
eth2            8000.000e0cb1a72d       no              peth2                   
                                                        tap4.0                  

Is qemu supposed to be involved in the hotplug mechanism, or is there
something else I'm missing?
If modify qemu-ifup to write a value for the xenstore key, then the
domain finishes booting and the network works.

Thanks,
        Gary
-- 
Gary Grebus
Virtual Iron Software, Inc.



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