search for: apr18

...ess 48301 2016-07-05 13:26:42.792+0000: 24552: error : qemuDomainDestroyFlags:2120 : operation failed: failed to kill qemu process with SIGTERM - lookup for process 48301: [root@lpextvms003c ~]# ps -ef | grep 48301 root 1114 24243 0 16:02 pts/1 00:00:00 grep 48301 oneadmin 48301 1 4 Apr18 ? 3-08:14:18 [qemu-kvm] <defunct> The name of the strange VM is one-357 I have seen that the last log in /var/log/libvirt/qemu/one-357.log are dated 2016/04/18. - Info on process one-357: [root@lpextvms003c ~]# cat /var/run/libvirt/qemu/one-357.xml <!-- WARNING: THIS IS AN AUTO-...

...000: 24552: error : qemuDomainDestroyFlags:2120 : > operation failed: failed to kill qemu process with SIGTERM > > - lookup for process 48301: > > [root@lpextvms003c ~]# ps -ef | grep 48301 > root 1114 24243 0 16:02 pts/1 00:00:00 grep 48301 > oneadmin 48301 1 4 Apr18 ? 3-08:14:18 [qemu-kvm] <defunct> Ok, so your QEMU process has not in fact died completely, so the libvirt state is correct. Usual cause of a qemu going into a defunct state is a storage failure which causes QEMU to be stuck in an uninterruptable I/O operation wait state. > So th...

Hello, We are currently facing a strange situation. One of our VM is shown by 'virsh list' as in state "in shutdown" but there is no more a qemu-kvm process linked to it. So we have a few questions: 1. What does means the state in shutdown (I have not found much information about it)? 2. How to cleanly "shutdown" the vm, or more correctly, clean the status in