http://bugzilla.novell.com/show_bug.cgi?id=618678 http://bugzilla.novell.com/show_bug.cgi?id=618678#c2 Harald Koenig <koenig@linux.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|koenig@linux.de | --- Comment #2 from Harald Koenig <koenig@linux.de> 2010-07-01 16:27:50 UTC --- (In reply to comment #1)
Getting xenstore's view (utility xenstore-ls) on both the corresponding frontends' and backends' states would possibly shed some light on this - the
I have one full xenstore dump which I took after all domUs have been shut down. only dom0 was still running, but xenstore showed all the machines which have been running before. one note about xenstore: I'm not using xenstore myself (no "xm new foo"), all domUs are started via config file either in /etc/init.d/xendomains or with "xm create foo", so I'm a bit surprised to find all the domU info in xenstore *after* all those domUs are shut down ?! I'll attach that dump..
driver terminates those threads when the devices get disconnected (hinting at some failure path [in tools or kernel] doing insufficient cleanup).
The kernel side code didn't change in quite a while - did you observe similar problems with earlier versions?
I'm afraid it'll be difficult for us to do anything if the issue doesn't re-occur for you.
it does reoccur 100% for me, right now xen 4.0 with 11.3 is more or less unusable: whenever the first domU gets shut down or crases it's not possible anymore to start any new domU -- so far I only can reboot the dom0 :-( now I did a new test: no iscsi but one single PVM domU being started with one disk image as local file. start and shutdown workds fine, and the "blkback" kernel thread vanished. but still it's not possible to start a new domU! with identical config file I get # time xm cre -c os-centos5 Using config file "./os-centos5". # Error: Device 0 (vif) could not be connected. Hotplug scripts not working. so I again commented out the "vif=..." def only to get this (both times after 100 secs timeout) # xm cre -c os-centos5 Using config file "./os-centos5". # Error: Device 768 (vbd) could not be connected. Hotplug scripts not working. so I have to reboot again... -- next/last "single domU" test will use a 64bit suse 11.1 domU instead of cenots, just in case you want to argue... -- so stay tuned;-) now I'm no longer sure if the remaining blkback threads are the real problem, or just one more symtom of a even bigger problem:-( -- 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.