Hmm, no, seems to be a missing hotplug event.

Sticked some printk's into the net backend, looks like a xenbus issue:
domU boot with broken network:
 netback_probe: add backend watch
 netback_probe: add frontend watch
 netback_probe: done
 frontend_changed: called
 frontend_changed: called
 frontend_changed: called
 frontend_changed: called
domU boot with working network:
 netback_probe: add backend watch
 netback_probe: add frontend watch
 netback_probe: done
 backend_changed: called
 backend_changed: hotplug online
 netback_hotplug: called
 frontend_changed: called
 frontend_changed: called
 device vif2.0 entered promiscuous mode
 xenbr0: port 3(vif2.0) entering learning state
 xenbr0: topology change detected, propagating
 xenbr0: port 3(vif2.0) entering forwarding state
 frontend_changed: called
 frontend_changed: called
 frontend_changed: called
Note that backend_changed is never called in the first case.
cheers,
 Gerd
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel