Sorry - found some other qemu-guest-agent issues along that were easier to address and I did so right away. Back on this now.
The actions run by the guest-agent are: - guest-sync (this is only to ensure no old content is on the channel, no relation to suspend) - guest-suspend-ram (the actual suspend) To do so it tries to call pm-utils (for it's quirks) and falls back to sysfs if not available. Note: by default pm-utils is not even a suggest so we WILL use the sysfs write usually. As I mentioned before there is no direct response by the command. Instead a QMP event will be emitted. Either the event or the query for status via qmp will be what should set libvirt to "pmsuspended" We should assume that it doesn't reach that state. With pm-utils it would call those $ pm-is-supported --suspend $ pm-suspend But without it is a slighly more advanced echo, it will: 1. open /sys/power/state read only 2. check if "mem" is in there (it is in our case) 3. open /sys/power/state write only 4. writes "mem" into that So not qemu-guest-agent is broken, but the suspend in kernel (this might still be related to the qemu environment it runs in thou). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737786 Title: (arm64) unable to dompmwakeup a vm after being suspended To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1737786/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
