[Group.of.nepali.translators] [Bug 1612089] Re: Fix for CVE-2016-5403 causes crash on migration if memory stats are enabled
This bug was fixed in the package qemu - 1:2.2+dfsg-5expubuntu9.7~cloud7 --- qemu (1:2.2+dfsg-5expubuntu9.7~cloud7) trusty-kilo; urgency=medium . * SECURITY REGRESSION: crash on migration with memory stats enabled (LP: #1612089) - debian/patches/CVE-2016-5403.patch: disable for now pending investigation. ** Changed in: cloud-archive/kilo Status: Fix Committed => Fix Released -- 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: Invalid Status in Ubuntu Cloud Archive icehouse series: Fix Committed Status in Ubuntu Cloud Archive kilo series: Fix Released Status in Ubuntu Cloud Archive liberty series: Fix Released Status in Ubuntu Cloud Archive mitaka series: Fix Released 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: 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
[Group.of.nepali.translators] [Bug 1612089] Re: Fix for CVE-2016-5403 causes crash on migration if memory stats are enabled
This bug was fixed in the package qemu - 1:2.3+dfsg-5ubuntu9.4~cloud2 --- qemu (1:2.3+dfsg-5ubuntu9.4~cloud2) trusty-liberty; urgency=medium . * SECURITY REGRESSION: crash on migration with memory stats enabled (LP: #1612089) - debian/patches/CVE-2016-5403.patch: disable for now pending investigation. ** Changed in: cloud-archive/liberty Status: Fix Committed => Fix Released -- 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: Invalid Status in Ubuntu Cloud Archive icehouse series: Fix Committed Status in Ubuntu Cloud Archive kilo series: Fix Committed Status in Ubuntu Cloud Archive liberty series: Fix Released Status in Ubuntu Cloud Archive mitaka series: Fix Released 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: 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
[Group.of.nepali.translators] [Bug 1612089] Re: Fix for CVE-2016-5403 causes crash on migration if memory stats are enabled
This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.4~cloud0 --- qemu (1:2.5+dfsg-5ubuntu10.4~cloud0) trusty-mitaka; urgency=medium . * New update for the Ubuntu Cloud Archive. . qemu (1:2.5+dfsg-5ubuntu10.4) xenial-security; urgency=medium . * SECURITY REGRESSION: crash on migration with memory stats enabled (LP: #1612089) - debian/patches/CVE-2016-5403.patch: disable for now pending investigation. ** Changed in: cloud-archive/mitaka Status: Triaged => Fix Released -- 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: Invalid Status in Ubuntu Cloud Archive icehouse series: Fix Committed Status in Ubuntu Cloud Archive kilo series: Fix Committed Status in Ubuntu Cloud Archive liberty series: Fix Released Status in Ubuntu Cloud Archive mitaka series: Fix Released 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: 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
[Group.of.nepali.translators] [Bug 1612089] Re: Fix for CVE-2016-5403 causes crash on migration if memory stats are enabled
** Changed in: cloud-archive Status: New => Invalid ** Changed in: cloud-archive/mitaka Status: New => Triaged ** Changed in: cloud-archive Importance: Undecided => High -- 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: Invalid Status in Ubuntu Cloud Archive icehouse series: Fix Committed Status in Ubuntu Cloud Archive kilo series: Fix Committed Status in Ubuntu Cloud Archive liberty series: Fix Committed Status in Ubuntu Cloud Archive mitaka series: Triaged 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: 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
[Group.of.nepali.translators] [Bug 1612089] Re: Fix for CVE-2016-5403 causes crash on migration if memory stats are enabled
** No longer affects: cloud-archive/newton -- 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: Fix Committed Status in Ubuntu Cloud Archive kilo series: Fix Committed Status in Ubuntu Cloud Archive liberty series: Fix Committed Status in Ubuntu Cloud Archive mitaka 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: 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
[Group.of.nepali.translators] [Bug 1612089] Re: Fix for CVE-2016-5403 causes crash on migration if memory stats are enabled
** 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: 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
[Group.of.nepali.translators] [Bug 1612089] Re: Fix for CVE-2016-5403 causes crash on migration if memory stats are enabled
** Also affects: cloud-archive Importance: Undecided Status: New -- 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 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: 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
[Group.of.nepali.translators] [Bug 1612089] Re: Fix for CVE-2016-5403 causes crash on migration if memory stats are enabled
** No longer affects: qemu (Ubuntu Precise) ** No longer affects: qemu-kvm (Ubuntu Trusty) ** No longer affects: qemu-kvm (Ubuntu Xenial) ** No longer affects: qemu-kvm (Ubuntu Yakkety) ** No longer affects: qemu-kvm (Ubuntu) -- 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 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: 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/ubuntu/+source/qemu/+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
[Group.of.nepali.translators] [Bug 1612089] Re: Fix for CVE-2016-5403 causes crash on migration if memory stats are enabled
** Changed in: qemu (Ubuntu Precise) Status: Confirmed => Invalid ** Also affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New ** Changed in: qemu-kvm (Ubuntu Trusty) Status: New => Invalid ** Changed in: qemu-kvm (Ubuntu Xenial) Status: New => Invalid ** Changed in: qemu-kvm (Ubuntu Yakkety) Status: New => Invalid ** Changed in: qemu-kvm (Ubuntu Precise) Importance: Undecided => High ** Changed in: qemu-kvm (Ubuntu Precise) Status: New => Fix Released ** Changed in: qemu-kvm (Ubuntu Precise) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) -- 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 qemu package in Ubuntu: Fix Released Status in qemu-kvm package in Ubuntu: Invalid Status in qemu source package in Precise: Invalid Status in qemu-kvm source package in Precise: Fix Released Status in qemu source package in Trusty: Fix Released Status in qemu-kvm source package in Trusty: Invalid Status in qemu source package in Xenial: Fix Released Status in qemu-kvm source package in Xenial: Invalid Status in qemu source package in Yakkety: Fix Released Status in qemu-kvm source package in Yakkety: Invalid Bug description: If memory statistics are enabled for the memory baloon device in libvirt like this: 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/ubuntu/+source/qemu/+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
[Group.of.nepali.translators] [Bug 1612089] Re: Fix for CVE-2016-5403 causes crash on migration if memory stats are enabled
I can't reproduce this in Yakkety with qemu 2.6, which means it's a bad backport to earlier releases. ** Changed in: qemu (Ubuntu Yakkety) Status: Confirmed => Fix Released -- 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 qemu package in Ubuntu: Fix Released Status in qemu source package in Precise: Confirmed Status in qemu source package in Trusty: Confirmed Status in qemu source package in Xenial: Confirmed 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: 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/ubuntu/+source/qemu/+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
