http://bugzilla.novell.com/show_bug.cgi?id=618678 http://bugzilla.novell.com/show_bug.cgi?id=618678#c11 James Fehlig <jfehlig@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |koenig@linux.de --- Comment #11 from James Fehlig <jfehlig@novell.com> 2010-07-02 17:20:58 UTC --- (In reply to comment #10)
can you reproduce that either (1) or (2) will lock you dom0 too ?
In each of these cases do you have a vif device that has not been released by netbk? I.e. do you have a /sys/devices/xen-backend/vif-X-Y? I think you are just hitting failure cases (different bugs) that cause netbk to not cleanup properly. Once netbk is in this state, further domUs cannot be started until a dom0 reboot. As mentioned in comment #8, I'm able to get netbk in this state by doing 'xm save' or 'xm destroy' on a domU. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.