kernel-packages team mailing list archive

[Chris J Arges <1366868@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

[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.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: Fix Released

** Affects: linux (Ubuntu Trusty)
     Importance: Medium
     Assignee: Chris J Arges (arges)
         Status: In Progress

** Also affects: linux (Ubuntu Trusty)
   Importance: Undecided
       Status: New

** Changed in: linux (Ubuntu Trusty)
     Assignee: (unassigned) => Chris J Arges (arges)

** Changed in: linux (Ubuntu)
       Status: In Progress => Fix Released

** Changed in: linux (Ubuntu)
     Assignee: Chris J Arges (arges) => (unassigned)

** Changed in: linux (Ubuntu Trusty)
       Status: New => In Progress

** Changed in: linux (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
   Importance: Medium => Undecided

-- 
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 “linux” package in Ubuntu:
  Fix Released
Status in “linux” 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/linux/+bug/1366868/+subscriptions