A comment in a duplicate bug of this states the following:

"Virsh adds video as default like:
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' 
primary='yes'/>
    </video>

Matched the cmdline: -device qxl-vga

The default of libvirt is:
    <video>
      <model type='cirrus' vram='16384' heads='1' primary='yes'/>
    </video>

Matches the cmdline: -device cirrus-vga,id=video0

Switching back to the default cirros graphics console makes it working
again.

Also type='vga' which matched qemu-cmdline "std" works.
So both qemu defaults (cirrus = old, vga = new), and the libvirt default 
(cirrus) work.
But the qxl as selected by virt-manager fails."

So it seems like this problem will only occur if virt-manager is used to
create the virtual machine.  Am I understanding that correctly?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1711358

Title:
  20170817 - ISO hangs on boot on qemu with splash screen enabled and
  qxl graphics driver

Status in linux package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  Test Case
  1. Boot artful desktop 20170817 under qemu with qxl
  2. Wait until ubiquity-dm is displayed

  Expected result
  It boots

  Actual result
  It hangs on the splash screen and the dots below the Ubuntu logo are not 
blinking. If the option 'splash' is removed from the boot command line it boots 
successfully.

  It also boots successfully with -vga std but in this case the splash
  screen is in text mode not graphical unlike with the qxl driver.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to