[Bug 1829380] Please test proposed package

[Corey Bryant]

Hello Dan, or anyone else affected,

Accepted qemu into mitaka-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.

Please help us by testing this new package. To enable the -proposed
repository:

  sudo add-apt-repository cloud-archive:mitaka-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-mitaka-needed to verification-mitaka-done. If it does
not fix the bug for you, please add a comment stating that, and change
the tag to verification-mitaka-failed. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!

** Changed in: cloud-archive/mitaka
       Status: Triaged => Fix Committed

** Tags added: verification-mitaka-needed

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
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:
  Fix Committed
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