Created attachment 556793 [details]
vdsm log.

Description of problem:

scenario: 

- vm is stuck on wait_for_lunch (probably, call created was never succeeded, and there is no corresponding qemu-process for it). 
- after quit some time, one tries to destroy the intractable vm. 

Thread-3739::DEBUG::2012-01-22 10:14:02,133::clientIF::76::vds::(wrapper) [10.16.144.104]::call destroy with ('4f3c3506-8196-49d3-8987-ec5c22f063bb',) {}

Unfortunately, there is no return for it, but I do see this message on getVmStats:

Thread-3738::DEBUG::2012-01-22 10:14:02,122::clientIF::81::vds::(wrapper) return getVmStats with {'status': {'message': 'Done', 'code': 0}, 'statsList': [{'status': 'Down', 'hash': '0', 'exitMessage': 'unsupported configuration: the QEM
U binary /usr/bin/qemu-kvm does not support smbios settings', 'vmId': '4f3c3506-8196-49d3-8987-ec5c22f063bb', 'timeOffset': '0', 'exitCode': 1}]}

some output for reference to correlate with logs

323d3dd5-cc6b-4e31-8210-f55c7fb96ca8      0  myVm7                WaitForLaunch                            
396a4645-9b9d-4a4c-b3a9-eed0320fb8a3      0  myVm9                WaitForLaunch                            
0a6ee3a6-cd6b-49d0-ad60-5a5a1d0f16be      0  myVm6                WaitForLaunch                            
9365c81d-c075-47c7-ae58-2f66cff1ae05      0  myVm8                WaitForLaunch                            
75f8b814-8a85-4bb0-a428-523e0ec6875c      0  myVm0                WaitForLaunch