qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Celso Pinto <cpinto@yimports.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Solaris (9 and 10) supported on 0.6.1?
Date: Thu, 21 Apr 2005 22:53:29 +0100	[thread overview]
Message-ID: <1114120409.22555.4.camel@lair> (raw)
In-Reply-To: <20050421134556.QCMV6521.lakermmtao02.cox.net@smtp.east.cox.net>

[-- Attachment #1: Type: text/plain, Size: 2263 bytes --]

Hi,

thanks a lot for your insight. I just pulled the source from CVS and
applied the mentioned patch but had no luck (tried running qemu both
with and without -isa). It keeps bumping on the "cannot mount root"
error and reboot automatically again and again.

Looking at the message output, it seems that there are problems when
mounting the root using the CDROM. I'll try to download the images again
and see how that goes.

Thanks a lot for your help.

Cheers,
Celso


On Thu, 2005-04-21 at 09:45 -0400, Ben Taylor wrote:
> "Celso Pinto" <cpinto@yimports.com>
> > 
> > I noticed on the website that Solaris is a supported guest OS so I took a
> > shot at trying to install them without much luck.
> > 
> > The installed keeps panic-ing stating it cannot mount root (screenshot:
> > http://yimports.com/~cpinto/downloads/qemu/Screenshot-1.png).
> 
> the failure of not mounting the root file system maybe 
> a symptom of a failed iso copy.  However, it's entirely
> possible that qemu is choking on the dma commands that
> Solaris is sending down to the virtual driver, and
> causing the problem.  There are some patches that Juergen
> Keil posted in the archive which can probably help that
> particular issue.  
> 
> > 
> > I used the command:
> > % qemu -hda <img created for hda> -cdrom <iso for solaris install> -d
> > int,pcall -boot d <img created for hda>
> 
> I looked at my start line and it looks like you have
> both -hda solaris10, and solaris10 at the end of your
> command line.  How about removing the trailing solaris10
> and see how that goes.   I think you probably want to
> add -localtime to the start command as well. Yes, you'll
> probably see some RTC errors when Solaris starts, 
> but I've gotten Solaris 10 to load with the CVS code
> plus Solaris patches.
> 
> > but only an empty log file was created on /tmp. Is there any alternative
> > to provide more information about this issue?
> 
> 
> stop qemu, add the log entries from the monitor, and
> continue?
> 
> Ben
> 
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
-- 
Celso Pinto <cpinto@yimports.com>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-04-21 21:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21 13:45 [Qemu-devel] Solaris (9 and 10) supported on 0.6.1? Ben Taylor
2005-04-21 21:53 ` Celso Pinto [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-22  8:32 Juergen Keil
2005-04-22  9:33 ` emuls
2005-04-22 10:11 ` Celso Pinto
2005-04-21 13:08 Celso Pinto
2005-04-21 13:16 ` Karel Gardas

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=1114120409.22555.4.camel@lair \
    --to=cpinto@yimports.com \
    --cc=qemu-devel@nongnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).