Thanks for trying to help me figure this out. I was using coreboot and FILO to build a custom BIOS that is supposed to live on this board. QEMU was asked to boot using the custom BIOS. A full Grub configuration wasn't needed in this case. The image that I was using from coreboot included the BIOS and a FILO build in a single image file. FILO (<a href="http://www.coreboot.org/FILO">http://www.coreboot.org/FILO</a>) is a cut-down version of Grub that can live inside the BIOS. I have no idea what version of Grub it is supposed to be compared to. Anyhow, it turns out I was confusing a FILO/Grub root parameter with a boot parameter that is supposed to be passed to the kernel. Basically, my root parameter was incorrect. That's why I got that weird error message about not being able to read the filesystem; FILO includes native ext2 support. You live and you learn.<br>
<br><div class="gmail_quote">On Mon, Aug 29, 2011 at 7:10 PM, James Baker <span dir="ltr"><<a href="mailto:jimbakerforlinux@comcast.net">jimbakerforlinux@comcast.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<u></u>
<div text="#000000" bgcolor="#ffffff"><div><div></div><div class="h5">
On 08/29/2011 03:00 PM, David Hillman wrote:
</div></div><blockquote type="cite"><div><div></div><div class="h5">I am trying to test out a custom firmware that is
supposed to be loaded to a router board. The test is done using
QEMU. I...
<div><br>
</div>
<div>
<ol>
<li>build the kernel and initrd using the tools from the board
manufacturer.</li>
<li>used qemu-img to create a raw disk image</li>
<li>mkfs.ext2 to format the image</li>
<li>mounted the image to my Ubuntu filesystem as a loop device</li>
<li>used debootstrap to build a minimal filesystem, plus added
tools required for the board to run</li>
<li>copied over the kernel and initrd to /boot on the mounted
filesystem</li>
<li>chrooted into the system to setup grub menu.1st, etc</li>
<li>exited out of and booted the router system using QEMU</li>
</ol>
<div>No matter what I do, Grub gives up and throws an error
about not being able to read the filesystem. I know the ext2
driver is in the initrd.</div>
</div>
<div>Manually setting up the partition info and telling Grub to
boot from the prompt gives the same error.</div>
<div><br>
</div>
<div>Is there something else I should be looking for? My
understanding of the Linux boot process might be fuzzy here,
plus I am not that familiar with Grub. </div>
<div>It's what was recommended to test inside QEMU.</div>
</div></div><pre><fieldset></fieldset>
_______________________________________________
Ale mailing list
<div class="im"><a href="mailto:Ale@ale.org" target="_blank">Ale@ale.org</a>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a>
See JOBS, ANNOUNCE and SCHOOLS lists at
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a>
</div></pre>
</blockquote>
The file name should be menu.lst NOT menu.1st.<br>
HTH<br>
<br>
</div>
<br>_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
<br></blockquote></div><br>