There were some fixes in QEMU v6.1. Please try that one to see whether
it solves your problem, too.
** Project changed: qemu => qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945540
@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)
** Changed in: qemu (Ubuntu)
Status: Confirmed => Incomplete
** Bug watch removed: Red Hat Bugzilla #1568939
https://bugzilla.redhat.com/show_bug.cgi?id=1568939
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Since there wasn't a reply to my question since more than half a year,
I'm assuming that this does not affect upstream QEMU anymore. Thus I'm
removing upstream QEMU from this ticket now.
** No longer affects: qemu
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 132720 ***
https://bugs.launchpad.net/bugs/132720
** No longer affects: qemu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/206818
Title:
qemulator.py crashed
*** This bug is a duplicate of bug 530077 ***
https://bugs.launchpad.net/bugs/530077
** No longer affects: qemu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/490484
Title:
running 64bit client
*** This bug is a duplicate of bug 391879 ***
https://bugs.launchpad.net/bugs/391879
** No longer affects: qemu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/391880
Title:
migrate exec hangs
The patch for QEMU that has been mentioned in comment #38 has been
merged already, so I'm marking this as Fix-Released there.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Is there still anything left to do here for upstream QEMU?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894804
Title:
Second DEVICE_DELETED
Do you still get the warning with the latest version of QEMU (v6.0)?
** Changed in: qemu
Status: New => Incomplete
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Since you were talking about Ubuntu, I moved this to the Ubuntu tracker
now. If you can reproduce the problem with upstream QEMU (currently
v6.0), then please open a new ticket in the new QEMU issue tracker at
gitlab.com.
** Project changed: qemu => qemu (Ubuntu)
--
You received this bug
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877052
Title:
KVM Win 10 guest pauses after kernel upgrade
To manage notifications about this
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/144
** Changed in: qemu
Status: New => Expired
** Bug
Thanks for opening the new ticket. Let's close this one here as WontFix
- since we will only look at the new issue now instead.
** Changed in: qemu
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Looking at the comments, it seems to me that this was an issue in VTE
that got fixed. Is there still anything left to do for upstream QEMU
here?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/118
** Changed in: qemu
Status: Triaged => Expired
** Bug
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/113
** Changed in: qemu
Status: New => Expired
** Bug
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/103
** Changed in: qemu
Status: Confirmed => Expired
**
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/102
** Changed in: qemu
Status: Confirmed => Expired
**
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/95
** Changed in: qemu
Status: Confirmed => Expired
** Bug
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/88
** Changed in: qemu
Status: Confirmed => Expired
** Bug
The QEMU project is currently considering to move its bug tracking to
another system. For this we need to know which bugs are still valid
and which could be closed already. Thus we are setting older bugs to
"Incomplete" now.
If you still think this bug report here is valid, then please switch
the
This bug report has been moved to QEMU's new bug tracker on gitlab.com
and thus gets now closed in Launchpad. Please continue with the
discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/66
** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #66
The QEMU project is currently considering to move its bug tracking to another
system. For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch
** Tags added: block
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/304636
Title:
-hda FAT:. limited to 504MBytes
To manage notifications about this bug go to:
This sounds like a bug in the packaging of Ubuntu, so I've moved it to
the Ubuntu tracker
** Project changed: qemu => qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822012
Title:
** No longer affects: qemu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920784
Title:
qemu-system-ppc64le fails with kvm acceleration
To manage notifications about this bug go to:
Pedro,
please also note that vvfat driver is general in a bad state and more or less
completely unmaintaind. I can only strongly recommend to *not* use it in
production. If you have to share files between guest and host, please use
something more modern like virtio-fs (or maybe virtio-9p)
Can you provide a link to the test case that you used? Otherwise, can
you try to bisect the problem? Can you please also try with the latest
version of QEMU? v4.0 is rather old already.
** Information type changed from Public Security to Public
** Changed in: qemu
Status: New =>
Closed by accident, Christian just told me that this is not fixed yet.
Sorry for the inconvenience.
** Changed in: qemu
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Released with QEMU v5.2.0.
** Changed in: qemu
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1336794
Title:
9pfs does not honor open file handles on
** Project changed: qemu => qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906155
Title:
USB Passthrough Fails on Start, Needs domain Reset
To manage notifications about this bug go
Sorry, since nobody seems to have capacity to work on this, it's
unlikely that this will ever be implemented in QEMU. Thus I'm closing
this as WontFix for now.
** Changed in: qemu
Status: New => Won't Fix
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Invalid
--
You
The QEMU project is currently considering to move its bug tracking to another
system. For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch
It's been a while since the last change to this ticket ... Has this ever
been implemented?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1163034
Title:
linux-user mode can't handle guest setting a
The QEMU project is currently considering to move its bug tracking to another
system. For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch
*** This bug is a duplicate of bug 1738972 ***
https://bugs.launchpad.net/bugs/1738972
** This bug has been marked a duplicate of bug 1738972
[A] KVM Windows BSOD on 4.13.x
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: btrfs-progs (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877418
Title:
qemu-nbd freezes access to VDI file
To manage notifications about
Ok, so I'm moving this to the Ubuntu bug tracker.
** Project changed: qemu => qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901440
Title:
Instability in IVSHMEM after updating QEMU
Is there still an issue left here for upstream QEMU?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1718719
Title:
qemu can't capture keys
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867519
Title:
qemu 4.2 segfaults on VF detach
To manage notifications about this bug
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886811
Title:
systemd complains Failed to enqueue loopback interface start request:
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883984
Title:
QEMU S/390x sqxbr (128-bit IEEE 754 square root) crashes qemu-system-
Looking through old bug tickets... is this still an issue with the
latest version of QEMU? Or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
** Changed in: qemu (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification
Looking through old bug tickets... is this still an issue with the
latest version of QEMU, or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: qemu-kvm (Ubuntu
** Changed in: qemu
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1390520
Title:
virtual machine fails to start with connected audio cd
To manage notifications
** Project changed: qemu => qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859656
Title:
[2.6] Unable to reboot s390x KVM machine after initial deploy
To manage notifications about
** Project changed: qemu => qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851552
Title:
since ubuntu 18 bionic release and latest, the ubuntu18 cloud image is
unable to boot up on
If it's reproducible with real hardware, then it's definitely not a bug
of QEMU ==> Removing QEMU from this bug ticket.
** No longer affects: qemu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Project changed: qemu => libvirt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633508
Title:
libvirt cannot hot insert interfaces to qemu
To manage notifications about this bug go to:
Patch a0e2251132995b9 is a kernel patch, thus this is certainly not
something we need to track in the upstream QEMU bugtracker.
** No longer affects: qemu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1842774 ***
https://bugs.launchpad.net/bugs/1842774
** No longer affects: qemu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842916
Title:
[18.04 FEAT]
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834113
Title:
QEMU touchpad input erratic after wakeup from sleep
To manage notifications about
** No longer affects: qemu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838312
Title:
Qemu virt-manager Segmentation fault
To manage notifications about this bug go to:
** Project changed: qemu => qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829945
Title:
SDL support missing from qemu-1:3.1+dfsg-2ubuntu3.1
To manage notifications about this bug go
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815889
Title:
qemu-system-x86_64 crashed with signal 31 in
Fix had been included here (in QEMU v3.1 already):
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=7294e600eb814fd2
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think this has been fixed in QEMU v2.10.0 with this commit here:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=0a9667ecdb6d7da90a2ef64
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I haven't tried, but I think this should be fixed now with the new
elevateprivileges parameter of the -sandbox option. Have you tried to
reproduce the problem with the latest version of QEMU already?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification
** No longer affects: qemu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823152
Title:
QEMU not able to boot ubuntu 18.04 as a guest
To manage notifications about this bug go to:
Since support for SDL 1.2 has been removed from QEMU now, can you still
reproduce this issue with the latest version of QEMU and SDL2 ?
** Changed in: qemu
Status: Triaged => Incomplete
** Changed in: qemu-kvm (Ubuntu)
Status: Triaged => Incomplete
** Bug watch removed:
Can you still reproduce this problem with the latest version of upstream
QEMU?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1562653
Title:
** No longer affects: qemu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818880
Title:
Deadlock when detaching network interface
To manage notifications about this bug go to:
At least please try to answer my questions in comment #3: Is
virtualization enabled in your BIOS? Is KVM enabled on your system (i.e.
are the kvm.ko and kvm_intel.ko or kvm_amd.ko modules loaded)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Jeb, if you open a bug against QEMU here, we expect some information how
QEMU is run. If you only interact with Gnome Boxes, then please only
open a bug against Boxes - best in their Bug tracker here:
https://bugzilla.gnome.org/ ... I guess nobody of the Boxes project is
checking Launchpad, so
And for the CLI parameters, you could run this in a console window for
example, after starting your guest:
ps aux | grep qemu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734810
Title:
Windows
** Project changed: qemu => qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797332
Title:
qemu nested virtualization is not working with Ubuntu16.04
To manage notifications about this
** Changed in: qemu
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1486278
Title:
'info vnc' monitor command does not show websocket information
To manage
Looking through old bug tickets... can you still reproduce this issue
with the latest upstream version of QEMU? Or could we close this ticket
nowadays?
** Changed in: qemu
Status: New => Incomplete
** Changed in: llvm-toolchain-3.6 (Ubuntu)
Status: New => Incomplete
** Changed
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: debian
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1180777
Title:
RDP
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/965867
Title:
9p virtual file system on qemu slow
To manage notifications
Closing for QEMU since there hasn't been any response within a year.
** Changed in: qemu
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297487
Title:
MTU not
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755912
Title:
qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl
To
Christian, what happened to the upstream patch? Looks like it never got
included? Could you please poke the maintainer, so we could finally
close this bug for upstream, too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looking through old bug tickets... can you still reproduce this issue
with the latest version of QEMU? Or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Project changed: qemu => qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1463909
Title:
virtio: networking not working when guest's eth0 is not in promiscuous
mode
To manage
Could you please check with the latest version of QEMU (v2.12), and make
sure that you're using SDL2 instead of SDL1.2 (since the latter is going
to be removed soon)?
** Changed in: qemu (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
If you don't provide the CLI parameters, there's no way we can help
here, sorry. So marking this as "invalid" for the QEMU project.
** Changed in: qemu
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353947
Title:
Hypervisor with QEMU-2.0/libvirtd 1.2.2 stack when launching VM
If the host kernel crashes, this is certainly rather a KVM bug than a
QEMU bug, so you should report this to the KVM / kernel mailing list
instead of opening an (upstream) QEMU bug ticket.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740219
Title:
static linux-user ARM emulation has several-second startup time
To
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/855800
Title:
KVM crashes when attempting to restart migration
To manage
Looking through old bug tickets... is there anything left to do here? Or
should we rather close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
** Changed in: qemu-kvm (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are
Ok, closing this for upstream, too, according to the previous comments.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481272
Title:
** Project changed: qemu => qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754597
Title:
qemu-system-x86_64 broken on ubuntu 17.10
To manage notifications about this bug go to:
Which command line parameters are passed to QEMU? Is your system able to
use KVM (e.g. did you enable virtualization support in your BIOS)?
** Changed in: qemu
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Fix has been released with QEMU 2.11:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=a8b154a637b586441b
** Changed in: qemu
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: qemu
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1254786
Title:
qemu-m68k-static: illegal instruction ebc0 during debootstrap second
** Project changed: qemu => qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1392504
Title:
libvirt not relabeling devices on USB Passthrough
To manage notifications about this bug go
Triaging old bug tickets... can you still reproduce this issue with the
latest version of QEMU? There should now be support for "normal" 68k
CPUs, too...
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Project changed: qemu => qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1449687
Title:
block migration of qcow2 VMs copies all empty space
To manage notifications about this bug go
Triaging old bug tickets... can you still reproduce this issue with the
latest version of QEMU? Or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Closing this bug for QEMU, since there haven't been any replies within
the last 7 months.
** Changed in: qemu
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: qemu
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1162644
Title:
qemu-system-x86_64 crashed with SIGABRT in __assert_fail_base()
To manage
Triaging old bug tickets... can you still reproduce this issue with the
latest version of QEMU? Or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Triaging old bug tickets... can you still reproduce this issue with the
latest version of QEMU? Or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1350435
Title:
tcg.c:1693: tcg fatal error
To manage notifications about this bug go
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711602
Title:
--copy-storage-all failing with qemu 2.10
To manage notifications
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1077116
Title:
automoc4 segfaults when building in an armhf pbuilder on an amd64 host
Looks like the fix has been included in QEMU's sgabios repository here:
https://git.qemu.org/?p=sgabios.git;a=commitdiff;h=cbaee52287e5f32373181cf
And the binary in the QEMU repository has been updated here:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=c8c33fca88fc3ab8a5e4b
So this fix is
1 - 100 of 172 matches
Mail list logo
