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

[Dave Chiluk]

Verified kilo staging as well.  Was able to boot with 20G allocated.
Booting with 21G correctly yielded error message smae as liberty.

ubuntu at nuc3:/etc/apt/sources.list.d$ virsh start demo
error: Failed to start domain demo
error: internal error: process exited while connecting to monitor: 2017-02-08T17:47:50.013119Z qemu-system-x86_64: cannot set up guest memory 'pc.ram': Cannot allocate memory

No Core dump was created.  So everything looks good.

** Tags added: verification-done verification-done-kilo

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