qemu core dumps when unable to allocate ram for new virtual machine
Bug #1650067 reported by
Dave Chiluk
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Cloud Archive |
Fix Released
|
Critical
|
Unassigned | ||
Kilo |
Fix Released
|
Critical
|
Unassigned | ||
Liberty |
Fix Released
|
Critical
|
Unassigned | ||
Mitaka |
Fix Released
|
Critical
|
Unassigned |
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 f8ed85ac992c488
I'm opening this case, while I decide if it's worthwhile to re-spin qemu to fix this issue.
description: | updated |
Changed in cloud-archive: | |
status: | New → Fix Released |
tags: | added: s390x |
To post a comment you must log in.
The commit in question was included in 2.5 Qemu stream, so I've nominated for Mitaka (to mark fix released), Liberty, Kilo. Still need to determine if this is an issue in the Trusty packages. If so, then we need to raise an Ubuntu task to get it fixed there prior to be included in the precise-icehouse cloud-archive.