see bug 1829245 for regression introduced by this patch; these patches
will be reverted from xenial, and then re-uploaded along with a patch
for the regression in bug 1829380
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
This bug was fixed in the package qemu - 1:2.8+dfsg-3ubuntu2.9~cloud5.1
---
qemu (1:2.8+dfsg-3ubuntu2.9~cloud5.1) xenial-ocata; urgency=medium
.
* d/p/lp1823458/add-VirtIONet-vhost_stopped-flag-to-prevent-multiple.patch,
This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.37~cloud0
---
qemu (1:2.5+dfsg-5ubuntu10.37~cloud0) trusty-mitaka; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
qemu (1:2.5+dfsg-5ubuntu10.37) xenial; urgency=medium
.
*
This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.37
---
qemu (1:2.5+dfsg-5ubuntu10.37) xenial; urgency=medium
* 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:
-
This is even more than what I wanted, thanks!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1823458
Title:
race condition between vhost_net_stop and CHR_EVENT_CLOSED on shutdown
crashes qemu
On a Xenial DPDK setup with the proposed qemu version (1:2.5+dfsg-
5ubuntu10.37), I created a VM and attached a vhost-user interface to it
using this xml:
$ cat vm3-iface2.xml
the OVS interface was created with:
# ovs-vsctl add-port br1 vhu2 -- set Interface vhu2
> @cpaelzer, if you have any suggestions for specific tests/configurations
> that might be good to test the specific code changed here, please let me
> know.
I have ran the few test that would cover that area in the past on PPAs already.
Unfortunately this is a very specific path and I don't have
@sil2100 yes I agree, let's wait longer before releasing. We have the
Canonical customer performing testing with the package, and we can run
some additional sanity checks as well. The config coming from the
customer is an openstack setup using OVS, so that's what we will setup
and perform sanity
I'm setting this to Incomplete per sil2100's last comment.
** Changed in: qemu (Ubuntu Xenial)
Status: Fix Committed => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1823458
Since this SRU is rather hard to verify + Christian's suggestion to let
the SRU age a bit longer, I would still wait a few days before
releasing.
Dan (or anyone else involved) - could you maybe perform some safety
checks using this package against the use-cases mentioned in the
regression
clarification: by "original reporter" I mean the customer of Canonical,
reporting the problem to us.
** Tags removed: verification-mitaka-needed verification-needed
verification-needed-xenial verification-ocata-needed
** Tags added: verification-done verification-done-xenial
This has been verified by the original reporter to fix the problem of
qemu crashing.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1823458
Title:
race condition between vhost_net_stop and
** Patch added: "lp1823458-ocata.debdiff"
https://bugs.launchpad.net/cloud-archive/+bug/1823458/+attachment/5258683/+files/lp1823458-ocata.debdiff
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
uca: workaround patches are needed in mitaka and ocata. Mitaka can pull
from Xenial build as usual, and debdiff for Ocata attached. Other UCA
releases are later than 2.9 and so are fixed with the upstream fix
mentioned in the description.
--
You received this bug notification because you are a
** Also affects: cloud-archive/ocata
Importance: Undecided
Status: New
** Changed in: cloud-archive/ocata
Importance: Undecided => Medium
** Changed in: cloud-archive/ocata
Status: New => Triaged
** Changed in: cloud-archive
Status: New => Fix Released
--
You
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/mitaka
Importance: Undecided
Status: New
** Changed in: cloud-archive/mitaka
Importance: Undecided => Medium
** Changed in: cloud-archive/mitaka
Status: New => Triaged
SRU note: please see Christian's MP review (linked from this bug) for
some advice on additional care during SRU verification.
** Changed in: qemu (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-xenial
--
You received this bug
** Merge proposal linked:
https://code.launchpad.net/~ddstreet/ubuntu/+source/qemu/+git/qemu/+merge/366392
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1823458
Title:
race condition between
Note as mentioned in the description, it appears this was fixed upstream
by commit e7c83a885f8, which is included starting in version 2.9.
However, this commit depends on at least commit 5345fdb4467, and likely
more other previous commits, which make widespread code changes and are
unsuitable to
** Changed in: qemu (Ubuntu Disco)
Status: In Progress => Fix Released
** Changed in: qemu (Ubuntu)
Status: In Progress => Fix Released
** Changed in: qemu
Status: In Progress => Fix Released
** Changed in: qemu (Ubuntu Cosmic)
Status: In Progress => Fix Released
**
** Description changed:
[impact]
on shutdown of a guest, there is a race condition that results in qemu
crashing instead of normally shutting down. The bt looks similar to
this (depending on the specific version of qemu, of course; this is
taken from 2.5 version of qemu):
(gdb)
test builds in https://launchpad.net/~ddstreet/+archive/ubuntu/lp1823458
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1823458
Title:
race condition between vhost_net_stop and CHR_EVENT_CLOSED on
** Description changed:
[impact]
on shutdown of a guest, there is a race condition that results in qemu
crashing instead of normally shutting down. The bt looks similar to
this (depending on the specific version of qemu, of course; this is
taken from 2.5 version of qemu):
(gdb)
** Also affects: qemu (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu Trusty)
Status: New => In Progress
** Changed in: qemu (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: qemu (Ubuntu Trusty)
Assignee: (unassigned) => Dan
24 matches
Mail list logo
