I cannot get qemu-system-arm to boot any of our F17 kernels, but here's what I did anyway. # Make a disk image: $ wget 'http://fedora.roving-it.com/rootfs-f17-hfp-alpha1.tar.bz2' $ bunzip2 rootfs-f17-hfp-alpha1.tar.bz2 $ virt-make-fs -s 2G -t ext3 -F raw --partition=mbr rootfs-f17-hfp-alpha1.tar disk.img Formatting 'disk.img', fmt=raw size=2147483648 $ ll disk.img -rw-r--r--. 1 rjones rjones 2147483648 Mar 23 05:47 disk.img $ virt-filesystems -a disk.img --all --long -h Name Type VFS Label MBR Size Parent /dev/sda1 filesystem ext3 - - 2.0G - /dev/sda1 partition - - 83 2.0G /dev/sda /dev/sda device - - - 2.0G - # Extract the kernels from the tarball: $ tar tf rootfs-f17-hfp-alpha1.tar | less $ tar xf rootfs-f17-hfp-alpha1.tar ./boot/ # Try to boot it one of the kernels in the boot/ directory: $ qemu-system-arm -m 256 -M versatilepb -kernel boot/vmlinuz-3.3.0-0.rc4.git3.1.fc17.armv7hl -initrd boot/initramfs-3.3.0-0.rc4.git3.1.fc17.armv7hl.img -hda disk.img -serial stdio -vga std Uncompressing Linux... done, booting the kernel. It just hangs at this point using 100% CPU with no output. The other kernels don't even seem to get that far. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
