[Buildroot] Anyone try simulating their Buildroot-created filesystem image in QEMU?

[Arun Reddy]

I too was confused about loading the kernel in this case. QEMU is supposed
to behave as the bootloader during emulation but that doesn't mean the
kernel will be loaded. I think the initial RAM disk might be a good option
to explore next. I'll enable RAM disk support and create a new filesystem
image to try and use with the -initrd option instead of -hda.

Thanks for the advice.

On Fri, May 23, 2008 at 12:13 PM, John Voltz <john.voltz at gmail.com> wrote:

> I've used qemu to run an image for x86, but I used grub to load the kernel.
> I'm not really sure how you do it without a bootloader. You also need to
> make sure you have the kernel module for the filesystem and storage device
> either compiled into the kernel or in a initrd file.
>
> John
>
>
> On Fri, May 23, 2008 at 3:05 PM, Arun Reddy <reddyac at gmail.com> wrote:
>
>> While this might fall more under a QEMU related problem, I thought it
>> might be helpful to ask it here since other Buildroot members may have
>> encountered the same problem I'm having.
>>
>> I have successfully built my filesystem image for a versatile (pb)
>> baseboard. I have included all the appropriate hardware and drivers for this
>> board in my kernel configuration as listed here:
>>
>> http://fabrice.bellard.free.fr/qemu/qemu-doc.html#SEC63
>>
>> I am trying to now boot it in QEMU, and used the following syntax:
>>
>> qemu-system-arm -M versatilepb -m 128 -kernel
>> arm-linux-2.6.24.4-20080523.gz -hda rootfs.arm.ext2 -nographic -append
>> "root=/dev/hda1 console=ttyAMA0"
>>
>> The kernel image uncompresses fine, but I am getting a kernel panic saying
>> that it is unable to mount the root fs on unknown block. I was wondering if
>> the problem is coming from the fact that rootfs.arm.ext2 is not a harddisk
>> image, and cannot be used with the -hda option? Or does it have to do with
>> the device I passed into root=? I know for certain that hda1 is what I wish
>> to use so the kernel will know what to use as the root filesystem... in this
>> case the local harddisk.
>>
>> Has anyone here had trouble getting their kernel to boot in qemu after
>> finishing their buildroot build process? Should I build my kernel for
>> another board supported by QEMU and try again? Thanks for any help you can
>> offer!
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot at uclibc.org
>> http://busybox.net/mailman/listinfo/buildroot
>>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.buildroot.org/pipermail/buildroot/attachments/20080523/96fd1032/attachment-0001.html>