GNOME Bugzilla – Bug 674826
qemu-kvm is still running after Boxes has exited
Last modified: 2016-03-31 13:57:03 UTC
qemu-kvm is still running after Boxes has exited.
(In reply to comment #0) > qemu-kvm is still running after Boxes has exited. Shouldn't happen and if it does, its very likely a bug in libvirt.
virt-manager sees the VM as "suspended" after Boxes exits, and will happily resume it or shut it down, so maybe Boxes is not doing something it should to fully shutdown qemu.
(In reply to comment #2) > virt-manager sees the VM as "suspended" after Boxes exits, and will happily > resume it or shut it down, so maybe Boxes is not doing something it should to > fully shutdown qemu. That would be the case if you have explicitly configured Boxes to 'suspend' domains OR if you still have the old source config (~/.config/gnome-boxes/sources/QEMU\ Session) before we started to save domains on exit.
FWIW, on my machine here is what libvirt reports about my (automatically) saved domains: $ virsh list --all Id Name State ---------------------------------------------------- - Fedora 16 shut off - Fedora 17 shut off - Microsoft Windows XP shut off $ ps -ef|grep qemu zeenix 5222 2018 0 23:33 pts/0 00:00:00 grep --color=auto qemu $
Id Name State ---------------------------------------------------- 3 precise-desktop-i386.iso running
(In reply to comment #3) if you still have the old source config > (~/.config/gnome-boxes/sources/QEMU\ Session) before we started to save domains > on exit. I did some cleanup and qemu processes are indeed gone afer exiting boxes. However, after restarting boxes, the VM does not restart where it was before boxes exit. Does the VM gets a "force shutdown/physical power off" before exiting? This could cause data loss/virtual disk corruption...
(In reply to comment #6) > (In reply to comment #3) > if you still have the old source config > > (~/.config/gnome-boxes/sources/QEMU\ Session) before we started to save domains > > on exit. > > I did some cleanup and qemu processes are indeed gone afer exiting boxes. > However, after restarting boxes, the VM does not restart where it was before > boxes exit. Does the VM gets a "force shutdown/physical power off" before > exiting? This could cause data loss/virtual disk corruption... No, we only call one function in libvirt to save the domain and shutdown is implied in that. I have seen that sometimes the restore doesn't exactly work and that would be a bug in libvirt/qemu.
Just to be 100% sure I'm expecting the right thing: default behaviour of boxes is to save running VMs to disk on exit, qemu is no longer running, and when restarting boxes and the VM, it restarts where it was before? If I don't get this behaviour, this means there's a bug somewhere?
(In reply to comment #8) > Just to be 100% sure I'm expecting the right thing: default behaviour of boxes > is to save running VMs to disk on exit, qemu is no longer running, and when > restarting boxes and the VM, it restarts where it was before? If I don't get > this behaviour, this means there's a bug somewhere? Correct!
We'd need a description how to reproduce the issue today. Thanks for taking the time to report this bug. This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug.
Might this be a dup of 683473?
Yup, let's bet on that *** This bug has been marked as a duplicate of bug 683473 ***