On 11/26/2013 12:10 PM, Cole Robinson wrote:
On 11/26/2013 12:07 PM, Reartes Guillermo wrote:
I also experienced it, by following
https://fedoraproject.org/wiki/QA:Testcase_Virt_x86_on_ARM
There, in "How to Test" -> "Get the Media" It says:
Copy kernel, initrd, and dtb to the default libvirt image location:
# sudo mv boot/vmlinuz-3.11.0-300.fc20.armv7hl+lpae
boot/initramfs-3.11.0-300.fc20.armv7hl.img
boot/dtb-3.11.0-300.fc20.armv7hl/vexpress-v2p-ca9.dtb
/var/lib/libvirt/images
--> /vmlinuz-3.11.0-300.fc20.armv7hl+lpae
--> /initramfs-3.11.0-300.fc20.armv7hl.img
So yes, i replaced the kernel with a non +lpae and i got output.
Maybe the page should be updated.
Whoops, apologies, didn't realize the page was wrong. Fixed now.
A world of difference! This time it worked.
One comment and one question:
Comment: Boy, there are some times when that arm virtual is "busy" and
the whole x-window/gnome-shell screen sort-of freezes. That happened
when I did "yum list kernel" on the virtual arm system. I have never
seen anything like that happen with the other qemu-kvm (mostly x86_64)
virtuals I run.
Question: OK, those "instructions" for the
|Fedora-Minimal-armhfp-20-Alpha-4|
system seem to be general enough that I might use them with other arm
images.
For example, I would like to give the Fedora LXDE armhfp 20 Beta a try.
(I have found that LXDE is a good choice for virtuals).
BTW, unxz works even better than unar for uncompressing that image ...
less cluttler left to clean up.
Gene
||
_______________________________________________
virt mailing list
virt@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/virt
