$ sudo virsh list --all
Id Name State
----------------------------------------------------
2 ubuntu1710 running
- instance-00000004 shut off
In the logs I see after the suspend is issued:
Nov 14 03:12:05 awrep4 libvirtd[3451]: 2017-11-14 03:12:05.265+0000: 3787: error : qemuDomainAgentAvailable:6078 : Guest agent is not responding: QEMU guest agent is not connected
Which I believe is the instance suspending itself thus disconnecting the guest agent, so probably nothing to worry about there.
But when the wakeup is issued: I can't reconnect to the instance:
$ sudo virsh dompmwakeup ubuntu1710
Domain ubuntu1710 successfully woken up
So I believe that this should be chased down in a different bug, and the original problem for which this bug was open (VM Reboot) has been fixed!!
Thanks Christian
It appears my update to this bug never saved properly:
I was able to test the following PPA: ppa:ci- train-ppa- service/ 3032
QEMU: 1:2.10+ dfsg-0ubuntu4~ ppa7
After executing the steps list in my description,
The Virtual Machine properly reboots as expected.
$ sudo virsh reboot ubuntu1710 --mode acpi
Domain ubuntu1710 is being rebooted
$ sudo virsh list --all ------- ------- ------- ------- ------- ------- ---
Id Name State
-------
1 ubuntu1710 running
- instance-00000004 shut off
I have also tested suspend capabilities which also appear to be somewhat working, at least better than where I was before:
$ sudo virsh dompmsuspend ubuntu1710 --target mem
Domain ubuntu1710 successfully suspended
$ sudo virsh list --all ------- ------- ------- ------- ------- ------- ---
Id Name State
-------
2 ubuntu1710 running
- instance-00000004 shut off
In the logs I see after the suspend is issued:
Nov 14 03:12:05 awrep4 libvirtd[3451]: 2017-11-14 03:12:05.265+0000: 3787: error : qemuDomainAgent Available: 6078 : Guest agent is not responding: QEMU guest agent is not connected
Which I believe is the instance suspending itself thus disconnecting the guest agent, so probably nothing to worry about there.
But when the wakeup is issued: I can't reconnect to the instance:
$ sudo virsh dompmwakeup ubuntu1710
Domain ubuntu1710 successfully woken up
So I believe that this should be chased down in a different bug, and the original problem for which this bug was open (VM Reboot) has been fixed!!
Thanks Christian