I noticed the PPA update today. I installed it and I can confirm that
1:2.11+dfsg-1ubuntu7.28 is running for me without issue.
Thanks all. Quicker response than I was expecting!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks a lot @racb for the quick SRU and @paelzer to take care of the
rollback after I was gone.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885419
Title:
QEMU crash using virtio-scsi with
This bug was fixed in the package qemu - 1:2.11+dfsg-1ubuntu7.28
---
qemu (1:2.11+dfsg-1ubuntu7.28) bionic; urgency=medium
* Revert the fixes in 1:2.11+dfsg-1ubuntu7.27 for LP: 1805256 as they
were causing regressions for some iothread use cases (LP: #1885419)
-- Christian
Hi Robie,
I didn't do hourly long tests but spawned three different kind of guests on two
architectures just as sanity check. I didn't do more as the code is literally
the same as .26 was - only difference would be the toolchain at compile time.
But even that is only a few weeks different, as
Thanks. The vagrant-mutate seems unrelated (looking at the history it
fails often with various versions of qemu) and given that this is an
exact revert (I checked) I believe this is fine to release then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Christian, your request to skip the ageing period seems fine, and thank
you for responding to this bug so quickly. Your verification steps seem
to relate only to the regression though. Are you satisfied that qemu is
working generally OK from bionic-proposed - not just the specific crash
being
Thank you for the quick response.
[1] has built now and I was verifying that it fixes the reported regression in
Bionic.
Gladly 1:2.11+dfsg-1ubuntu7.26 still is in bionic-security so we can make a
three way comparison.
For tests I used a default uvtool created VM and added:
...
1
...
Hello Viktor, or anyone else affected,
Accepted qemu into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:2.11+dfsg-
1ubuntu7.28 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
I reopened and assigned rafael to bug 1805256 to re-evaluate this.
I've taken over this bug to push a revert to Bionic asap.
SRU Template added to the bug here.
Since it is a plain revert with no other changes in between this (other
than the changelog) matches the former 1%2.11+dfsg-1ubuntu7.26.
To ssh://git.launchpad.net/~usd-import-team/ubuntu/+source/qemu
* [new tag] upload/1%2.11+dfsg-1ubuntu7.28 ->
upload/1%2.11+dfsg-1ubuntu7.28
Uploading to ubuntu (via ftp to upload.ubuntu.com):
Uploading qemu_2.11+dfsg-1ubuntu7.28.dsc: done.
Uploading
** Description changed:
- After a recent upgrade I can't start a Windows 10 VM anymore, QEMU
- crashes with the error message:
+ [Impact]
+
+ * Despite quite a bunch of regression testing, explicit testing by
+different parties and extra time in -proposed the fix to bug 1805256
+
After an initial analysis by Rafael we decided that we will upload a
revert of version .27 so that we have more time to re-evaluate this.
The backports of the fixes added the assert, but chances are that the issue was
already present in Bionic before - not triggered but detected by the backport.
I have tagged it as update regression and bumped the priority.
Rafael is working on a fix already (thanks!).
Furthermore we reset the phasing of [1] to reduce the number of people getting
the update.
And thanks for the report Victor and Bill.
P.S. I have added a todo to the regression tests to
** Tags added: regression-update
** Changed in: qemu (Ubuntu Bionic)
Importance: High => Critical
** Changed in: qemu (Ubuntu Bionic)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have uploaded a source package that overseeds existing bionic version
at:
https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1885419
So anyone facing this issue can keep the PPA and have a mitigated
version for now.
--
You received this bug notification because you are a member of Ubuntu
Alright, looks like it only affects bionic:
(c)rafaeldtinoco@qemueoan:~$ virsh start tsting
Domain tsting started
as Eoan worked fine with the same XML definition.
** Also affects: qemu (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Focal)
I was able to reproduce it:
$ virsh start tsting
error: Failed to start domain tsting
error: internal error: process exited while connecting to monitor:
qemu-system-x86_64: /build/qemu-v_zvmu/qemu-2.11+dfsg/util/aio-posix.c:592:
aio_poll: Assertion `in_aio_context_home_thread(ctx)' failed.
BTW, as a workaround, one should keep using version:
- 1:2.11+dfsg-1ubuntu7.26
and, perhaps, mark it as "hold" if needed (as the 7.27 version focus in
an issue that could only be seen in aarch64 so far).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for the feedback.
It looks like this happens because of:
/*
* There cannot be two concurrent aio_poll calls for the same AioContext (or
* an aio_poll concurrent with a GSource prepare/check/dispatch callback).
* We rely on this below to avoid slow locked accesses to
On the same system and qemu command line options, I just tried my own
upstream build from git://git.qemu.org/qemu.git at commit
master:e7651153a8801dad6805d450ea8bef9b46c1adf5. I do not encounter the
error with this upstream build.
$ ~/qemu/bin/qemu-system-x86_64 --version
QEMU emulator version
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885419
Title:
QEMU
I too get this after an upgrade and I can add only a couple of things to
Viktor's report. I've tried both aio=native and aio=threads with same
result. Unlike Viktor, I'm using virtio-blk-pci with raw images.
With both aio=native and aio=threads:
qemu-system-x86_64:
22 matches
Mail list logo
