search for: everaert

...n" 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 virsh/libvirt? Regards, Roland Everaert.

...'/> </vcpus> So the process is defunct, does a 'kill -9 48301' could fix the problem with a restart of libvirtd? Thanks, Roland. On Tue, Jul 5, 2016 at 2:55 PM, Daniel P. Berrange <berrange@redhat.com> wrote: > On Tue, Jul 05, 2016 at 02:50:25PM +0200, Roland Everaert wrote: > > 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: >...

On Tue, Jul 05, 2016 at 02:50:25PM +0200, Roland Everaert wrote: > 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 stat...

On Tue, Jul 05, 2016 at 04:20:58PM +0200, Roland Everaert wrote: > Restarting libvirtd doesn't change the situation. > > But looking into the logs I see the following: > > - Last lines in /var/log/libvirt/libvirtd.log: > > 2016-07-05 13:26:42.792+0000: 24552: warning : qemuProcessKill:4419 : Timed > out waiting after SIGKILL...