From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ETeA2-0001hs-Kq for qemu-devel@nongnu.org; Sun, 23 Oct 2005 07:37:10 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ETe9z-0001gk-I2 for qemu-devel@nongnu.org; Sun, 23 Oct 2005 07:37:09 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ETe46-0008FT-3V for qemu-devel@nongnu.org; Sun, 23 Oct 2005 07:31:02 -0400 Received: from [66.249.82.207] (helo=xproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1ETe45-0003Bl-Pc for qemu-devel@nongnu.org; Sun, 23 Oct 2005 07:31:02 -0400 Received: by xproxy.gmail.com with SMTP id i30so12628wxd for ; Sun, 23 Oct 2005 04:30:58 -0700 (PDT) Message-ID: Date: Sun, 23 Oct 2005 11:30:58 +0000 From: Ulf Magnusson Subject: Re: [Qemu-devel] Problems with Zeta LiveCD In-Reply-To: <435B4549.3060801@gmx.de> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_23633_4140438.1130067058561" References: <435B4549.3060801@gmx.de> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org ------=_Part_23633_4140438.1130067058561 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I noticed the official distribution already has the two tracks split into zetaboot.img and zetacd.img, so that's less work me :) I ran $ qemu -cdrom zetaboot.img -hda zetacd.img -boot d and selected the hd from the boot menu. That led to a kernel panic (PANIC: boot device not found"). I then tried running without any hd, and instead changed the disk to zetacd.img from the console when the prompt for the CD came up. That way I got to the magnifying glass stage of the ZETA boot screen, but there it panics with "PANIC: no shell!". Any ideas? Thanks for your reply, Ulf On 10/23/05, Christian Wiese wrote: > > Hi, > > this behaviour is because of the way a BeOS/ZETA cd is constructed. For > some more infos take a look at the bottom of this page: > http://forum.mlotz.ch/viewtopic.php?t=3D120 > > What you could do: > - Make a boot floppy out of track one of your demo-cd. > - Extract the second track as iso (be sure to take only the second track) > - In qEmu boot from your virtual floppy, press `space` to access the > bootmenu and select your virtual hd. > This way I get a complete ZETA installed in qEmu. But don=B4t expect to > much, as most hardware is currently not supported (the last time i tried) > > Greetings, > Chris > > > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel > ------=_Part_23633_4140438.1130067058561 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I noticed the official distribution already has the two tracks split into z= etaboot.img and zetacd.img, so that's less work me :)

I ran

$ qemu -cdrom zetaboot.img -hda zetacd.img -boot d

and selected the hd from the boot menu. That led to a kernel panic (PANIC: = boot device not found").

I then tried running without any hd, and instead changed the disk to zetacd.img from the console when the prompt for the CD came up. That way I got to the magnifying glass stage of the ZETA boot screen, but there it panics with "PANIC: no shell!". Any ideas?

Thanks for your reply,
Ulf

On 10/23/05, Christian Wiese <= developlists@gmx.de> wrote:
Hi,

this behaviour is because of the way a BeOS/ZETA cd is construct= ed. For
some more infos take a look at the bottom of this page:
http://forum.mlotz.ch/vi= ewtopic.php?t=3D120

What you could do:
- Make a boot floppy out of track one of = your demo-cd.
- Extract the second track as iso (be sure to take only th= e second track)
- In qEmu boot from your virtual floppy, press `space` t= o access the
bootmenu and select your virtual hd.
This way I get a complete ZETA = installed in qEmu. But don=B4t expect to
much, as most hardware is curre= ntly not supported (the last time i tried)

Greetings,
Chris


_______________________________________________
Qemu-devel maili= ng list
Qemu-devel@nongnu.org
http:= //lists.nongnu.org/mailman/listinfo/qemu-devel

------=_Part_23633_4140438.1130067058561--