[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1336801
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1336801
Title:
12.04 guest
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
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
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
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 Ubuntu
Server Team, which is subscribed to qemu 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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 Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1336801
Title:
12.04 guest hangs on a 14.04 host server with cirrus
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]
Getting a working console is quite hit-or-miss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1336801
Title:
12.04 guest hangs on a 14.04 host server with cirrus graphics
To manage notifications
I can reproduce the console not being useful, however I can ssh into the
VM. Syslog shows:
[7.296919] fb: conflicting fb hw usage cirrusdrmfb vs EFI VGA - removing
generic driver
[7.433222] [drm:cirrus_vram_init] *ERROR* can't reserve VRAM
[7.433234] cirrus :00:02.0: Fatal error
Getting a working console is quite hit-or-miss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1336801
Title:
12.04 guest hangs on a 14.04 host server with cirrus graphics
To manage notifications
A subsequent (clean) reboot results in a working console.
So it sounds like qemu is not properly resetting its hardware during the
first reboot.
** Changed in: libvirt (Ubuntu)
Status: New = Triaged
** Changed in: libvirt (Ubuntu)
Importance: High = Medium
--
You received this bug
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1336801
Title:
12.04 guest hangs on a 14.04 host server with cirrus graphics
To
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]
15 matches
Mail list logo
