I am trying to run fedora arm under virtual box under fedora 18. I am
following http://fedoraproject.org/wiki/Architectures/ARM/HowToQemu .
I get following error. Please help.
# virsh define arm1.xml
Domain arm1 defined from arm1.xml
# virsh start arm1
error: Failed to start domain arm1
error: internal error process exited while connecting to monitor: Error:
Cirrus VGA not available
Open Learning Exchange (OLE) Nepal
Tel: +977.1.5544441, 5520075 Ext. 303
Cell: +977.9818 605110
** Resending with the right lists **
after talking at devconf with David Cantrell about the best way to
support setting up uboot on arm devices in anaconda, the best approach
going forward is pretty clear, ill get to it in a bit first i want to
describe things as I see them.
Unified kernel while solving many issues introduces some. platform
detection was kinda simple with separate kernels. unified kernel means
that while we dont need to worry about having the right kernel, we do
need to worry about loading the right dtb.
platform detection is also needed to know where in ram we should load
the kernel and offsets for initramfs and dtb to be loaded. anaconda can
tell us the filesystem and device that we are installing to, but
depending on the exact way support is done in uboot we may need to put
in different values, SCSI vs SATA vs USB etc we also need to ensure we
use the right dtb file. for instance a pandaboard ES can use a
pandaboard dtb but will be 1ghz vs the 1.2ghz its capable of. some
systems like the highbank ones have the dtb in their uboot. while
others need to load an external file.
so as i see it we need a library that anaconda can import and use to
work out the right values for the system we are installing to. probably
the library should write out the uboot template and run mkconfig on
it. we could then reuse the library in a tool to say setup a boot
sdcard to run the installer on a system. we have an issue where it is
really not possible to make the equivilent of a boot.iso that will be
I think we should take this up to the cross distro list at linaro and
ideally have the distros work on a database at the least of platforms
and the values and types needed. if not the whole library that can be
used in different places to set things up.
this is only needed for 32 bit arm, 64 bit will have UEFI, ACPI and
grub2. potentially we also want to consider if we can implement
http://www.freedesktop.org/wiki/Specifications/BootLoaderSpec since we
need to implement something anyway.
I was looking over at Linaro.org and saw them recommend Freescale's i.MX53 Quick Start board 
Then I looked at the list of ARM boards with Fedora 18 and the Remix list and didn't see Freescale mentioned. Anyone done any Fedora work on that board?
Their Code Warrior setup for their boards is nice. So I was considering one of these boards. Thoughts?
Good day all,
At FUDCon we discussed the creation of a 'Secret Decoder Ring' document that would help
those new to the ARM world to quickly become familiar with the ongoing work and ease the
process of jumping in.
A draft of the document has been posted:
Please take a few moments to have a look, and feel free to contribute or provide feedback
on any areas that may need more fleshing out or have yet to have text added. There is a
link at the top of the page to the original document created at FUDCon for reference.