[Bug 1650067] Please test proposed package

Ryan Beisner 1650067 at bugs.launchpad.net
Wed Feb 8 21:44:26 UTC 2017

Hello Dave, or anyone else affected,

Accepted qemu into liberty-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.

Please help us by testing this new package. To enable the -proposed

  sudo add-apt-repository cloud-archive:liberty-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-liberty-needed to verification-liberty-done. If it
does not fix the bug for you, please add a comment stating that, and
change the tag to verification-liberty-failed. In either case, details
of your testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in

** Changed in: cloud-archive/liberty
       Status: Triaged => Fix Committed

** Tags added: verification-liberty-needed

You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.

  qemu core dumps when unable to allocate ram for new virtual machine

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive kilo series:
  Fix Committed
Status in Ubuntu Cloud Archive liberty series:
  Fix Committed
Status in Ubuntu Cloud Archive mitaka series:
  Fix Released

Bug description:
  Qemu available in the kilo-staging cloud archive will cause an abort
  which will generate a core dump, if there is not enough memory
  available to satisfy creation of the new Virtual Machine.

  This becomes more critical if this happens over and over in highly
  resource constrained environments, as the core dumps start filling up
  the disk.

  This is resolved with upstream commit

  I'm opening this case, while I decide if it's worthwhile to re-spin
  qemu to fix this issue.

To manage notifications about this bug go to:

More information about the Ubuntu-openstack-bugs mailing list