[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-bugs] [Bug 392] domU cannot start: Device 0 (vif) could not be connected
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=392 ewan@xxxxxxxxxxxxx changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From ewan@xxxxxxxxxxxxx 2005-11-16 10:54 ------- Fixed, changeset 7814:a064c5804eae. Note that the message "Hotplug scripts not working" could refer to any number of failures. The bug that is fixed is a race condition, characterised by the call to hotplugStatus (now renamed hotplugStatusCallback) being logged immediately after the exception is thrown by waitForDevice. This behaviour is exhibited by the final set of logs given here. -- 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 |