The issue is manyfold: - On paused domains Starting shutdown on guest: testguest3 error: Failed to shutdown domain 50ee425f-899e-4489-b5b0-22a97c2a2f42 error: Requested operation is not valid: domain is not running - on running but non cooperative domains The softer shutdown will be ignored by the guest
TL;DR it can't shut down either type. Now for the non-cooperative case it is preferred to do nothing as the reasons why it doesn't shut down are unclear, so any action taken could be wrong. I can't help you a lot for that. While "shutdown" won't work on any type of the above it is clear that the suspend action works. It ignores any guest cooperation and just saves memory to a file to restore it later on. This will make the qemu process eventually disappear which is what you need in your case for LVM. But "suspend" is not concurrent and therefore (too slow when scaling) therefore it is not the default. I'm glad that we can consider "setting ON_SHUTDOWN=suspend" a config workaround for you. Now lets consider how we could make this smarter. We could in theory - fall back to call "managedsave" on ANY guest either non-cooperative or paused which would ensure it is freed up. I'd need to check what the implications of this are for other cases, but it seems like an interesting approach. Writing some test code later on and then hopefully having something to upstream. @gene - for when I upstream I'd like to add you as Reported-by, but I'd need your email for that. You can find my email on launchpad (just click on my user) - if you are ok that I add you let me know your address please. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803741 Title: libvirt-guests.sh cannot stop Paused domains To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1803741/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
