QEMU

From WebOS Internals
Revision as of 17:38, 22 July 2009 by Hopspitfire (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

THIS DOES NOT WORK. REPEAT, DOES NOT WORK. THIS IS STILL BEING INVESTIGATED.

1) Grab qemu-omap3.

2) Compile (standard configure options are fine).

3) Create a full PC-partitioned disk image with a fat32 partition. extract the root image into it:

mount -o loop,offset=16384 root.img m
cd m
tar xzvf ../nova-cust-image-castle.rootfs.tar.gz

4) The bootloader must be named mlo in the root directory:

cp boot/boot.bin mlo
cd ..
umount m

5) qemu-system-arm -M beagle -sd root.img

You will probably get this output:

omap3_mmc_fat_boot: MLO file not found in the root directory
qemu: fatal: no boot device found
R00=00000000 R01=00000000 R02=00000000 R03=00000000
R04=00000000 R05=00000000 R06=00000000 R07=00000000
R08=00000000 R09=00000000 R10=00000000 R11=00000000
R12=00000000 R13=00000000 R14=00000000 R15=400140a4
PSR=400001d3 -Z-- A svc32
Aborted

Not sure why. Still digging.

I added some debugging hooks into QEMU and it looks like it's not parsing the file system. it's *finding* everything fine, but seems to not want to actually read the data clusters. Perhaps it's an issue with mkdosfs...?