From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1RXNG8-0000Kp-H9 for garchives@archives.gentoo.org; Mon, 05 Dec 2011 01:22:20 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2C30421C092; Mon, 5 Dec 2011 01:22:10 +0000 (UTC) Received: from svr-us4.tirtonadi.com (svr-us4.tirtonadi.com [69.65.43.212]) by pigeon.gentoo.org (Postfix) with ESMTP id D7D4521C053 for ; Mon, 5 Dec 2011 01:20:26 +0000 (UTC) Received: from mail-ww0-f53.google.com ([74.125.82.53]) by svr-us4.tirtonadi.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.69) (envelope-from ) id 1RXNEI-0048Kg-M2 for gentoo-user@lists.gentoo.org; Mon, 05 Dec 2011 08:20:26 +0700 Received: by wgbds1 with SMTP id ds1so6303849wgb.10 for ; Sun, 04 Dec 2011 17:20:23 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.216.230.133 with SMTP id j5mr1590848weq.42.1323048023052; Sun, 04 Dec 2011 17:20:23 -0800 (PST) Received: by 10.223.103.70 with HTTP; Sun, 4 Dec 2011 17:20:22 -0800 (PST) Received: by 10.223.103.70 with HTTP; Sun, 4 Dec 2011 17:20:22 -0800 (PST) In-Reply-To: <20111205030758.33e7a4e2@rohan.example.com> References: <87vcpwxau3.fsf@newsguy.com> <20111205000820.7b829d64@rohan.example.com> <87r50jykcx.fsf@newsguy.com> <87mxb7yiwk.fsf@newsguy.com> <20111205030758.33e7a4e2@rohan.example.com> Date: Mon, 5 Dec 2011 08:20:22 +0700 Message-ID: Subject: Re: [gentoo-user] Re: vbox vm no boot From: Pandu Poluan To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=0016364d1bc16f4fdc04b34e1f56 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - svr-us4.tirtonadi.com X-AntiAbuse: Original Domain - lists.gentoo.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - poluan.info X-Archives-Salt: c7b2a3c2-3726-4355-a031-1098567bb617 X-Archives-Hash: ca230359ebffccc482845d1c1460af20 --0016364d1bc16f4fdc04b34e1f56 Content-Type: text/plain; charset=UTF-8 On Dec 5, 2011 8:13 AM, "Alan McKinnon" wrote: > > On Mon, 5 Dec 2011 07:34:46 +0700 > Pandu Poluan wrote: > > > On Dec 5, 2011 7:19 AM, "Harry Putnam" wrote: > > > > > > Harry Putnam writes: > > > > > > > Alan McKinnon writes: > > > > > > > > [...] > > > > > > > >> A Gentoo VM on a Linux host works fine here with the same setup. > > > >> Let's examine the host settings first as that affects booting > > > >> too. > > > >> > > > >> What settings do you have on the System and Storage tabs on the > > > >> VBox host for that vm? > > > > > > > > I guess the easiest is to post screen shots of those tabs: > > > > > > > > www.jtan.com/~reader/vu2/disp.cgi > > > > > > > > I did notice that on System tab the chipset is listed as piix3 > > > > and on Storage Tab it shows `type' as PIIX4. At first there were > > > > no other choices on the drop downs, so I assumed it was ok like > > > > that... now I see the dropdown on Storage has gotten populated > > > > since I last tried it. > > > > > > > > I set it to match the System `chip' PIIX3... but still the same > > > > failure. > > > > > > > > Maybe those are not related to the problem? > > > > > > Haa... that google hit I mentioned about resetting bootable with > > > gparted worked... Now bootup starts. But the same old sorry bs I > > > have always hit with gentoo when trying to setup a vm is now > > > present and accounted for... > > > > > > www.jtan.com/~reader/vu1/disp.cgi > > > > > > > Seems to be a case of missing driver to me :-) > > I'm not convinced. The error is: > > FATAL: No bootable medium found! System halted > Have you seen his last screen cap? The latest error message is now: Kernel panic - not syncing: VFS: unable to mount root. The preceding lines don't indicate the kernel recognizing any hard disks, so I guessed the right driver has not been loaded. Rgds, --0016364d1bc16f4fdc04b34e1f56 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Dec 5, 2011 8:13 AM, "Alan McKinnon" <alan.mckinnon@gmail.com> wrote:
>
> On Mon, 5 Dec 2011 07:34:46 +0700
> Pandu Poluan <pandu@poluan.inf= o> wrote:
>
> > On Dec 5, 2011 7:19 AM, "Harry Putnam" <reader@newsguy.com> wrote:
> > >
> > > Harry Putnam <reade= r@newsguy.com> writes:
> > >
> > > > Alan McKinnon <alan.mckinnon@gmail.com> writes:
> > > >
> > > > [...]
> > > >
> > > >> A Gentoo VM on a Linux host works fine here with th= e same setup.
> > > >> Let's examine the host settings first as that a= ffects booting
> > > >> too.
> > > >>
> > > >> What settings do you have on the System and Storage= tabs on the
> > > >> VBox host for that vm?
> > > >
> > > > I guess the easiest is to post screen shots of those ta= bs:
> > > >
> > > > =C2=A0 =C2=A0www.jtan.com/~reader/vu2/disp.cgi
> > > >
> > > > I did notice that on System tab the chipset is listed a= s piix3
> > > > and on Storage Tab it shows `type' as PIIX4. =C2=A0= At first there were
> > > > no other choices on the drop downs, so I assumed it was= ok like
> > > > that... now I see the dropdown on Storage has gotten po= pulated
> > > > since I last tried it.
> > > >
> > > > I set it to match the System `chip' PIIX3... but st= ill the same
> > > > failure.
> > > >
> > > > Maybe those are not related to the problem?
> > >
> > > Haa... that google hit I mentioned about resetting bootable = with
> > > gparted worked... Now bootup starts. =C2=A0But the same old = sorry bs I
> > > have always hit with gentoo when trying to setup a vm is now=
> > > present and accounted for...
> > >
> > > www.jta= n.com/~reader/vu1/disp.cgi
> > >
> >
> > Seems to be a case of missing driver to me :-)
>
> I'm not convinced. The error is:
>
> FATAL: No bootable medium found! System halted
>

Have you seen his last screen cap? The latest error message is now:

Kernel panic - not syncing: VFS: unable to mount root.

The preceding lines don't indicate the kernel recognizing any hard d= isks, so I guessed the right driver has not been loaded.

Rgds,

--0016364d1bc16f4fdc04b34e1f56--