[LinuxBIOS] Question about QEMU & FILO

[Marc Karasek]

I am trying to get a system up using QEMU.  I have compiled LinuxBIOS 
with Filo as a payload.

I followed the steps on the wiki about making a harddrive image,  I had 
to make it a bit bigger than 200M though. 
When I "boot" the system,  it finds the kernel and the initrd image, but 
then when it gets a bit further it seems to have a problem with finding 
the harddrive image to boot from .  Although it has already fetched the 
kernel and initrd from the image.

Any pointers would be appreciated.

Waiting for driver initialization.
Loading ata_generic.ko module
Trying to resume from LABEL=SWAP-sda2
Unable to access resume device (LABEL=SWAP-sda2)
Creating root device.
Mounting root filesystem.
mount: could not find filesystem '/dev/root'
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Booting has failed.

[Corey Osgood]

Marc Karasek wrote:
> I am trying to get a system up using QEMU.  I have compiled LinuxBIOS 
> with Filo as a payload.
>
> I followed the steps on the wiki about making a harddrive image,  I had 
> to make it a bit bigger than 200M though. 
> When I "boot" the system,  it finds the kernel and the initrd image, but 
> then when it gets a bit further it seems to have a problem with finding 
> the harddrive image to boot from .  Although it has already fetched the 
> kernel and initrd from the image.
>
> Any pointers would be appreciated.
>
> Waiting for driver initialization.
> Loading ata_generic.ko module
> Trying to resume from LABEL=SWAP-sda2
> Unable to access resume device (LABEL=SWAP-sda2)
> Creating root device.
> Mounting root filesystem.
> mount: could not find filesystem '/dev/root'

what's your FILO boot command? Are you using grub or autoboot? Shouldn't
this be root=/dev/XdaN?

-Corey
> Setting up other filesystems.
> Setting up new root fs
> setuproot: moving /dev failed: No such file or directory
> no fstab.sys, mounting internal defaults
> setuproot: error mounting /proc: No such file or directory
> setuproot: error mounting /sys: No such file or directory
> Switching to new root and running init.
> unmounting old /dev
> unmounting old /proc
> unmounting old /sys
> switchroot: mount failed: No such file or directory
> Booting has failed.

[ron minnich]

On Dec 6, 2007 10:57 AM, Marc Karasek  wrote:
> I am trying to get a system up using QEMU.  I have compiled LinuxBIOS
> with Filo as a payload.
>
> I followed the steps on the wiki about making a harddrive image,  I had
> to make it a bit bigger than 200M though.
> When I "boot" the system,  it finds the kernel and the initrd image, but
> then when it gets a bit further it seems to have a problem with finding
> the harddrive image to boot from .  Although it has already fetched the
> kernel and initrd from the image.
>
> Any pointers would be appreciated.
>
> Waiting for driver initialization.
> Loading ata_generic.ko module
> Trying to resume from LABEL=SWAP-sda2
> Unable to access resume device (LABEL=SWAP-sda2)

This is a linux error message. Your are now in initrd hell. You are
missing the modules you need to load the drivers for the hardware.

The problems start above. Everything else after is of no real use,
since you are dead at this point.

I am attaching a script I used to generate a very generic initrd with
lots of drivers, including USB drivers; we use it when we boot usb
root file systems. It's a useful example and it's small.

ron

[Erwan Velu]

Marc Karasek a écrit :
> I am trying to get a system up using QEMU.  I have compiled LinuxBIOS 
> with Filo as a payload.
>
> I followed the steps on the wiki about making a harddrive image,  I had 
> to make it a bit bigger than 200M though. 
> When I "boot" the system,  it finds the kernel and the initrd image, but 
> then when it gets a bit further it seems to have a problem with finding 
> the harddrive image to boot from .  Although it has already fetched the 
> kernel and initrd from the image.
>
> Any pointers would be appreciated.
>
> Waiting for driver initialization.
> Loading ata_generic.ko module
> Trying to resume from LABEL=SWAP-sda2
> Unable to access resume device (LABEL=SWAP-sda2)
> Creating root device.
> Mounting root filesystem.
> mount: could not find filesystem '/dev/root'
> Setting up other filesystems.
> Setting up new root fs
> setuproot: moving /dev failed: No such file or directory
> no fstab.sys, mounting internal defaults
> setuproot: error mounting /proc: No such file or directory
> setuproot: error mounting /sys: No such file or directory
> Switching to new root and running init.
> unmounting old /dev
> unmounting old /proc
> unmounting old /sys
> switchroot: mount failed: No such file or directory
> Booting has failed.

Qemu is emulating some ide disks, so you must have some root=/dev/hdax 
on your command line instead of /dev/sdax
About the kernel modules, you must have the piix kernel module loaded in 
the initrd.
Please check your /etc/modprobe.conf for that and redo the initrd with 
mkinitrd.

--------------------------------------------------------------------------------
Les opinions et prises de position emises par le signataire du present
message lui sont propres et ne sauraient engager la responsabilite de la
societe SEANODES.

Ce message ainsi que les eventuelles pieces jointes constituent une
correspondance privee et confidentielle a l'attention exclusive du
destinataire designe ci-dessus. Si vous n'etes pas le destinataire du
present message ou une personne susceptible de pouvoir le lui delivrer, il
vous est signifie que toute divulgation, distribution ou copie de cette
transmission est strictement interdite. Si vous avez recu ce message par
erreur, nous vous remercions d'en informer l'expediteur par telephone ou de
lui retourner le present message, puis d'effacer immediatement ce message de
votre systeme.

The views and opinions expressed by the author of this message are personal.
SEANODES shall assume no liability, express or implied for such message.

This e-mail and any attachments is a confidential correspondence intended
only for use of the individual or entity named above. If you are not the
intended recipient or the agent responsible for delivering the message to
the intended recipient, you are hereby notified that any disclosure,
distribution or copying of this communication is strictly prohibited. If you
have received this communication in error, please notify the sender by phone
or by replying this message, and then delete this message from your system.