Chapter 22. Kickstart commands and options reference

--source= - URL for the driver disk. Examples include:

driverdisk --source=ftp://path/to/dd.img
driverdisk --source=http://path/to/dd.img
driverdisk --source=nfs:host:/path/to/dd.img

driverdisk --source=ftp://path/to/dd.img
driverdisk --source=http://path/to/dd.img
driverdisk --source=nfs:host:/path/to/dd.img

--nogpg - Disable GPG key verification.

For more information about the OStree tools, see the upstream documentation: https://ostreedev.github.io/ostree/

--transport: The transport, for example, registry or oci. The default value is registry.

When performing Kickstart installations, the following commands are available together with ostreecontainer:

user - When you specify a group within the user command, the user account can be assigned only to a group that already exists in the container image.

The following Kickstart commands are unsupported together with ostreecontainer:

zipl

Kickstart commands not listed here are allowed to be used with the ostreecontainer command, however, they are not guaranteed to work as expected in the same way as with package-based installations.

--kexec - Uses the kexec system call instead of performing a full reboot, which immediately loads the installed system into memory, bypassing the hardware initialization normally performed by the BIOS or firmware.

If you want to disable root ssh access, while allowing another user ssh access, use the following:

sshpw --username=example_username example_password --plaintext
sshpw --username=root example_password --lock

sshpw --username=example_username example_password --plaintext
sshpw --username=root example_password --lock

To simply disable root ssh access, use the following:

sshpw --username=root example_password --lock

sshpw --username=root example_password --lock

To install from a FTP server:

url --url=ftp://username:password@server/path

url --url=ftp://username:password@server/path

To install from a HTTP server:

url --url=http://server/path

url --url=http://server/path

incoming - Replace with one or more of the following to allow the specified services through the firewall.

--service= - This option provides a higher-level way to allow services through the firewall. Some services (such as cups, avahi, and so on) require multiple ports to be open or other special configuration in order for the service to work. You can specify each individual port with the --port option, or specify --service= and open them all at once.

Valid options are anything recognized by the firewall-offline-cmd program in the firewalld package. If the firewalld service is running, firewall-cmd --get-services provides a list of known service names.

--xlayouts= - Specify a list of X layouts that should be used as a comma-separated list without spaces. Accepts values in the same format as setxkbmap(1), either in the layout format (such as cz), or in the layout (variant) format (such as cz (qwerty)).

All available layouts can be viewed on the xkeyboard-config(7) man page under Layouts.

--switch= - Specify a list of layout-switching options (shortcuts for switching between multiple keyboard layouts). Multiple options must be separated by commas without spaces. Accepts values in the same format as setxkbmap(1).

Available switching options can be viewed on the xkeyboard-config(7) man page under Options.

Multiple services should be included separated by comma, without any spaces. For example, to disable four services, enter:

services --disabled=auditd,cups,smartd,nfslock

services --disabled=auditd,cups,smartd,nfslock

If you include any spaces, Kickstart enables or disables only the services up to the first space. For example:

services --disabled=auditd, cups, smartd, nfslock

services --disabled=auditd, cups, smartd, nfslock

That disables only the auditd service. To disable all four services, this entry must include no spaces.

--role= - Set the intended system role. Available values are:

--sla= - Set the Service Level Agreement. Available values are:

--usage= - The intended usage of the system. Available values are:

--iscrypted - If this option is present, the password argument is assumed to already be encrypted. This option is mutually exclusive with --plaintext. To create an encrypted password, you can use python:

python -c 'import crypt,getpass;pw=getpass.getpass();print(crypt.crypt(pw) if (pw==getpass.getpass("Confirm: ")) else exit())'

$ python -c 'import crypt,getpass;pw=getpass.getpass();print(crypt.crypt(pw) if (pw==getpass.getpass("Confirm: ")) else exit())'

This generates a sha512 crypt-compatible hash of your password by using a random salt.

Files and directories are created with various permissions, dictated by the application used to create the file or directory. For example, the mkdir command creates directories with all permissions enabled. However, applications are prevented from granting certain permissions to newly created files, as specified by the user file-creation mask setting.

The user file-creation mask can be controlled with the umask command. The default setting of the user file-creation mask for new users is defined by the UMASK variable in the /etc/login.defs configuration file on the installed system. If unset, it defaults to 022. This means that by default when an application creates a file, it is prevented from granting write permission to users other than the owner of the file. However, this can be overridden by other settings or scripts.

--no-activate - do not activate this device in the installation environment.

By default, Anaconda activates the first network device in the Kickstart file regardless of the --activate option. You can disable the default setting by using the --no-activate option.

--bootproto= - One of dhcp, bootp, ibft, or static. The default option is dhcp; the dhcp and bootp options are treated the same. To disable ipv4 configuration of the device, use --noipv4 option.

The DHCP method uses a DHCP server system to obtain its networking configuration. The BOOTP method is similar, requiring a BOOTP server to supply the networking configuration. To direct a system to use DHCP:

network --bootproto=dhcp

network --bootproto=dhcp

To direct a machine to use BOOTP to obtain its networking configuration, use the following line in the Kickstart file:

network --bootproto=bootp

network --bootproto=bootp

To direct a machine to use the configuration specified in iBFT, use:

network --bootproto=ibft

network --bootproto=ibft

The static method requires that you specify at least the IP address and netmask in the Kickstart file. This information is static and is used during and after the installation.

All static networking configuration information must be specified on one line; you cannot wrap lines by using a backslash (\) as you can on a command line.

network --bootproto=static --ip=10.0.2.15 --netmask=255.255.255.0 --gateway=10.0.2.254 --nameserver=10.0.2.1

network --bootproto=static --ip=10.0.2.15 --netmask=255.255.255.0 --gateway=10.0.2.254 --nameserver=10.0.2.1

You can also configure multiple nameservers at the same time. To do so, use the --nameserver= option once, and specify each of their IP addresses, separated by commas:

network --bootproto=static --ip=10.0.2.15 --netmask=255.255.255.0 --gateway=10.0.2.254 --nameserver=192.168.2.1,192.168.3.1

network --bootproto=static --ip=10.0.2.15 --netmask=255.255.255.0 --gateway=10.0.2.254 --nameserver=192.168.2.1,192.168.3.1

--device= - specifies the device to be configured (and eventually activated in Anaconda) with the network command.

If the --device= option is missing on the first use of the network command, the value of the inst.ks.device= Anaconda boot option is used, if available. This is considered deprecated behavior; in most cases, you should always specify a --device= for every network command.

The behavior of any subsequent network command in the same Kickstart file is unspecified if its --device= option is missing. Verify you specify this option for any network command beyond the first.

You can specify a device to be activated in any of the following ways:

For example:

network --bootproto=dhcp --device=em1

network --bootproto=dhcp --device=em1

--ipv4-dns-search/--ipv6-dns-search - Set the DNS search domains manually. You must use these options together with --device options and mirror their respective NetworkManager properties, for example:

network --device ens3 --ipv4-dns-search domain1.example.com,domain2.example.com

network --device ens3 --ipv4-dns-search domain1.example.com,domain2.example.com

--hostname= - Used to configure the target system’s host name. The host name can either be a fully qualified domain name (FQDN) in the format hostname.domainname, or a short host name without the domain. Many networks have a Dynamic Host Configuration Protocol (DHCP) service that automatically supplies connected systems with a domain name. To allow the DHCP service to assign the domain name to this machine, specify only the short host name.

When using static IP and host name configuration, it depends on the planned system use case whether to use a short name or FQDN. Red Hat Identity Management configures FQDN during provisioning but some 3rd party software products may require a short name. In either case, to ensure availability of both forms in all situations, add an entry for the host in /etc/hosts in the format IP FQDN short-alias.

Host names can only contain alphanumeric characters and - or .. Host name should be equal to or less than 64 characters. Host names cannot start or end with - and .. To be compliant with DNS, each part of a FQDN should be equal to or less than 63 characters and the FQDN total length, including dots, should not exceed 255 characters.

If you only want to configure the target system’s host name, use the --hostname option in the network command and do not include any other option.

If you provide additional options when configuring the host name, the network command configures a device by using the options specified. If you do not specify which device to configure by using the --device option, the default --device link value is used. Additionally, if you do not specify the protocol by using the --bootproto option, the device is configured to use DHCP by default.

--bondslaves= - When this option is used, the bond device specified by the --device= option is created using secondary devices defined in the --bondslaves= option. For example:

network --device=bond0 --bondslaves=em1,em2

network --device=bond0 --bondslaves=em1,em2

The above command creates a bond device named bond0 by using the em1 and em2 interfaces as its secondary devices.

--bondopts= - a list of optional parameters for a bonded interface, which is specified by using the --bondslaves= and --device= options. Options in this list must be separated by commas (“,”) or semicolons (“;”). If an option itself contains a comma, use a semicolon to separate the options. For example:

network --bondopts=mode=active-backup,balance-rr;primary=eth1

network --bondopts=mode=active-backup,balance-rr;primary=eth1

--interfacename= - Specify a custom interface name for a virtual LAN device. This option should be used when the default name generated by the --vlanid= option is not desirable. This option must be used along with --vlanid=. For example:

network --device=em1 --vlanid=171 --interfacename=vlan171

network --device=em1 --vlanid=171 --interfacename=vlan171

The above command creates a virtual LAN interface named vlan171 on the em1 device with an ID of 171.

The interface name can be arbitrary (for example, my-vlan), but in specific cases, the following conventions must be followed:

--bridgeslaves= - When this option is used, the network bridge with device name specified by using the --device= option will be created and devices defined in the --bridgeslaves= option will be added to the bridge. For example:

network --device=bridge0 --bridgeslaves=em1

network --device=bridge0 --bridgeslaves=em1

--bridgeopts= - An optional comma-separated list of parameters for the bridged interface. Available values are stp, priority, forward-delay, hello-time, max-age, and ageing-time. For information about these parameters, see the bridge setting table in the nm-settings(5) man page or at Network Configuration Setting Specification.

Also see the Configuring and managing networking document for general information about network bridging.

--only-use=driveN,…​ - Specifies a list of disks for the installation program to use. All other disks are ignored. For example, to use disk sda during installation and ignore all other disks:

ignoredisk --only-use=sda

ignoredisk --only-use=sda

To include a multipath device that does not use LVM:

ignoredisk --only-use=disk/by-id/dm-uuid-mpath-2416CD96995134CA5D787F00A5AA11017

ignoredisk --only-use=disk/by-id/dm-uuid-mpath-2416CD96995134CA5D787F00A5AA11017

To include a multipath device that uses LVM:

ignoredisk --only-use=disk/by-id/scsi-58095BEC5510947BE8C0360F604351918

ignoredisk --only-use=disk/by-id/scsi-58095BEC5510947BE8C0360F604351918

You must specify only one of the --drives or --only-use.

The sdX (or /dev/sdX) format does not guarantee consistent device names across reboots, which can complicate the usage of some Kickstart commands. When a command requires a device node name, you can use any item from /dev/disk as an alternative. For example, instead of using the following device name:

ignoredisk --only-use=sda

ignoredisk --only-use=sda

You can use an entry similar to one of the following:

ignoredisk --only-use=/dev/disk/by-path/pci-0000:00:05.0-scsi-0:0:0:0
ignoredisk --only-use=/dev/disk/by-id/ata-ST3160815AS_6RA0C882

ignoredisk --only-use=/dev/disk/by-path/pci-0000:00:05.0-scsi-0:0:0:0
ignoredisk --only-use=/dev/disk/by-id/ata-ST3160815AS_6RA0C882

By using this approach, the command always targets the same storage device. This is especially useful in large storage environments. To explore the available device names on the system, you can use the ls -lR /dev/disk command during the interactive installation. For more information about different ways to consistently refer to storage devices, see Persistent naming attributes.

--drives= - Specifies which drives to clear partitions from. For example, the following clears all the partitions on the first two drives on the primary IDE controller:

clearpart --drives=hda,hdb --all

clearpart --drives=hda,hdb --all

To clear a multipath device, use the format disk/by-id/scsi-WWID, where WWID is the world-wide identifier for the device. For example, to clear a disk with WWID 58095BEC5510947BE8C0360F604351918, use:

clearpart --drives=disk/by-id/scsi-58095BEC5510947BE8C0360F604351918

clearpart --drives=disk/by-id/scsi-58095BEC5510947BE8C0360F604351918

This format is preferable for all multipath devices, but if errors arise, multipath devices that do not use logical volume manager (LVM) can also be cleared using the format disk/by-id/dm-uuid-mpath-WWID, where WWID is the world-wide identifier for the device. For example, to clear a disk with WWID 2416CD96995134CA5D787F00A5AA11017, use:

clearpart --drives=disk/by-id/dm-uuid-mpath-2416CD96995134CA5D787F00A5AA11017

clearpart --drives=disk/by-id/dm-uuid-mpath-2416CD96995134CA5D787F00A5AA11017

Never specify multipath devices by device names like mpatha. Device names such as this are not specific to a particular disk. The disk named /dev/mpatha during installation might not be the one that you expect it to be. Therefore, the clearpart command could target the wrong disk.

--initlabel - Initializes a disk (or disks) by creating a default disk label for all disks in their respective architecture that have been designated for formatting (for example, gpt for x86). Because --initlabel can see all disks, it is important to ensure only those drives that are to be formatted are connected. Disks cleared by clearpart will have the label created even in case the --initlabel is not used.

clearpart --initlabel --drives=names_of_disks

clearpart --initlabel --drives=names_of_disks

For example:

clearpart --initlabel --drives=dasda,dasdb,dasdc

clearpart --initlabel --drives=dasda,dasdb,dasdc

--list= - Specifies which partitions to clear. This option overrides the --all and --linux options if used. Can be used across different drives. For example:

clearpart --list=sda2,sda3,sdb1

clearpart --list=sda2,sda3,sdb1

On the x86_64 systems running in Legacy BIOS mode, the GPT disklabel is the default. To ensure these systems can boot properly with GPT, add a dedicated BIOS boot partition. For automated installations, consider using the reqpart kickstart command to create this BIOS boot partition when required automatically. Optionally, use the part kickstart command, for example: part biosboot --size=1. If you prefer to stick with the older MBR partitioning scheme instead of GPT, you have two options:

To specify a multipath device, use the format disk/by-id/scsi-WWID, where WWID is the world-wide identifier for the device. For example, to specify a disk with WWID 58095BEC5510947BE8C0360F604351918, use:

ignoredisk --only-use=disk/by-id/scsi-58095BEC5510947BE8C0360F604351918

ignoredisk --only-use=disk/by-id/scsi-58095BEC5510947BE8C0360F604351918

This format is preferable for all multipath devices, but if errors arise, multipath devices that do not use logical volume manager (LVM) can also be specified by using the format disk/by-id/dm-uuid-mpath-WWID, where WWID is the world-wide identifier for the device. For example, to specify a disk with WWID 2416CD96995134CA5D787F00A5AA11017, use:

ignoredisk --only-use=disk/by-id/dm-uuid-mpath-2416CD96995134CA5D787F00A5AA11017

ignoredisk --only-use=disk/by-id/dm-uuid-mpath-2416CD96995134CA5D787F00A5AA11017

Never specify multipath devices by device names like mpatha. Device names such as this are not specific to a particular disk. The disk named /dev/mpatha during installation might not be the one that you expect it to be. Therefore, the ignoredisk command could target the wrong disk.

The sdX (or /dev/sdX) format does not guarantee consistent device names across reboots, which can complicate the usage of some Kickstart commands. When a command requires a device node name, you can use any item from /dev/disk as an alternative. For example, instead of using the following device name:

clearpart --drives=sda

clearpart --drives=sda

You can use an entry similar to one of the following:

clearpart --drives=/dev/disk/by-path/pci-0000:00:05.0-scsi-0:0:0:0
clearpart --drives=/dev/disk/by-id/ata-ST3160815AS_6RA0C882

clearpart --drives=/dev/disk/by-path/pci-0000:00:05.0-scsi-0:0:0:0
clearpart --drives=/dev/disk/by-id/ata-ST3160815AS_6RA0C882

By using this approach, the command always targets the same storage device. This is especially useful in large storage environments. To explore the available device names on the system, you can use the ls -lR /dev/disk command during the interactive installation. For more information about different ways to consistently refer to storage devices, see Persistent naming attributes.

--boot-drive= - Specifies which drive the boot loader should be written to, and therefore which drive the computer will boot from. If you use a multipath device as the boot drive, specify the device by using its disk/by-id/dm-uuid-mpath-WWID name.

--driveorder= - Specifies which drive is first in the BIOS boot order. For example:

bootloader --driveorder=sda,hda

bootloader --driveorder=sda,hda

--location= - Specifies where the boot record is written. Valid values are the following:

In most cases, this option does not need to be specified.

--password= - If using GRUB2, set the boot loader password to the one specified with this option. This should be used to restrict access to the GRUB2 shell, where arbitrary kernel options can be passed.

If a password is specified, GRUB2 also asks for a user name. The user name is always root.

--iscrypted - Normally, when you specify a boot loader password by using the --password= option, it is stored in the Kickstart file in plain text. If you want to encrypt the password, use this option and an encrypted password.

To generate an encrypted password, use the grub2-mkpasswd-pbkdf2 command, enter the password you want to use, and copy the command’s output (the hash starting with grub.pbkdf2) into the Kickstart file. An example bootloader Kickstart entry with an encrypted password looks similar to the following:

bootloader --iscrypted --password=grub.pbkdf2.sha512.10000.5520C6C9832F3AC3D149AC0B24BE69E2D4FB0DBEEDBD29CA1D30A044DE2645C4C7A291E585D4DC43F8A4D82479F8B95CA4BA4381F8550510B75E8E0BB2938990.C688B6F0EF935701FF9BD1A8EC7FE5BD2333799C98F28420C5CC8F1A2A233DE22C83705BB614EA17F3FDFDF4AC2161CEA3384E56EB38A2E39102F5334C47405E

bootloader --iscrypted --password=grub.pbkdf2.sha512.10000.5520C6C9832F3AC3D149AC0B24BE69E2D4FB0DBEEDBD29CA1D30A044DE2645C4C7A291E585D4DC43F8A4D82479F8B95CA4BA4381F8550510B75E8E0BB2938990.C688B6F0EF935701FF9BD1A8EC7FE5BD2333799C98F28420C5CC8F1A2A233DE22C83705BB614EA17F3FDFDF4AC2161CEA3384E56EB38A2E39102F5334C47405E

The sdX (or /dev/sdX) format does not guarantee consistent device names across reboots, which can complicate the usage of some Kickstart commands. When a command requires a device node name, you can use any item from /dev/disk as an alternative. For example, instead of using the following device name:

bootloader --boot-drive=sda

bootloader --boot-drive=sda

You can use an entry similar to one of the following:

bootloader --boot-drive=/dev/disk/by-path/pci-0000:00:05.0-scsi-0:0:0:0
bootloader --boot-drive=/dev/disk/by-id/ata-ST3160815AS_6RA0C882

bootloader --boot-drive=/dev/disk/by-path/pci-0000:00:05.0-scsi-0:0:0:0
bootloader --boot-drive=/dev/disk/by-id/ata-ST3160815AS_6RA0C882

By using this approach, the command always targets the same storage device. This is especially useful in large storage environments. To explore the available device names on the system, you can use the ls -lR /dev/disk command during the interactive installation. For more information about different ways to consistently refer to storage devices, see Persistent naming attributes.

--type= - Selects one of the predefined automatic partitioning schemes you want to use. Accepts the following values:

--encrypted - Encrypts all partitions with Linux Unified Key Setup (LUKS). This is equivalent to checking the Encrypt partitions check box on the initial partitioning screen during a manual graphical installation.

mntpoint - Where the partition is mounted. The value must be of one of the following forms:

--onpart= or --usepart= - Specifies the device on which to place the partition. Uses an existing blank device and formats it to the new specified type. For example:

partition /home --onpart=hda1

partition /home --onpart=hda1

puts /home on /dev/hda1.

These options can also add a partition to a logical volume. For example:

partition pv.1 --onpart=hda2

partition pv.1 --onpart=hda2

The device must already exist on the system; the --onpart option will not create it.

It is also possible to specify an entire drive, rather than a partition, in which case Anaconda will format and use the drive without creating a partition table. However, installation of GRUB2 is not supported on a device formatted in this way, and must be placed on a drive with a partition table.

partition pv.1 --onpart=hdb

partition pv.1 --onpart=hdb

--ondisk= or --ondrive= - Creates a partition (specified by the part command) on an existing disk.This command always creates a partition. Forces the partition to be created on a particular disk. For example, --ondisk=sdb puts the partition on the second SCSI disk on the system.

part / --size=5000 --ondisk=disk/by-id/scsi-58095BEC5510947BE8C0360F604351918

part / --size=5000 --ondisk=disk/by-id/scsi-58095BEC5510947BE8C0360F604351918

This format is preferable for all multipath devices, but if errors arise, multipath devices that do not use logical volume manager (LVM) can also be specified by using the format disk/by-id/dm-uuid-mpath-WWID, where WWID is the world-wide identifier for the device. For example, to specify a disk with WWID 2416CD96995134CA5D787F00A5AA11017, use:

part / --size=5000 --ondisk=disk/by-id/dm-uuid-mpath-2416CD96995134CA5D787F00A5AA11017

part / --size=5000 --ondisk=disk/by-id/dm-uuid-mpath-2416CD96995134CA5D787F00A5AA11017

Never specify multipath devices by device names like mpatha. Device names such as this are not specific to a particular disk. The disk named /dev/mpatha during installation might not be the one that you expect it to be. Therefore, the part command could target the wrong disk.

--mkfsoptions= - Specifies additional parameters to be passed to the program that makes a filesystem on this partition. This is similar to --fsprofile but works for all filesystems, not just the ones that support the profile concept. No processing is done on the list of arguments, so they must be supplied in a format that can be passed directly to the mkfs program. This means multiple options should be comma-separated or surrounded by double quotes, depending on the filesystem. For example,

part /opt/foo1 --size=512 --fstype=ext4 --mkfsoptions="-O ^has_journal,^flex_bg,^metadata_csum"

part /opt/foo2 --size=512 --fstype=xfs --mkfsoptions="-m bigtime=0,finobt=0"

part /opt/foo1 --size=512 --fstype=ext4 --mkfsoptions="-O ^has_journal,^flex_bg,^metadata_csum"

part /opt/foo2 --size=512 --fstype=xfs --mkfsoptions="-m bigtime=0,finobt=0"

For details, see the man pages of the filesystems you are creating. For example, mkfs.ext4 or mkfs.xfs.

--fsoptions - Specifies a free form string of options to be used when mounting the filesystem. This string will be copied into the /etc/fstab file of the installed system and should be enclosed in quotes.

--encrypted - Specifies that this partition should be encrypted with Linux Unified Key Setup (LUKS) by using the passphrase provided in the --passphrase option. If you do not specify a passphrase, Anaconda uses the default, system-wide passphrase set with the autopart --passphrase command, or stops the installation and prompts you to provide a passphrase if no default is set.

The sdX (or /dev/sdX) format does not guarantee consistent device names across reboots, which can complicate the usage of some Kickstart commands. When a command requires a device node name, you can use any item from /dev/disk as an alternative. For example, instead of using the following device name:

part / --fstype=xfs --onpart=sda1

part / --fstype=xfs --onpart=sda1

You can use an entry similar to one of the following:

part / --fstype=xfs --onpart=/dev/disk/by-path/pci-0000:00:05.0-scsi-0:0:0:0-part1
part / --fstype=xfs --onpart=/dev/disk/by-id/ata-ST3160815AS_6RA0C882-part1

part / --fstype=xfs --onpart=/dev/disk/by-path/pci-0000:00:05.0-scsi-0:0:0:0-part1
part / --fstype=xfs --onpart=/dev/disk/by-id/ata-ST3160815AS_6RA0C882-part1

By using this approach, the command always targets the same storage device. This is especially useful in large storage environments. To explore the available device names on the system, you can use the ls -lR /dev/disk command during the interactive installation. For more information about different ways to consistently refer to storage devices, see Persistent naming attributes.

--device= - Name of the RAID device to use - for example, --device=root.

--mkfsoptions= - Specifies additional parameters to be passed to the program that makes a filesystem on this partition. No processing is done on the list of arguments, so they must be supplied in a format that can be passed directly to the mkfs program. This means multiple options should be comma-separated or surrounded by double quotes, depending on the filesystem. For example,

part /opt/foo1 --size=512 --fstype=ext4 --mkfsoptions="-O ^has_journal,^flex_bg,^metadata_csum"

part /opt/foo2 --size=512 --fstype=xfs --mkfsoptions="-m bigtime=0,finobt=0"

part /opt/foo1 --size=512 --fstype=ext4 --mkfsoptions="-O ^has_journal,^flex_bg,^metadata_csum"

part /opt/foo2 --size=512 --fstype=xfs --mkfsoptions="-m bigtime=0,finobt=0"

For details, see the man pages of the filesystems you are creating. For example, mkfs.ext4 or mkfs.xfs.

--encrypted - Specifies that this RAID device should be encrypted with Linux Unified Key Setup (LUKS) by using the passphrase provided in the --passphrase option. If you do not specify a passphrase, Anaconda uses the default, system-wide passphrase set with the autopart --passphrase command, or stops the installation and prompts you to provide a passphrase if no default is set.

--useexisting - Use an existing volume group and reformat it. If you use this option, do not specify a partition. For example:

volgroup rhel00 --useexisting --noformat

volgroup rhel00 --useexisting --noformat

Do not use the dash (-) character in logical volume and volume group names when installing Red Hat Enterprise Linux by using Kickstart. If this character is used, the installation finishes normally, but the /dev/mapper/ directory will list these volumes and volume groups with every dash doubled. For example, a volume group named volgrp-01 containing a logical volume named logvol-01 will be listed as /dev/mapper/volgrp--01-logvol--01.

This limitation only applies to newly created logical volume and volume group names. If you are reusing existing ones by using the --noformat option, their names will not be changed.

mntpoint: The mount point where the partition is mounted. Must be of one of the following forms:

--fsoptions=: Specifies a free form string of options to be used when mounting the filesystem. This string will be copied into the /etc/fstab file of the installed system and should be enclosed in quotes.

--mkfsoptions=: Specifies additional parameters to be passed to the program that makes a filesystem on this partition. No processing is done on the list of arguments, so they must be supplied in a format that can be passed directly to the mkfs program. This means multiple options should be comma-separated or surrounded by double quotes, depending on the filesystem. For example,

part /opt/foo1 --size=512 --fstype=ext4 --mkfsoptions="-O ^has_journal,^flex_bg,^metadata_csum"

part /opt/foo2 --size=512 --fstype=xfs --mkfsoptions="-m bigtime=0,finobt=0"

part /opt/foo1 --size=512 --fstype=ext4 --mkfsoptions="-O ^has_journal,^flex_bg,^metadata_csum"

part /opt/foo2 --size=512 --fstype=xfs --mkfsoptions="-m bigtime=0,finobt=0"

For details, see the man pages of the filesystems you are creating. For example, mkfs.ext4 or mkfs.xfs.

--percent=: The size of the logical volume, as a percentage of the free space in the volume group after any statically-sized logical volumes are taken into account. This option cannot be used together with the --size= option.

--encrypted: Specifies that this logical volume should be encrypted with Linux Unified Key Setup (LUKS) by using the passphrase provided in the --passphrase= option. If you do not specify a passphrase, the installation program stops the installation and prompts you to provide a passphrase if no default is set.

--cachemode=: Specify which mode should be used to cache this logical volume - either writeback or writethrough.

Create the partition first, create the volume group, and then create the logical volume to occupy 90% of the remaining space in the volume group:

part pv.01 --size 1 --grow
volgroup myvg pv.01
logvol / --vgname=myvg --name=rootvol --percent=90

part pv.01 --size 1 --grow
volgroup myvg pv.01
logvol / --vgname=myvg --name=rootvol --percent=90

--reserve-mb= - The amount of memory you want to reserve for kdump, in MiB. For example:

%addon com_redhat_kdump --enable --reserve-mb=128
%end

%addon com_redhat_kdump --enable --reserve-mb=128
%end

You can also specify auto instead of a numeric value. In that case, the installation program will determine the amount of memory automatically based on the criteria described in the Memory requirements for kdump section of the Managing, monitoring and updating the kernel document.

If you enable kdump and do not specify a --reserve-mb= option, the value auto will be used.