Red Hat Bugzilla – Bug 149014
xend stops responding after xm destroy
Last modified: 2007-11-30 17:11:00 EST
Description of problem:
If I destroy a domain with xm destroy, a subsequent xm list command will hang.
Sometimes it is necessary to use xm destroy, because xm shutdown doesn't always
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. xm create -c foo
2. CTRL+] to detach from domain foo
3. xm destroy foo
4. xm list
xm list hangs
xm list should list domains
All kernels used are the latest kernels (2.6.10-1.1142_FC4) from fedora
development, with my floating-point-workaround patch applied.
Sometimes, service xend restart doesn't make xend work again either, so I have
to reboot the machine.
I have seen this bug too, but it seems to have gone away with
xen-2-20050222, which should be in rawhide in a few days. Please move
this bug back to ASSIGNED state if it pops up again in the future.