** Also affects: cloud-archive/icehouse Importance: Undecided Status: New
** Also affects: cloud-archive/newton Importance: Undecided Status: New ** Also affects: cloud-archive/mitaka Importance: Undecided Status: New ** Also affects: cloud-archive/kilo Importance: Undecided Status: New ** Also affects: cloud-archive/liberty Importance: Undecided Status: New ** Changed in: cloud-archive/icehouse Assignee: (unassigned) => Corey Bryant (corey.bryant) ** Changed in: cloud-archive/kilo Assignee: (unassigned) => Corey Bryant (corey.bryant) ** Changed in: cloud-archive/liberty Assignee: (unassigned) => Corey Bryant (corey.bryant) ** Changed in: cloud-archive/mitaka Assignee: (unassigned) => Corey Bryant (corey.bryant) ** Changed in: cloud-archive/newton Assignee: (unassigned) => Corey Bryant (corey.bryant) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1612089 Title: Fix for CVE-2016-5403 causes crash on migration if memory stats are enabled Status in Ubuntu Cloud Archive: New Status in Ubuntu Cloud Archive icehouse series: New Status in Ubuntu Cloud Archive kilo series: New Status in Ubuntu Cloud Archive liberty series: New Status in Ubuntu Cloud Archive mitaka series: New Status in Ubuntu Cloud Archive newton series: New Status in qemu package in Ubuntu: Fix Released Status in qemu-kvm source package in Precise: Fix Released Status in qemu source package in Trusty: Fix Released Status in qemu source package in Xenial: Fix Released Status in qemu source package in Yakkety: Fix Released Bug description: If memory statistics are enabled for the memory baloon device in libvirt like this: <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> <stats period='10'/> </memballoon> Then qemu exits with "qemu-system-x86_64: Virtqueue size exceeded" after the VM is migrated or when starting the VM again after a managedsave. This bug is present since 2.0.0+dfsg-2ubuntu1.26 and was not present in 2.0.0+dfsg-2ubuntu1.24. It's most probably caused by the Fix for CVE-2016-5403. Steps to reproduce: 1. Create a VM with libvirt which contains the above memory balloon device 2. Start the VM and let the Linux kernel boot (bug does not appear if the kernel is not yet booted, eg. while in the PXE boot phase) 3. Issue a managedsave 4. Start the VM again 5. The VM is restored and "crashes" right after it starts running again. 6. You can find the qemu output "qemu-system-x86_64: Virtqueue size exceeded" in the log at /var/log/libvirt/vmname.log ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-system-x86 2.0.0+dfsg-2ubuntu1.26 ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39 Uname: Linux 3.13.0-93-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Thu Aug 11 08:39:33 2016 SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1612089/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp