Description of problem:
Create the guest, then destroy it immediately, qemu-dm is usually left not killed, causing later created guests fail to respond on vnc.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. xm create domU
2. after 'xm create' returns, xm destroy domU immediately.
3. ps -ef
qemu-dm is still there.
no qemu-dm running.
Host is AMD with 128G memory. It's more reproducible on a machine with large memory.
The bug 610208, which was closed 'insufficient data', seems relevant.
Created attachment 510397 [details]
the domain config
Created attachment 510398 [details]
Created attachment 510399 [details]
Problem only for PV guest as qemu-dm is setuping xenpv machine and do not recieve kill signal.
reproduce the bug in xen-3.0.3-132.el5 and verify the bug in xen-3.0.3-135.el5.
Steps of reproduce:
1. destroy a pv guest right after it is created
# xm cr pv.cfg; xm des RHEL5.8-64-PV
Using config file "./pv.cfg".
Using <class 'grub.GrubConf.GrubConfigFile'> to parse /grub/menu.lst
Started domain RHEL5.8-64-PV
2. check the xm list, there is no guest running.
# xm list
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 2880 2 r----- 942.9
3. Check the processes, and the qemu-dm is not killed
# ps aux | grep qemu
root 11627 0.1 0.1 90444 4824 ? Sl 14:27 0:00 /usr/lib64/xen/bin/qemu-dm -M xenpv -d 5 -domain-name RHEL5.8-64-PV -vnc 0.0.0.0:0 -vncunused -k en-us
root 11892 0.0 0.0 61172 736 pts/0 S+ 14:27 0:00 grep qemu
Verify the bug with same steps as reproduce, and repeat the test for 5 times, the qemu-dm is killed every time.
So change this bug into VERIFIED.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.