Re: F14 qemu arm default board

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Quoting Chris Tyler <chris@xxxxxxxxxxx>:

> On Thu, 2010-12-30 at 10:47 -0500, omalleys@xxxxxxx wrote:
>> In F14 x86, we finally have the ability to add an ARM based VM via the
>> libvirt management tool!! IE you can go through the GUI and set up an
>> qemu based arm VM*.
>>
>> It defaults to the integratorcp board. But our image/kernel for F12 is
>> for the versatile board.)
>
> The F12 ARM project doesn't provide a kernel, and the rootfs is pretty
> much board-agnostic, so you just need to use/supply a suitable kernel.

The point I am trying to get at is, not whether the it will work, but  
what is the fastest combo so we can make that the default target in  
the F14 virt manager and have a matching working image/install system  
for it.

I do update the wiki if I find something useful. I don't want to have  
to go back and re-figure everything out again.

There is a downloadable versatile kernel along with instructions on  
how to make it on the wiki.

The F12 image along with your workaround script do work in F14. Minus  
the fact when you stop the VM from the GUI it leaves a qemu process  
hanging.  I think I got an armv7 kernel working with like the  
versatilea/b board, but I stopped there.  I kind of lost patience with  
5 hour kernel compiles and qemu crashing when I tried to add more then  
128M of ram. I think there were some device issues, so some setting I  
was probably missing. Im not exactly an arm guru.

While real hardware is better, some of us don't have 2 devices to test  
with, and make rootfs and kernels with and test software with. I  
debated for months on whether a guruplug would be fast enough for my  
needs, and if i would have solely looked at the results of my qemu  
testing, I wouldn't have purchased one.

One instance is when I tried to do the mkrootfs-13 on the guruplug  
with the default software (apt-get yum rpmbuild etc) the checksums  
couldn't be verified because the versions of python were different and  
yum couldn't support the sha256 or whatever checksum algorithm. I had  
to set up a VM to do that.

If you can get performance similar or faster to actual hardware, there  
will be more interest. If it is pretty easy to set up a VM and add it  
to your build system, you might actually do it like we did for  
openafs. (which takes like 3 hours and you cannot get it to cross  
compile.)  Virtio and 9P support are coming for qemu arm, which would  
be a nice default setting, but I don't think all of the patches have  
made it to the mainline kernel yet.





_______________________________________________
arm mailing list
arm@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/arm


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux ARM (Vger)]     [Linux ARM]     [ARM Kernel]     [Fedora User Discussion]     [Older Fedora Users Discussion]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Maintainers]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Coolkey]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]

Powered by Linux