Upstream QEMU bugs are now tracked on https://gitlab.com/qemu-
project/qemu/-/issues - so if you can reproduce it with the latest
version from upstream QEMU, please report it there.
** No longer affects: qemu
--
You received this bug notification because you are a member of qemu-
devel-ml, which
I am consistently hitting this when trying to install the Ubuntu arm64
ISO image in a VM. A minimal command line that reproduces the problem is
(host system is jammy arm64):
qemu-system-aarch64 -enable-kvm -m 2048 -M virt -cpu host -nographic
-drive file=flash0.img,if=pflash,format=raw -drive
file
No, as I described in great detail it has nothing to do with the attached
devices.
I just noticed that the bug was excused away
as being do to the “slow” RPi 4. I’ll share that I originally hit it
on Apple’s M1 but as I expect my environment might be too unusual I replicated
it on RPi 4. I have s
I've been having crashes with the same assertion message, when trying to
run Windows 10 ARM under a VM. But I finally figured out that what's
actually crashing it is not the fact that it's Windows, it's the fact
that I was attaching the virtual drive via virtual USB.
If I do the same thing to an
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1921664
Title:
Coroutines
[Expired for qemu (Ubuntu) because there has been no activity for 60
days.]
** Changed in: qemu (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1921664
Ti
Hmm, thanks for the hint Thomas.
Of the two formerly referenced same-source different result builds:
[1] => built 2021-03-23 in Hirsute => works
[2] => built 2021-04-12 in Hirsute => fails
[1]:
https://launchpad.net/ubuntu/+source/qemu/1:5.2+dfsg-9ubuntu1/+build/21196422
[2]:
https://launchpad
@Christian & Tommy : Could you please check whether the problematic
binaries were built with link-time optimization, i.e. with -flto ? If
so, does the problem go away when you rebuild the package without LTO?
** Changed in: qemu
Status: New => Incomplete
** Changed in: qemu (Ubuntu)