Hide Forgot
Problem Description -------------------------------- This issue is observed in RHEL7.0 pre beta Steps to reproduce -------------------------- 1. Add more than 30 parameters in .prm file, 2. kickstart the installation What is the restriction for number of parameters in param file? if its exceeds then what is the way to use conf file? Param file attached
Created attachment 826565 [details] .prm file
You can use conf file the same way as in RHEL-6 -use CMSDASD and CMSCONFFILE boot options in your parameter file, for example: ro ramdisk_size=40000 cio_ignore=all,!0.0.0009 CMSDASD=0191 CMSCONFFILE=r7.conf inst.repo=<path_to_repository> Conf file from RHEL-6 should not need any modification to work in RHEL7, for example: HOSTNAME="hostname" IPADDR="xx.xx.xx.xx" NETTYPE="qeth" PORTNAME="FOOBAR" LAYER2=0 VSWITCH=1 SUBCHANNELS="0.0.0c00,0.0.0c01,0.0.0c02" NETMASK="xx.xx.xx.xx" GATEWAY="xx.xx.xx.xx" SEARCHDNS="searchdns" DNS="xx.xx.xx.xx" MTU="4096" PORTNO=0 DASD=3527,3621,3622,3625,3627,3721,3722,3727 FCP_1="A007 0x500507630503C73D 0x4020400700000000" FCP_2="A007 0x500507630503C73D 0x4020400600000000" Regarding the number of parameters in parameter file - it seems that it is not possible to use more than 891 characters in the parameter file - if the parameter file is longer, only the first 891 characters are visible in /proc/cmdline: [anaconda root@rtt7 ~]# cat /proc/cmdline | wc -c 891 [anaconda root@rtt7 ~]# I found following in source code of kernel: jstodola@unused-4-186 ~/tmp/kernel/linux-3.10.0-53.el7$ grep -ri ARCH_COMMAND_LINE_SIZE arch/s390/kernel/early.c: COMMAND_LINE[ARCH_COMMAND_LINE_SIZE - 1] = 0; arch/s390/kernel/early.c: EBCASC(COMMAND_LINE, ARCH_COMMAND_LINE_SIZE); arch/s390/kernel/early.c: ARCH_COMMAND_LINE_SIZE); arch/s390/include/uapi/asm/setup.h:#define ARCH_COMMAND_LINE_SIZE 896 jstodola@unused-4-186 ~/tmp/kernel/linux-3.10.0-53.el7$
Closing per comment #4. Lots of parameters have to use the CMSCONFFILE as did previous RHEL releases. The limitation of the param file contents is not imposed by us, that's an IBM limitation.