[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-bugs] [Bug 1247] Cascade failure when creating multiple domU's requires dom0 reboot
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1247 ------- Comment #1 from jeff@xxxxxxxxxxxxxxx 2008-05-08 14:02 ------- (In reply to comment #0) > For the last 10 days or so, I have been having problems where I get the > dreaded: > > Error: Device 0 (vif) could not be connected. Hotplug scripts not working. > > and once that happens, I must reboot the machine before I can start a domU > again. I'm not intimately familiar with the other bugs currently filed for the 'hotplug scripts not working' issue, so please excuse me if this doesn't apply or you already know of it - but in my experience, when I get that problem trying to 'xm create', it means that my udev daemon (on dom0) has gone AWOL. Simply doing an '/etc/init.d/udev start' to bring udev back up always seems to fix the problem for me. I suspect the same thing afflicts you given your mention of rebooting fixing the problem. While this is obviously not a great state of affairs, running the udev init script to restart udev is clearly a better solution than a physical restart. I have not noticed any issues with currently-running domUs when this issue comes up, FWIW: they don't hiccup or have any other problems. The problem seems isolated to the creation of new domU processes only. Hope this helps somewhat... -- Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. _______________________________________________ Xen-bugs mailing list Xen-bugs@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-bugs
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |