[Bug 1038055] Re: graphics fail to initialise correctly, in kvm with cirrus graphics (after LUKS install)

[Stefan Bader]

Testing today (on a Xen guest) showed that the X crash on unity startup
seems to be resolved. On the KVM side at least startup works, while I
get occasional crashed that look similar to the initial crash (maybe
that is a result of a slower machine trying to cope with llvm-pipe). But
in the light of that I would also tend to disable the kernel cirrus drm
driver (even more as this currently would only do anything for KVM).
That way we at least face the same stacks when running Xen and KVM
guests.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1038055

Title:
  graphics fail to initialise correctly, in kvm with cirrus graphics
  (after LUKS install)

Status in “cryptsetup” package in Ubuntu:
  Invalid
Status in “grub2” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Confirmed
Status in “plymouth” package in Ubuntu:
  Invalid
Status in “ubiquity” package in Ubuntu:
  Invalid

Bug description:
  reproducible with ubiquity or alternate installer in KVM virtual machine:
  1) select lvm + encrypted instalation

  
  it fails to boot, in a way that I get "no video mode activated" and I cannot type the password in to unlock the drive.

  As a workaround, I had to:
  1) force reboot machine
  2) then grub options come up
  3) select recovery mode
  4) then I can enter the password using text interface
  5) resume normal boot

  Disabling splash, brings up text interface to unlock the drive &
  allows to boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1038055/+subscriptions