Not keen on providing apport info as this is a production system with
multiple tenants and we have no agreement with Canonical. The info here
and verification from others indicates this is a simple bug to reproduce
and not specific to our systems.
--
You received this bug notification because
Here's an example of an affected qemu command, as already pointed out
the relevant parts are the -cpu host and -smp n where n1.
qemu-system-x86_64 -enable-kvm -name instance-000173d4 -S -machine
pc-1.0,accel=kvm,usb=off -cpu host -m 16384 -realtime mlock=off -smp
4,sockets=4,cores=1,threads=1
Public bug reported:
Just upgraded OpenStack compute hosts in our public cloud (using qemu-
kvm via libvirt) from Precise to Trusty (14.04.1), now on kernel
3.13.0-36-generic with qemu-kvm 2.0.0+dfsg-2ubuntu1.5.
Following the upgrade, whenever we try to start an smp/multicore Trusty
guest
