El 22/05/12 15:15, Dennis Gilmore escribió:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 22 May 2012 14:54:59 -0500
Alex Villacís Lasso<a_villacis@xxxxxxxxxxxxx> wrote:
I am currently able to boot kernel-3.3.4-3.fc17.armv5tel with the
following qemu commandline:
[palosanto@virthost fedora-17]$ KERNELVER=3.3.4-3.fc17.armv5tel
[palosanto@virthost
fedora-17]$ /home/palosanto/programa/qemu-build/arm-softmmu/qemu-system-arm
-nographic -m 256 -M versatilepb -kernel boot/vmlinuz-$KERNELVER
-initrd boot/initramfs-$KERNELVER.img -append "root=LABEL=rootfs
console=ttyAMA0 audit=0" -hda fedora-17-arm.vmdk
If I just replace KERNELVER to 3.3.6-3.fc17.armv5tel , the boot
process just hangs.
If I specify -M vexpress-a9, I can sort of boot the kernel. However
no block device matching the disk image appears anywhere, so the boot
process drops to an debug shell, like this:
use -sd for your disk not -hda and you have to use -M vexpress-a9
so something like
/home/palosanto/programa/qemu-build/arm-softmmu/qemu-system-arm
- -nographic -m 256 -M versatilepb -kernel boot/vmlinuz-$KERNELVER
- -initrd boot/initramfs-$KERNELVER.img -append "root=LABEL=rootfs
console=ttyAMA0 audit=0" -sd fedora-17-arm.vmdk -M vexpress-a9
should work it does with the qemu binarries shipped in Fedora 17
Dennis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
iEYEARECAAYFAk+79AYACgkQkSxm47BaWfdzyACdGMdbFPAJuABsBxyUO9jjKeJN
+RcAmwWNervHKZAcsuDdimDUJUnY/TA3
=PoN8
-----END PGP SIGNATURE-----
_______________________________________________
arm mailing list
arm@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/arm
Thanks! -sd did the trick.
_______________________________________________
arm mailing list
arm@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/arm
