* Custom kickstart file
* Requires old packages of anaconda(anaconda-17.29-1.fc17) and lorax(lorax-17.17-1.fc17)
* Let us know if you get this working with newest packages ^of anaconda or lorax please (:
== Process ==
# * Install a virtual machine setup on fedora including virt-manager# * Download a fedora arm image: [http://download.fedoraproject.org/pub/fedora/linux/releases/20/Images/armhfp/Fedora 20 Arm Images]# * Copy out the boot files from the image: http[https://download.fedoraproject.org/pubwiki/QA:Testcase_Virt_ARM_on_x86#Get_the_media Some instructions ]** If these instructions don't work you may have to use kpartx on the image to mount it and cp out the /boot manually.<pre># if you are having trouble getting the /boot out of the imagekpartx -av /path_to_image/image.img# find out which loop it was mounted on, probably loop0, which means boot is loop0p1mount /dev/mapper/loop0p1 /mnt/cp /mnt/fedora/linuxwhere_ever_you_want/releasesumount /20mnt/Imageskpartx -dv /armhfppath_to_image/image.img# Confirm that loop closed successfullylosetup -a # should show no output# If the loop is still being used by the image you can try removing all loopslosetup -D# All else fails, don't worry about it, a reboot will get rid of it. </pre> *Create a new virtual machine with virt-manager* # Choose the arm architecture* # Use the vexpress-a15* # kernel: /directory_to_extracted_files/boot/vmlinuz-3.11.10-301.fc20.armv7hl* # Initrd: /directory_to_extracted_files/boot/uInitrd-3.11.10-301.fc20.armv7hl* # DTB: /directory_to_extracted_files/boot/dtb-3.11.10-301.fc20.armv7hl/vexpress-v2p-ca15-tc1.dtb* # Kernel args: console=ttyAMA0 rw root=/dev/vda3 rootwait* # ram should be at least than 1.2GB(I tested with 2GB)* # Only use 1 cpu or it crashes(I don't know why...)# * Expand image or add extra space. You will need disk space equal to (pidora composed image size * 2) + pidora chroot size. I used about 20 GB, was enough for multiple composes.* I used a pidora f17chroot inside the inside the arm qemu image, then installed anaconda and lorax inside the chroot. You can get the packages through yum or if that is an issue from the pidora koji instance.#
#
* EXTRA NOTE: Using a pidora chroot might not be necessary(?) as long as you can use the following packages inside the qemu environment: anaconda(anaconda-17.29-1.fc17) and lorax(lorax-17.17-1.fc17), however this is a guess. Maybe people would have better luck using a fedora 17 rootfs instead of the f20 rootfs. (On that note, it might be worth it to try using the fedora 20 images /boot: kernel, initrd, and dtb with a fedora 17 arm image rootfs)
