Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 861821[details]
A screenshot
Description of problem:
I just get a black screen.
Version-Release number of selected component (if applicable):
gnome-boxes-3.8.3-2.el7.x86_64
qemu-kvm-1.5.3-19.el7.x86_64
How reproducible:
Always.
Steps to Reproduce:
1. Click "new"
2. Select image http://releases.ubuntu.cz//precise/ubuntu-12.04.4-desktop-i386.iso
Actual results:
Black screen.
Expected results:
Purple screen.
Likely buggy QXL driver on Ubuntu. Could you check if following hack makes it work (after creating the VM):
* virsh list --all (So you can find the name of domain)
* virsh edit DOMAIN
* find 'qxl' device
* replace 'qxl' with 'vga' and remove other attributes of 'model' node and 'address' node too.
* See if that helps.
If it helps, its an ubuntu/qxl bug and there isn't much we can do other than reporting it.
> If it helps, its an ubuntu/qxl bug and there isn't much we can do other than reporting it.
From irc discussion, there actually is something we can do: adjust our stored configs so that we automatically choose vga if we recognize a version of ubuntu that is known to have a buggy qxl driver.
Replacing QXL with VGA really fixes the issue.
By the way, there's a few things to note:
* Ubuntu ships the qxl kernel module, but not the X11 driver -- vesa is loaded instead
* The hang happens only when plymouth is run (removing "splash" parameter or adding "console=ttyS0" works around the issue)
Unfortunately, this means I have no logs -- the hang happens prior to root mount, so there's no logs and once I try to get verbose output things start to work.
If I install the qxl x11 driver (which involves complete update of the X11 stack with one with different ABI, so that the other drivers get removed -- wtf) it reproducely hangs almost instantly. I'd say it's safe to assume this Ubuntu release just won't work with QXL anyway.