Comment 3 for bug 1829245

I'm wondering as 1:2.5+dfsg-5ubuntu10.37 never existed in the wild.
The archive should have went from .36 to .38 I'd think.

There is a single upload [1] covering both.
.37 only existed in proposed I'd think.

Never the less it contained a few changes to networking.
One to slirp (not your case), but also:
  * 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:
    - Prevent crash due to race condition on shutdown;
      this is fixed differently upstream (starting in Bionic), but
      the change is too large to backport into Xenial. These two very
      small patches work around the problem in an unintrusive way.
      (LP: #1823458)

I'll subscribe mdeslaur, sbeattie (uploaders) and ddstreet (patch author) to consider your case.

Please add whatever else you found, in particular:
- does every qemu start fail networking for you?
- if not what part of the config is it that seem required to hit the issue
- how is your networking set up in general (normal libvirt network, OVS, ..)?
- which network HW is attached (in case it makes a difference)?
- the guest cmdline looks like a libvirt qemu-cmdline, so you might add the guest XML

[1]: https://launchpad.net/ubuntu/+source/qemu/1:2.5+dfsg-5ubuntu10.37