[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/1336801
Title:
12.04 guest
[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/1336801
Ti
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 qemu-
devel-ml, which is subscribed to QE
The errors about the frame buffer device happen because grub is started in
graphical mode and then the boot wants to replace the framebuffer device/driver
while plymouth still holds it. I thought we should have fixed this before
release by adding cirrus to the list of graphics that should get in
I'm also having issues with libvirt/kvm guests becoming unresponsive and
they were all using cirrus as their video model. I've tried switching
some to vga to see if that helps.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://b
Actually I suppose this could be a seabios bug? (I am on 1.7.4-4)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1336801
Title:
12.04 guest hangs on a 14.04 host server with cirrus graphics
Statu
Note that on a successful boot, dmesg | grep cirrus shows:
[9.064581] fb: conflicting fb hw usage cirrusdrmfb vs EFI VGA - removing
generic driver
[9.133808] fbcon: cirrusdrmfb (fb0) is primary device
[9.431359] cirrus :00:02.0: fb0: cirrusdrmfb frame buffer device
[9.431362]
