[Bug 1650067] Re: qemu core dumps when unable to allocate ram for new virtual machine

[Dave Chiluk]

Here's my proposed solution for trusty-kilo.  This ended up being more
involved than I originally expected.

I started with attmepting to do a clean cherry-pick, but the list of
patches quickly grew unmanageable.

f8ed85ac99
a29a37b994
1e9b65bb1b
edf6f3b335
4463dcb85c

These diffs together totalled roughly 2k lines of diffs, and affected
large areas of the code base.  I eventually settled on just f8ed85ac99
and backported the spirit of a29a37b994 (it doesn't even close to apply,
but it's primary function is to enable logic for using error_fatal).

Now hopefully this applies to the liberty archives as well.

** Patch added: "lp1650067.t.kilo.debdiff"
   https://bugs.launchpad.net/cloud-archive/+bug/1650067/+attachment/4812229/+files/lp1650067.t.kilo.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1650067

Title:
  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:
  Triaged
Status in Ubuntu Cloud Archive liberty series:
  Triaged
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
  f8ed85ac992c48814d916d5df4d44f9a971c5de4

  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:
https://bugs.launchpad.net/cloud-archive/+bug/1650067/+subscriptions