group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1829380@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.40

---------------
qemu (1:2.5+dfsg-5ubuntu10.40) xenial; urgency=medium

  * Restore patches that caused regression
    - d/p/lp1823458/add-VirtIONet-vhost_stopped-flag-to-prevent-multiple.patch
    - d/p/lp1823458/do-not-call-vhost_net_cleanup-on-running-net-from-ch.patch
  * Fix regression introduced by above patches (LP: #1829380)
    - d/p/lp1829380.patch

  [ Rafael David Tinoco ]
  * d/p/lp1828288/target-i386-Set-AMD-alias-bits-after-filtering-CPUID.patch
    - Fix issues with CPUID_EXT2_AMD_ALIASES allowing guests using
      cpu passthrough to boot. (LP: #1828288)

 -- Dan Streetman <ddstreet@xxxxxxxxxxxxx>  Thu, 16 May 2019 14:29:56
-0400

** Changed in: qemu (Ubuntu Xenial)
       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/1829380

Title:
  race condition between vhost_net_stop and CHR_EVENT_CLOSED on shutdown
  crashes qemu (fix regression)

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive mitaka series:
  Triaged
Status in Ubuntu Cloud Archive ocata series:
  Fix Released
Status in qemu package in Ubuntu:
  Invalid
Status in qemu source package in Xenial:
  Fix Released

Bug description:
  [impact]

  this bug is to track re-uploading the fix for bug 1823458 plus a patch
  to fix a regression it introduced.

  instead of copying the details from bug 1823458, please see that bug
  for impact and testcase.

  [test case]

  see bug 1823458 for the original bug test case

  for the regression test case from bug 1829245, rebooting the guest
  will result in the guest being unable to use the interface (possibly a
  couple reboots are needed to reproduce if the interface still works
  after the first reboot).

  [regression potential]

  see bug 1823458

  additionally, the regression from the last fix is in bug 1829245.

  the change is in code where this still has the regression potential of
  causing guest networking to fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1829380/+subscriptions