This is a qemu issue, not a kernel issue. This works with qemu 2.1, and
not 2.0. Doing a bisect now.
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu)
** Changed in: qemu (Ubuntu)
Status: New => Fix Released
** No longer affects: linux (Ubuntu Trusty)
** Changed in: qemu (Ubuntu Trusty)
Assignee: (unassigned) => Chris J Arges (arges)
** Changed in: qemu (Ubuntu Trusty)
Status: New => In Progress
** Changed in: qemu (Ubuntu Trusty)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1366868
Title:
kvm: dompmwakeup fails if domain becomes pmsuspended
Status in “qemu” package in Ubuntu:
Fix Released
Status in “qemu” source package in Trusty:
In Progress
Bug description:
[Impact]
When using KVM, 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
So far I've noticed that on Utopic this works fine, while on Trusty
this fails; a bisect is needed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1366868/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
