Created attachment 693407 [details]
logs

Description of problem:

I ran a vm -> suspended it -> resumed it -> powered off the vm -> started it again. 
the vm is stuck in wait for launch forever. 
looking at the host, the vm's status in libvirt is shut off and vdsm is not getting a pid. 
I am not sure if this is a libvirt bug or if vdsm is sending wrong configuration while running the vm. 

Version-Release number of selected component (if applicable):

sf5
vdsm-4.10.2-5.0.el6ev.x86_64
libvirt-0.10.2-18.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.348.el6.x86_64
qemu-img-rhev-0.12.1.2-2.348.el6.x86_64

How reproducible:

100%

Steps to Reproduce:
1. create a vm and run it on a specific host
2. suspend the vm -> resume the vm
3. power off the vm -> start the vm on the original host
  
Actual results:

vm is stuck in wait for launch forever. 

Expected results:

vm should not be stuck in wait for launch forever

Additional info: logs


88255c59-396b-47ed-90c9-72cca70a4a06      0  ZZZZZZ               WaitForLaunch                            
[root@gold-vdsd ~]# 
[root@gold-vdsd ~]# 
[root@gold-vdsd ~]# 
[root@gold-vdsd ~]# 
[root@gold-vdsd ~]# virsh -r list
 Id    Name                           State
----------------------------------------------------
 13    XXXXX                          shut off
 16    LLLLLL                         shut off
 19    ZZZZZZ                         shut off

[root@gold-vdsd ~]# 


[root@gold-vdsd ~]# date
Tue Feb  5 17:08:28 IST 2013
[root@gold-vdsd ~]# vdsClient -s 0 list table
88255c59-396b-47ed-90c9-72cca70a4a06      0  ZZZZZZ               WaitForLaunch   

[root@gold-vdsd ~]# date
Tue Feb  5 17:10:36 IST 2013
[root@gold-vdsd ~]# vdsClient -s 0 list table
88255c59-396b-47ed-90c9-72cca70a4a06      0  ZZZZZZ               WaitForLaunch     

root@gold-vdsd ~]# date
Tue Feb  5 17:15:12 IST 2013
[root@gold-vdsd ~]# vdsClient -s 0 list table
88255c59-396b-47ed-90c9-72cca70a4a06      0  ZZZZZZ               WaitForLaunch