Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1056284 - Solaris 11 fails to install with BAD TRAP
Summary: Solaris 11 fails to install with BAD TRAP
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: qemu
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Fedora Virtualization Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-21 21:29 UTC by Richard W.M. Jones
Modified: 2014-01-21 21:31 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-21 21:31:56 UTC


Attachments (Terms of Use)
solaris.png (deleted)
2014-01-21 21:29 UTC, Richard W.M. Jones
no flags Details

Description Richard W.M. Jones 2014-01-21 21:29:22 UTC
Created attachment 853462 [details]
solaris.png

Description of problem:

I know we don't care about this.  I'm just recording this
here along with the failure so that there will be more than
1 hit on Google for this bug.

Version-Release number of selected component (if applicable):

sol-11_1-text-x86.iso
qemu-1.6.1-3.fc20.x86_64

How reproducible:

100%

Steps to Reproduce:

virt-install -n solaris-11 \
  --disk path=/dev/fedora/solaris-11 \
  --cdrom /tmp/sol-11_1-text-x86.iso \
  --os-variant solaris11 \
  --cpu=host --vcpus=1 \
  -r 2048

Actual results:

panic[cpu0]/thread=...: BAD TRAP: type=d (#gp General protection) [...]

Stack trace:
unix:real_mode_stop_cpu_stage2_end+bb22 )(
unix:trap+3b2 ()
unix:cmntrap+e6 ()
unix:rdmsr+2 ()
unix:cpupm_init+7e ()
genunix:main+1d6 ()
unix:_locore_start+90 ()

Additional info:

See attached image.

Comment 1 Richard W.M. Jones 2014-01-21 21:31:25 UTC
Hmm, *removing* --cpu=host gets past this error.


Note You need to log in before you can comment on or make changes to this bug.