Sounds like your problem only occurs on older versions of Ubuntu, so
moving this to the QEMU-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.
Can you still reproduce this issue with the latest version of QEMU
(currently v2.8)?
** 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/855800
Title:
FYI, the pa_features[24] setting has been fixed in upstream in a slightly
different way:
http://git.qemu-project.org/?p=qemu.git;a=commitdiff;h=bac3bf287ab60e264b6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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/785668
Title:
bonding inside a bridge does not update ARP correctly when bridged net
accessed from within a VM
To manage
Is there still something left to do here, 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 Ubuntu.
https://bugs.launchpad.net/bugs/1192499
Title:
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 Ubuntu.
This sounds like a distribution specific bug to me, so moving the bug to
QEMU-Ubuntu.
** 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/1254828
Title:
Sounds like this was an Ubuntu- or libvirt-specific bug ... so closing
this in the upstream QEMU bug tracker.
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Bug has also been reported here:
https://bugs.launchpad.net/qemu/+bug/1012023
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/921208
Title:
win7/x64 installer hangs on startup with 0x005d.
To
I think you need at least also the first patch that moves the code into
a separate function. Otherwise you'll have to resolve the conflicts
manually.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Patch 3efffc3292d9427 had been released with QEMU 2.5
** 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/1006655
Title:
Can't convert 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/1285363
Title:
qemu-aarch64-static segfaults
To manage notifications about this bug
** Changed in: qemu
Status: New => 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/741887
Title:
virsh snapshot-create too slow (kvm, qcow2, savevm)
To manage notifications about
Commit 0d34fbabc13 has been released with QEMU v2.8
** 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/1626972
Title:
QEMU memfd_create
** 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/1062220
Title:
qemu-system-arm crashed with SIGABRT in cpu_abort()
To manage
The QEMU versions mentioned in this ticket are quite old already ... can
you still reproduce this with the latest version of QEMU? If so, please
also provide the exact command line parameters that you used to start
QEMU, and the steps you took afterwards to get to the crash? Thanks!
** Changed
Since cirrus is not the prefered graphics card in QEMU anymore, and
there hasn't been any update to this within the last four years, I think
nobody will take care of this ticket anymore, so setting the status to
"Won't fix" now.
** Changed in: qemu
Status: Triaged => Won't Fix
--
You
Is there still an issue left here with upstream QEMU?
** Changed in: qemu
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/453617
Title:
kvm hangs at 100% cpu
Triaging old bug tickets... Can you still reproduce this behavior with
the latest version, or has the problem been fixed now?
** Changed in: qemu
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This sounds like a kernel bug, so it should not be tracked via the QEMU
bug tracker.
** 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/977391
Title:
BUG: soft lockup - CPU#8
Commit 0d34fbabc13 is upstream, so setting this to "Fix committed", too.
** Changed in: qemu
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626972
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/1285508
Title:
[ppa 2.0~git-20140225] mouse cursor invisible with Ubuntu live system
To manage notifications about this bug
If I get the last two comments right, the problem was only about the
Ubuntu PPA package, so I'm closing this for upstream QEMU, too. If you
still have problems with upstream QEMU here, please feel free to open
the ticket again.
** Changed in: qemu
Status: New => Invalid
--
You received
Can you still reproduce this issue with the latest upstream version of
QEMU?
** Changed in: qemu
Status: New => Confirmed
** Changed in: qemu
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed 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/990364
Title:
virtio_ioport_write: unexpected address 0x13 value 0x1
To manage notifications about this bug
Looking at comment #7, it sounds like you're not interested in this
ticket anymore, so I'm closing it as "Won't fix". Feel free to open it
again if you are still interested in this.
** Changed in: qemu
Status: New => Won't Fix
--
You received this bug notification because you are a
** 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/1433081
Title:
kvm hardware error 0x with vfio-pci VGA passthrough
To manage notifications about
Do you still have this problem with the latest released version of QEMU
(see http://wiki.qemu-project.org/Download)?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That "Debian 8.5 (64bit).vmdk" also works fine with the qemu-img from
upstream master branch ==> I'm closing this ticket now for upstream,
too.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This does not sound like a QEMU bug, so let's remove it from the QEMU
bug tracker
** 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/712416
Title:
kvm_intel kernel module
Is here still a problem left with 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/897750
Title:
libvirt/kvm problem with disk
Moving this to the Ubuntu-qemu bug tracker since you're apparently using
Ubuntu's QEMU, not the upstream QEMU.
** Project changed: qemu => qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
If I've got comment 27 right, the issue has also been fixed upstream, so
I'm setting the status now to "Fix released". If there's still something
left to do here, feel free to change it again.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because
** 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/1645287
Title:
Option "split" does not available for kernel_irqchip flag in qemu-
system-x86_64
To manage
** Changed in: qemu
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/925405
Title:
VNC server does not work with Mac Screen Sharing
To manage notifications
Since it has been fixed in Precise ... I assume this has also been fixed
in upstream QEMU? Or is there still anything left to do here?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
QEMU 2.0 is not maintained by the QEMU project anymore. Can you please
try again with the latest release of QEMU (v2.8)? ... otherwise you
should report this to the bug tracker of your distro instead.
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification
According to comment #3, this bug has been fixed, so I'm closing this
ticket now. If you can still reproduce this issue with the latest
version from QEMU, please feel free to open this ticket again.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification
Please do not report distribution specific bugs (since you're using
qemu-kvm 2.0.0+dfsg-2ubuntu1.27) against the QEMU project bugtracker -
use the distribution's bugtracker instead.
** Project changed: qemu => qemu (Ubuntu)
--
You received this bug notification because you are a member of
** 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/1201447
Title:
Blue screen when disk uses cache='writeback'
To manage notifications about this bug go to:
Please make sure to use the right target for downstream bugs ==> Re-
assigned this to qemu-ubuntu
** 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/1706058
** 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/1610368
Title:
qemu-system-x86_64 read acces DENIED in apparmor
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/1682681
Title:
qemu 2.5 network model rtl8139 collisions Ubuntu 16.04.2 LTS
To manage notifications about
Moving to QEMU-Ubuntu since you're not using upstream QEMU (and the bug
should have been fixed there as pointed out by Hervé on the qemu-devel
mailing list).
** Project changed: qemu => qemu (Ubuntu)
--
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/1357226
Title:
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
To manage notifications
The patch with CPUID_DE has apparently been included here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=b6c5a6f021f485fc36
So has this issue now been fixed in the current version of QEMU?
** Changed in: qemu
Status: Confirmed => Incomplete
--
You received this bug notification because
https://bugzilla.kernel.org/show_bug.cgi?id=46711 is marked as
WILLNOTFIX, so I'm closing the QEMU bug here, too.
** Changed in: qemu
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK, got your point ... but AFAIK the vmware display device in QEMU is
pretty much unmaintened anyway, so unless someone steps up and takes
care of this device, I think the WONT-FIX status is appropriate for this
bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
If I get the previous comments right, this is just about using the right
configuration, and not a real bug? If so, I assume we can close this
ticket nowadays?
** Changed in: qemu
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
OK, since there hasn't been a reply within 6 months, I assume this is
now fixed. So closing this ticket now.
** 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.
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917824
Title:
qemu loops/hangs on extending qcow2-diskspace
To manage notifications about this bug
Did anybody ever tried to reproduce this bug with 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/1297487
Title:
MTU not honored
Can you still reproduce this problem with the latest version of QEMU
(currently version 2.9.0)?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Have you tried whether it works with the latest upstream version of QEMU
(currently version 2.9) - since you've marked this as upstream QEMU
problem, too?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I think this has been fixed by this commit here:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=d139e9a6cf01b8c31f59
... so closing this ticket now.
** Changed in: qemu
Status: New => Fix Released
--
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/1721468
Title:
Free invalid pointer crash in vnc
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/1691109
Title:
qemu-kvm not working as nested inside ESX 6.0
To manage notifications about this bug go 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
There hasn't been any comment about upstream QEMU within the last
months, so I assume this has been fixed there, too. Closing...
** Changed in: qemu
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
There hasn't been a reply to my question in the last comment within
months, so I assume this has been fixed in upstream, too. Closing this
ticket now...
** Changed in: qemu
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
There hasn't been a reply to my question in the last comment within
months, so I assume nobody cares about this anymore. So I'm closing this
ticket now...
** Changed in: qemu
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs,
There hasn't been a reply to my question in the last comment within
months, so I assume nobody cares about this anymore. So I'm closing this
ticket now...
** Changed in: qemu
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs,
There hasn't been a reply to my question in comment #32 within
months, so I assume nobody cares about this anymore. So I'm closing this
ticket now...
** Changed in: qemu
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Since the fix mentioned in the previous comments is already in upstream
QEMU, I'm setting the upstream status to "Fix released".
** 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.
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/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
** 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
Please always use the latest version of QEMU (currently v2.10, soon
v2.11) when reporting bugs to the upstream QEMU project - we don't
support old versions like v2.5 any more. So I guess you wanted to report
a bug agains v2.5 in Ubuntu instead and I changed the target of this bug
accordingly.
**
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
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
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
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
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
** 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
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
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug
Fix had been included here:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=e9d21c436f716603b3
** 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.
** 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/1288259
Title:
KVM vms are paused and cannot be deleted due to hardware error 0x0
To manage notifications
Since there hasn't been a reply within the last 5 months, I assume this
has been fixed and thus close now this ticket accordingly.
** Changed in: qemu
Status: Incomplete => Fix Released
--
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
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: 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
** 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
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/1392504
Title:
libvirt not relabeling devices on USB Passthrough
To manage notifications about this bug go
** 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
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.
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
** 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-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
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 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
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.
1 - 100 of 172 matches
Mail list logo