Comment 9 for bug 524893

Reopening the bug since:
- the patch was just a workaround to support the RAMDISK method, but doesn't fix initramfs support
- it actually doesn't work even with the patch :-(

qemu-system-arm -m 256 -drive file=lucid.img,media=disk -M versatilepb -cpu cortex-a8 -kernel linux-image-2.6.32-16-versatile_2.6.32-16.24/boot/vmlinuz-2.6.32-16-versatile -initrd initrd.gz -append 'rootdelay=20 root=/dev/ram0 console=ttyAMA0,115200' -nographic
[...]
[ 1.752156] type=2000 audit(0.495:1): initialized
[ 1.817340] Trying to unpack rootfs image as initramfs...
[ 1.824094] rootfs image is not initramfs (junk in compressed archive); looks like an initrd
[ 1.876329] Freeing initrd memory: 3640K
[...]
[ 25.265275] md: ... autorun DONE.
[ 25.270878] RAMDISK: Couldn't find valid RAM disk image starting at 0.
[ 25.291694] List of all partitions:
[ 25.292090] 0b00 1048575 sr0 driver: sr
[ 25.292315] 0800 1331200 sda driver: sd
[ 25.292514] No filesystem could mount root, tried: ext3 ext2 ext4 cramfs fuseblk
[ 25.292991] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
[...]

It might be that our vmlinuz is so big that it clobbers the initramfs space on unpack; I can't load vmlinux though (bug #534324) so can't easily confirm.