[Bug 1366868] Re: kvm: dompmwakeup fails if domain becomes pmsuspended
Chris J Arges
1366868 at bugs.launchpad.net
Thu Sep 11 02:20:51 UTC 2014
** Description changed:
[Impact]
When using qemu/kvm/libvirt, if one suspends the VM using actual power
suspending code, the guest cannot resume using 'virsh dompmwakeup'.
[Test Case]
1) Create a KVM VM and install Trusty using libvirt (although qemu alone will also exhibit this problem)
2) Inside the vm run (as root): 'echo mem > /sys/power/state'
3) From the hypervisor run 'virsh dompmwakeup <domain name>'
4) The domain should resume
+
+ [Regression Potential]
+ Commit 2feb1258cbf77047e448a4a2736965d6010d8764 from seabios backported into trusty fixes the issue.
** Description changed:
[Impact]
When using qemu/kvm/libvirt, if one suspends the VM using actual power
suspending code, the guest cannot resume using 'virsh dompmwakeup'.
[Test Case]
1) Create a KVM VM and install Trusty using libvirt (although qemu alone will also exhibit this problem)
2) Inside the vm run (as root): 'echo mem > /sys/power/state'
3) From the hypervisor run 'virsh dompmwakeup <domain name>'
4) The domain should resume
[Regression Potential]
- Commit 2feb1258cbf77047e448a4a2736965d6010d8764 from seabios backported into trusty fixes the issue.
+ Commit 40d020f56226aee7c75a6c29f471c4b866765732 from seabios backported into trusty fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to seabios in Ubuntu.
https://bugs.launchpad.net/bugs/1366868
Title:
kvm: dompmwakeup fails if domain becomes pmsuspended
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/1366868/+subscriptions
More information about the Ubuntu-server-bugs
mailing list