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.

Bug 1063899

Summary: Solaris 11 does not boot
Product: Red Hat Enterprise Linux 8 Reporter: Lubomir Rintel <lkundrak>
Component: gnome-boxesAssignee: Felipe Borges <feborges>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.3CC: berrange, feborges, lkundrak, lrintel, mclasen, scorcora, vbenes
Target Milestone: rcKeywords: Reopened
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-19 11:17:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshot none

Description Lubomir Rintel 2014-02-11 15:39:43 UTC
Created attachment 861820 [details]
Screenshot

Description of problem:

Solaris 11 panicks upon start.

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://download.oracle.com/otn/solaris/11_1/sol-11_1-live-x86.iso

Actual results:

A panic.

Expected results:

Not sure what did I expect.

Comment 2 Zeeshan Ali 2014-02-12 19:44:52 UTC
Could you please try with virt-manager and see if it works there? If it does, can you please try this:

https://bugzilla.redhat.com/show_bug.cgi?id=1063900#c2

Comment 3 Lubomir Rintel 2014-02-13 11:09:23 UTC
It does not work either and replacing QXL GPU with VGA does not change that.

On the other hand, replacing <cpu mode='host-model'> (which sets -cpu SandyBridge to qemu-kvm on my machine) with <cpu mode='custom' match='exact'<model fallback='allow'>cpu64-rhel6</model> fixes the panic.

Unfortunately, it runs out of memory quickly with default of 512M. Changing that to 1024M makes it boot to the desktop.

In the desktop, mouse cursor does not move. Removing the USB tablet and leaving the PS/2 mouse attached fixes this problem.

The boot is ridiculously slow, but the desktop works mostly fine then. I verified this problem exists on real hardware too, so that's nothing related to Boxes or QEMU.

So, to summarize, the following needs to be done to make Solaris work:

* Avoid CPU being set to SandyBridge
* Assign 1024M of memory
* Remove USB Tablet

Comment 6 Zeeshan Ali 2015-04-15 12:40:17 UTC
(In reply to Lubomir Rintel from comment #3)
>
> * Avoid CPU being set to SandyBridge

Are you sure SanyBridge is the issue? Could you please test this config:

  <cpu mode='custom' match='exact'>
    <model fallback='allow'>SandyBridge</model>

Thats what Boxes has been using lately (3.14).

> * Assign 1024M of memory

We do that by default now too.

> * Remove USB Tablet

That is something that still needs doing: https://bugzilla.gnome.org/show_bug.cgi?id=747910

Comment 7 Vladimir Benes 2015-05-06 10:18:08 UTC
I've just checked solaris 11.2 (the newest) and gnome-boxes 3.14.3 and the crash still occurs.

Comment 10 Zeeshan Ali 2015-05-29 19:02:43 UTC
Daniel, would you have any ideas about this?

Comment 11 Zeeshan Ali 2015-05-29 19:07:29 UTC
(In reply to Zeeshan Ali from comment #6)
> (In reply to Lubomir Rintel from comment #3)
> >
> > * Avoid CPU being set to SandyBridge
> 
> Are you sure SanyBridge is the issue? Could you please test this config:
> 
>   <cpu mode='custom' match='exact'>
>     <model fallback='allow'>SandyBridge</model>

Just FYI, the "SandyBridge" part is not hard coded by Boxes but rather Boxes uses the model libvirt capabilities report to be the host cpu model.

Comment 15 Felipe Borges 2019-11-14 16:00:32 UTC
I have been attempting to fix this issue. So far I am encountering the same limitations specified in https://www.linux-kvm.org/page/Guest_Support_Status

Comment 16 Felipe Borges 2020-09-16 12:40:25 UTC
I am tracking the progress on this issue upstream at https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/600

Comment 20 RHEL Program Management 2020-09-19 00:10:01 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 25 Red Hat Bugzilla 2023-09-14 02:03:29 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days