Description of problem:
Running 'xm reboot -a' may result in some DomUs not being
rebooted, and others being in an inaccessible state.
Version-Release number of selected component (if applicable):
Most of the time.
Steps to Reproduce:
1. Start several pv guests.
2. run 'xm reboot -a'
Chaos. After the attempted reboot of all guest domains, some (or
all) of the domains will not be restarted. Running 'xm list'
shows something like:
# xm list
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 444 1 r----- 119.9
Zombie-rhel52-test 9 256 1 ------ 5.0
Zombie-rhel52-test 10 256 1 ----c- 0.2
Joy and harmony. All guests should restart successfully.
It is reported that this worked fine in xen-3.0.3-64.el5_2.3, but
is a problem with xen-3.0.3-64.el5_2.9 as well as the latest
version in RHEL 5.4 (xen-xen-3.0.3-94.el5). I have verified the
problem with xen-3.0.3-80.el5.
I suspect this could be caused by bug 518104, I'll prepare testing packages to check if my suspicion is right...
Could you please try the packages at http://people.redhat.com/jdenemar/xen/bz522274/ to see if that fixes your issue?
Great, thank you very much for the testing which confirms that this bug is solved by patches for bug 513604 and bug 518104. I'm going to close this bug as a duplicate of the latter (although both of them are most likely needed). Both BZs are nominated for Z-stream, so once they are approved, built and tested by QA, you should be able to get them as an update.
*** This bug has been marked as a duplicate of bug 518104 ***
This bug was closed during 5.5 development and it's being removed from the internal tracking bugs (which are now for 5.6).