On 12/27/2014 06:19 PM, Brooks Hu
wrote:
Note that the installation options indicate: 4) [!] Software selection (Nothing selected) and 5) [!] Installation Destination (No disks selected), which implies anaconda is not seeing (or accepting) some of the options in your kickstart. Please look in the logs in /tmp to find any errors. There are some things in you kickstart that I am not familiar with, such as: vznetcfg --net=virt_network1:eth0 vztturlmap $FS_SERVER http://myrepository.com nosfxtemplate %eztmplates --cache and the following just look wrong for an aarch64 install: centos-6-x86_64 centos-6-x86
mailman-centos-6-x86_64
mailman-centos-6-x86
I would try a more "standard" Fedora kickstart install first to make sure the repos, etc. are working, and then try adding the 'custom' config options to see what breaks. Attached is an example kickstart I have successfully used for provisioning a Mustang board. d.marlin ========
|
Attachment:
F21-aarch64-RC7.ks
Description: application/java-keystore
_______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm