[SeaBIOS] [Qemu-devel] solaris x86 in qemu? [bisected]

Kevin O'Connor kevin at koconnor.net
Sun Jun 16 17:30:12 CEST 2013


On Sun, Jun 16, 2013 at 02:07:39PM +0400, Michael Tokarev wrote:
> 14.06.2013 03:47, Kevin O'Connor wrote:
> > On Fri, Jun 14, 2013 at 12:32:22AM +0400, Michael Tokarev wrote:
> >> 13.06.2013 11:51, Michael Tokarev wrote:
> >>> In order to verify some build issues on solaris, I tried to install
> >>> sol10 x86 in a kvm vm.  But unfortunately it does not work: after the
> >>> grub prompt and choosing "Solaris 10 x86" boot entry, the kernel
> >>> gets loaded (there's a row of dots displayed during that), next,
> >>> the following message gets displayed:
> >>>
> >>>  SunOS Release 5.10 Version Generic_147148-26 64-bit
> >>>  Copyright (c) 1983, 2013 Oracle and/or its affiliates.  All rights reserved.
> >>>
> >>> and the guest stays there for a long time, spinning up 100% of its CPU,
> >>> and nothing more happens.
> > 
> > Can you try with the latest seabios release (v1.7.2.2)?  There have
> > been other changes to the dsdt that may have corrected your issue.
> 
> So, with the knowlege that current 1.7.2.2 does not change this, can we
> guess what's going on there?  I don't really know solaris kernel internals
> (is the source available to start with?), but maybe this particular commit
> may give some hint?

Unfortunately not.  There was nothing special about the DSDT changes
in that commit.  Likely the AML interpretter in Solaris is quirky and
one of the clauses in that commit (or some arrangement of clauses) is
confusing Solaris.  This is one of the unfortunate parts of ACPI -
despite the lengthy specification each implementation of ACPI is
different and it's painful to come up with AML code that runs on
multiple platforms.

You could try disabling acpi entirely.

You could also try iterating through the parts of that commit and
commenting out various DSDT entries until you find which one is
aggravating Solaris.

-Kevin



More information about the SeaBIOS mailing list