<p>What version of grub are you using and how are you attempting to install it in the image? As David T. mentioned, no partitions can be a problem, but grub likes to installed on real devices anyway, which can be an issue. Very late GRUBs can be used on certain types of images, in certain conditions... and if it is an older grub it needs a bios mapping.</p>
<div class="gmail_quote">On Aug 29, 2011 3:01 PM, "David Hillman" <<a href="mailto:hillmands@gmail.com">hillmands@gmail.com</a>> wrote:<br type="attribution">> I am trying to test out a custom firmware that is supposed to be loaded to a<br>
> router board. The test is done using QEMU. I...<br>> <br>> <br>> 1. build the kernel and initrd using the tools from the board<br>> manufacturer.<br>> 2. used qemu-img to create a raw disk image<br>
> 3. mkfs.ext2 to format the image<br>> 4. mounted the image to my Ubuntu filesystem as a loop device<br>> 5. used debootstrap to build a minimal filesystem, plus added tools<br>> required for the board to run<br>
> 6. copied over the kernel and initrd to /boot on the mounted filesystem<br>> 7. chrooted into the system to setup grub menu.1st, etc<br>> 8. exited out of and booted the router system using QEMU<br>> <br>
> No matter what I do, Grub gives up and throws an error about not being able<br>> to read the filesystem. I know the ext2 driver is in the initrd.<br>> Manually setting up the partition info and telling Grub to boot from the<br>
> prompt gives the same error.<br>> <br>> Is there something else I should be looking for? My understanding of the<br>> Linux boot process might be fuzzy here, plus I am not that familiar with<br>> Grub.<br>
> It's what was recommended to test inside QEMU.<br></div>