Product SiteDocumentation Site

8.2.5. Advanced Installation Options

Configure the system for multilib packages (that is, to allow installing 32-bit packages on a 64-bit x86 system) and install packages specified in this section as such.
Normally, on an AMD64 or Intel 64 system, only packages for this architecture (marked as x86_64) and packages for all architectures (marked as noarch would be installed. When you use this option, packages for 32-bit AMD or Intel systems (marked as i686) will be automatically installed as well if available.
This only applies to packages directly specified in the %packages section. If a package is only installed as a dependency, only the exact specified dependency will be installed. For example, if you are installing package foo which depends on package bar, the former will be installed in multiple variants, while the latter will only be installed in variants specifically required.
Force the installation program to install partition information into a GUID Partition Table (GPT) instead of a Master Boot Record (MBR). This option is meaningless on UEFI-based systems, unless they are in BIOS compatibility mode.
Normally, BIOS-based systems and UEFI-based systems in BIOS compatibility mode will attempt to use the MBR schema for storing partitioning information, unless the disk is larger than 2 TB. Using this option will change this behavior, allowing a GPT to be written even to disks smaller than 2 TB.
See Section, “Recommended Partitioning Scheme” for more information about GPT and MBR, and Section B.1.4, “GUID Partition Table (GPT)” for more general information about GPT, MBR and disk partitioning in general.
This option controls which Kickstart files and installation logs are saved to the installed system. It can be especially useful to disable saving such data when performing OEM operating system installations, or when generating images using sensitive resources (such as internal repository URLs), as these resources might otherwise be mentioned in kickstart files and/or logs on the image. Possible values for this option are:
input_ks - disables saving of the input Kickstart file (if any).
output_ks - disables saving of the output Kickstart file generated by Anaconda.
all_ks - disables saving of both input and output Kickstart files.
logs - disables saving of all installation logs.
all - disables saving of all Kickstart files and all installation logs.
Multiple values can be combined as a comma separated list, for example: input_ks,logs
This option controls the usage of zRAM swap during the installation. It creates a compressed block device inside the system RAM and uses it for swap space instead of the hard drive. This allows the installer to essentially increase the amount of memory available, which makes the installation faster on systems with low memory.
By default, swap on zRAM is enabled on systems with 2 GB or less RAM, and disabled on systems with more than 2 GB of memory. You can use this option to change this behavior - on a system with more than 2 GB RAM, use inst.zram=1 to enable it, and on systems with 2 GB or less memory, use inst.zram=0 to disable this feature.
Perform a check at the beginning of the installation to determine if there is enough available RAM. If there is not enough memory detected, the installation will stop with an error message. This option is enabled by default; use inst.memcheck=0 to disable it.
Use the older Yum backend for package installation and dependency resolution instead of DNF. See the Fedora System Administrator's Guide, available at, for details about DNF.
Turns the Kdump installer add-on on or off (the add-on is off by default). If you use inst.kdump_addon=on, a new screen, which allows you to configure the Kdump kernel crash dumping mechanism, will appear in the main menu of the graphical or text interface (see Section 5.4.11, “Kdump”). Enabling this add-on is also necessary to use the Section A.7.1, “%addon com_redhat_kdump (optional) - Configure kdump” Kickstart command.
With this option, warnings encountered when reading a Kickstart file will be treated as errors - they will be printed on the output and the installation will terminate. Without this option, the warnings are only printed to log and the installation continues.