From: Avi Kivity <avi@redhat.com>
To: g3vbv@blueyonder.co.uk
Cc: linux-kernel@vger.kernel.org, Sid Boyce <sboyce@blueyonder.co.uk>,
KVM list <kvm@vger.kernel.org>
Subject: Re: OpenSolaris boot failure with KVM and VirtualBox
Date: Sun, 26 Jul 2009 19:13:55 +0300 [thread overview]
Message-ID: <4A6C80C3.8090007@redhat.com> (raw)
In-Reply-To: <4A5ED714.7010304@blueyonder.co.uk>
On 07/16/2009 10:30 AM, Sid Boyce wrote:
> I first tried using kernel 2.6.31-rc1 on openSUSE 11.2 Milestone1 on a
> 4P box. All other VM's, Windows and Linux work, currently running
> openSUSE 11.2 Milestone 3 with 2.6.31-rc3. Verified the .iso is good.
> Error message
> =============
> Booting 'OpenSolaris 2009.06'
> kernel$ /platform/i86pc/kernel/$ISADIR/unix
> loading '/platform/i86pc/kernel/$ISADIR/unix' ...
> cpu: 'AuthenticAMD' family 16 model 4 step 2 ...
> [BIOS accepted mixed-mode target setting!]
> [Multiboot-kernel, loadaddr=0xbffe38, text-and-data=0x1b1ff0, bss=0x0,
> entry=0xc00000]
> 'platform/i86pc/kernel/amd64/unix' is loaded
> module$ /boot/$ISADIR/x86.microroot
> loading '/boot/$ISADIR/x86.microroot' ...
> Error 15: File not found
> Press any key to continue ...
> Regards
> Sid.
>
Please copy kvm@vger.kernel.org on kvm issues.
Is this a regression from previous kernel versions? What userspace are
you using?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-07-26 16:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 7:30 OpenSolaris boot failure with KVM and VirtualBox Sid Boyce
2009-07-26 16:13 ` Avi Kivity [this message]
2009-07-26 16:48 ` Heinz Diehl
2009-07-26 18:14 ` Sid Boyce
2009-07-26 18:18 ` Avi Kivity
2009-07-26 21:59 ` Sid Boyce
2009-07-27 5:36 ` Alexander Graf
2009-07-27 11:11 ` Sid Boyce
[not found] ` <8A7B7BFF-9561-478A-898F-DD7031558960@suse.de>
2009-07-27 11:28 ` Sid Boyce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A6C80C3.8090007@redhat.com \
--to=avi@redhat.com \
--cc=g3vbv@blueyonder.co.uk \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyce@blueyonder.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.