[ https://issues.apache.org/jira/browse/CLOUDSTACK-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bharat Kumar resolved CLOUDSTACK-5700. -------------------------------------- Resolution: Fixed > [Vmsync] - kvm- "paused" state of Vm is not synced to CS. > --------------------------------------------------------- > > Key: CLOUDSTACK-5700 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5700 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM, Management Server > Affects Versions: 4.3.0 > Environment: Build from 4.3 > Reporter: Sangeetha Hariharan > Assignee: Bharat Kumar > Fix For: 4.4.0, 4.5.0 > > > [Vmsync] - kvm - "paused" state of Vm is not synced to CS. > Steps to reproduce the problem: > PreReq: > Have few Vms deployed using Cloudstack. > Steps: > Outside of Cloudstack , Suspend an existing VM using the following command: > virsh suspend <domain Id> > Vmsync does not detect the "paused" state of a VM. CS reports the real state > of this VM as "running" > 2013-12-31 18:44:20,977 DEBUG [c.c.v.VirtualMachineManagerImpl] > (AgentConnectTaskPool-4:ctx-daf59377) Found 6 VMs for host 2 > 2013-12-31 18:44:20,990 DEBUG [c.c.v.VirtualMachineManagerImpl] > (AgentConnectTaskPool-4:ctx-daf59377) VM i-3-3-VM: cs state = Running and > realState = Running > 2013-12-31 18:44:20,997 DEBUG [c.c.v.VirtualMachineManagerImpl] > (AgentConnectTaskPool-4:ctx-daf59377) VM i-3-3-VM: cs state = Running and > realState = Running > 2013-12-31 18:44:20,997 DEBUG [c.c.v.VirtualMachineManagerImpl] > (AgentConnectTaskPool-4:ctx-daf59377) Both states are Running for > VM[User|TestVM-1] > [root@Rack3Host14 ~]# virsh list > Id Name State > ---------------------------------------------------- > 2 r-4-VM running > 5 i-3-6-VM running > 6 i-3-5-VM running > 7 s-9-VM running > 9 i-3-8-VM running > 10 i-3-3-VM paused -- This message was sent by Atlassian JIRA (v6.3.4#6332)