From my experience with Gentoo / Xen3, the hotplug dependency is not optional, as it currently stands. I installed xen-3 from the xen-3.0.0-r2 ebuild on a new system running on a 64-bit Pentium D. Xen compiled correctly, and the xen daemon would start, but 'xm create' would fail to create new domains, giving "Error: Device 0 (vif) could not be connected. Hotplug scripts not working." After finding this thread, http://www.nabble.com/Xen-Starting-DomainU:Error:-Device-0-(vif)-could-not-be-connected.-Hotplug-scripts-not-working-t966265.html I emerged hotplug (which also installed pciutils and usbutils), then unmerged and re-emerged xen. After a restart, Xen was able to create domUs correctly. As a sidenote: I was, in one instance, able to get a domU to start before installing hotplug, but it required some manual monkeying around with the brctl bridging that I was not able to reproduce consistently. Cheers, -- Travis
As another data point, I can consistently reproduce the error message even with hotplug installed. Procedure: (From a system started without Xend running) # /etc/init.d/xend start # xm create foo [works properly] # xm shutdown foo # /etc/init.d/xend stop # cat /var/run/xenstore.pid | xargs kill # cat /var/run/xenconsoled.pid | xargs kill # /etc/init.d/xend start # xm create foo Using config file "foo". Error: Device 0 (vif) could not be connected. Hotplug scripts not working. Cheers, -- Travis
Do you still have this problem? The xen ebuild has a DEPEND on udev||hotplug. The udev rules are in xen-backend.rules - that should be enough to for any udev system. Did you etc-update/dispatch-conf after emerging? The udev maintainer has stated that hotplug backward compatibility will be going away soon, so the udev rules are the only way to ensure future compatibility.
Closing. Please reopen if you still see problems with xen-3.0.2.
