I've been trying to get a 32 bit Fedora/armv7hl guest to boot on a 64 bit Fedora/aarch64 host. Host: Fedora Rawhide, aarch64 on Mustang Guest: Fedora 22 disk image from: $ virt-builder --arch armv7l fedora-22 I should say that: (1) I can boot this guest using an external <kernel> and <initrd> and some hand written libvirt XML. However external kernel is not very flexible, since it means you have to do a dance on the host each time you update the guest. (2) I can boot this guest on x86-64 host using external kernel. (3) It doesn't boot with UEFI in the guest, but that is expected since the guest doesn't contain a UEFI bootloader, and I'm not even sure if there is such a thing as UEFI for 32 bit ARM. Anyway, I attempted to boot this disk image without the external kernel hack using: $ virt-install --arch armv7l --import --name test3 --ram 2048 --disk path=/var/tmp/test3.qcow2,format=qcow2 --os-variant fedora22 but it just hangs with a blank console, and with qemu-system-aarch64 [sic] using 100% CPU. I poked around inside the disk image, and there seems to be no evidence that it booted, eg. no logs, no updated timestamps. Should I try a newer guest? I am going to try updating to Fedora 23. Is it even possible to boot a 32 bit disk image without external kernel? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/arm@xxxxxxxxxxxxxxxxxxxxxxx
