Red Hat Summit Red Hat SummitSuporteConsoleDesenvolvedoresComeçar um testeContato

Este conteúdo não está disponível no idioma selecionado.

Chapter 23. Boot options reference

You can use the boot options to modify the default behavior of the installation program.

23.1. Installation source boot options
Copiar o link

You can configure installation source boot options to specify where RHEL installation files are located. These options enable installations from various sources including local media, network servers, and additional repositories, providing flexibility in deployment scenarios.

inst.repo=

The inst.repo= boot option specifies the installation source, that is, the location providing the package repositories and a valid .treeinfo file that describes them. For example: inst.repo=cdrom. The target of the inst.repo= option must be one of the following installation media:

  • an installable tree, which is a directory structure containing the installation program images, packages, and repository data as well as a valid .treeinfo file
  • a DVD (a physical disk present in the system DVD drive)

  • an ISO image of the full Red Hat Enterprise Linux installation DVD, placed on a disk or a network location accessible to the system.

    Use the inst.repo= boot option to configure different installation methods by using different formats. The following table contains details of the inst.repo= boot option syntax:

    Expand
    Table 23.1. Types and format for the inst.repo= boot option and installation source
    Source typeBoot option formatSource format

    CD/DVD drive

    inst.repo=cdrom:<device>

    Installation DVD as a physical disk. [a]

    Mountable device (HDD and USB stick)

    inst.repo=hd:<device>:/<path>

    Image file of the installation DVD.

    NFS Server

    inst.repo=nfs:[options:]<server>:/<path>

    Image file of the installation DVD, or an installation tree, which is a complete copy of the directories and files on the installation DVD. [b]

    HTTP Server

    inst.repo=http://<host>/<path>

    Installation tree that is a complete copy of the directories and files on the installation DVD.

    HTTPS Server

    inst.repo=https://<host>/<path>

    FTP Server

    inst.repo=ftp://<username>:<password>@<host>/<path>

    HMC

    inst.repo=hmc

    		 
    [a] If device is left out, installation program automatically searches for a drive containing the installation DVD.
    [b] The NFS Server option uses NFS protocol version 3 by default. To use a different version, add nfsvers=X to options, replacing X with the version number that you want to use.

Set disk device names with the following formats:

  • Kernel device name, for example /dev/sda1 or sdb2
  • File system label, for example LABEL=Flash or LABEL=RHEL8

  • File system UUID, for example UUID=8176c7bf-04ff-403a-a832-9557f94e61db

    Non-alphanumeric characters must be represented as \xNN, where NN is the hexadecimal representation of the character. For example, \x20 is a white space (" ").

    inst.addrepo=

    Use the inst.addrepo= boot option to add an additional repository that you can use as another installation source along with the main repository (inst.repo=). You can use the inst.addrepo= boot option multiple times during one boot. The following table contains details of the inst.addrepo= boot option syntax.

    Note

    The REPO_NAME is the name of the repository and is required in the installation process. These repositories are only used during the installation process; they are not installed on the installed system.

    Expand
    Table 23.2. Installation sources and boot option format
    Installation sourceBoot option formatAdditional information

    Installable tree at a URL

    inst.addrepo=REPO_NAME,[http,https,ftp]://<host>/<path>

    Looks for the installable tree at a given URL.

    Installable tree at an NFS path

    inst.addrepo=REPO_NAME,nfs://<server>:/<path>

    Looks for the installable tree at a given NFS path. A colon is required after the host. The installation program passes everything after nfs:// directly to the mount command instead of parsing URLs according to RFC 2224.

    Installable tree in the installation environment

    inst.addrepo=REPO_NAME,file://<path>

    Looks for the installable tree at the given location in the installation environment. To use this option, the repository must be mounted before the installation program attempts to load the available software groups. The benefit of this option is that you can have multiple repositories on one bootable ISO, and you can install both the main repository and additional repositories from the ISO. The path to the additional repositories is /run/install/source/REPO_ISO_PATH. Additionally, you can mount the repository directory in the %pre section in the Kickstart file. The path must be absolute and start with /, for example inst.addrepo=REPO_NAME,file:///<path>

    Disk

    inst.addrepo=REPO_NAME,hd:<device>:<path>

    Mounts the given <device> partition and installs from the ISO that is specified by the <path>. If the <path> is not specified, the installation program looks for a valid installation ISO on the <device>. This installation method requires an ISO with a valid installable tree.

    inst.stage2=

    The inst.stage2= boot option specifies the location of the installation program’s runtime image. This option expects the path to a directory that contains a valid .treeinfo file and reads the runtime image location from the .treeinfo file. If the .treeinfo file is not available, the installation program attempts to load the image from images/install.img.

    When you do not specify the inst.stage2 option, the installation program attempts to use the location specified with the inst.repo option.

    You can use this option when you want to manually specify the installation source in the installation program at a later time. For example, when you want to select the Content Delivery Network (CDN) as an installation source. The installation DVD and Boot ISO already contain a suitable inst.stage2 option to boot the installation program from the respective ISO.

    If you want to specify an installation source, use the inst.repo= option instead.

    Note

    By default, the inst.stage2= boot option is used on the installation media and is set to a specific label; for example, inst.stage2=hd:LABEL=RHEL-x-0-0-BaseOS-x86_64. If you modify the default label of the file system that contains the runtime image, or if you use a customized procedure to boot the installation system, verify that the inst.stage2= boot option is set to the correct value.

    inst.noverifyssl

    Use the inst.noverifyssl boot option to prevent the installer from verifying SSL certificates for all HTTPS connections with the exception of additional Kickstart repositories, where --noverifyssl can be set per repository.

    For example, if your remote installation source is using self-signed SSL certificates, the inst.noverifyssl boot option enables the installer to complete the installation without verifying the SSL certificates. For example, when specifying the source by using inst.stage2=: 

    inst.stage2=https://hostname/path_to_install_image/ inst.noverifyssl
    Copy to Clipboard Toggle word wrap

    And for example when specifying the source by using inst.repo=: 

    inst.repo=https://hostname/path_to_install_repository/ inst.noverifyssl
    Copy to Clipboard Toggle word wrap
    inst.stage2.all

    Use the inst.stage2.all boot option to specify several HTTP, HTTPS, or FTP sources. You can use the inst.stage2= boot option multiple times with the inst.stage2.all option to fetch the image from the sources sequentially until one succeeds. For example: 

    inst.stage2.all
inst.stage2=http://hostname1/path_to_install_tree/
inst.stage2=http://hostname2/path_to_install_tree/
inst.stage2=http://hostname3/path_to_install_tree/
    Copy to Clipboard Toggle word wrap
    inst.dd=
    The inst.dd= boot option is used to perform a driver update during the installation. For more information about how to update drivers during installation, see the Updating drivers during installation.
    inst.repo=hmc

    This option eliminates the requirement of an external network setup and expands the installation options. When booting from a Binary DVD, the installation program prompts you to enter additional kernel parameters. To set the DVD as an installation source, append the inst.repo=hmc option to the kernel parameters. The installation program then enables support element (SE) and hardware management console (HMC) file access, fetches the images for stage2 from the DVD, and provides access to the packages on the DVD for software selection.

    Important

    To use the inst.repo boot option, ensure the user is configured with a minimum of Privilege Class B. For more information about the user configuration, see IBM documentation.

    inst.proxy=

    This boot option is used when performing an installation from a HTTP, HTTPS, and FTP protocol in the following form: 

    [PROTOCOL://][USERNAME[:PASSWORD]@]HOST[:PORT]
For example:
http://proxyuser:proxypassword@10.1.2.3:3128
    Copy to Clipboard Toggle word wrap
    inst.nosave=

    Use the inst.nosave= boot option to control the installation logs and related files that are not saved to the installed system, for example input_ks, output_ks, all_ks, logs and all. You can combine multiple values separated by a comma. For example, 

    inst.nosave=input_ks,logs
    Copy to Clipboard Toggle word wrap
    Note

    The inst.nosave boot option is used for excluding files from the installed system that cannot be removed by a Kickstart %post script, such as logs and input/output Kickstart results.

    input_ks
    Disables the ability to save the input Kickstart results.
    output_ks
    Disables the ability to save the output Kickstart results generated by the installation program.
    all_ks
    Disables the ability to save the input and output Kickstart results.
    logs
    Disables the ability to save all installation logs.
    all
    Disables the ability to save all Kickstart results, and all logs.
    inst.multilib
    Use the inst.multilib boot option to set DNF’s multilib_policy to all, instead of best.
    inst.memcheck
    The inst.memcheck boot option performs a check to verify that the system has enough RAM to complete the installation. If there is not enough RAM, the installation process is stopped. The system check is approximate and memory usage during installation depends on the package selection, user interface, for example graphical or text, and other parameters.
    inst.nomemcheck
    The inst.nomemcheck boot option does not perform a check to verify if the system has enough RAM to complete the installation. Any attempt to perform the installation with less than the minimum amount of memory is unsupported, and might result in the installation process failing.

23.2. Network boot options
Copiar o link

You can configure network boot options to enable RHEL installation over network connections. These options allow you to set up network interfaces, specify IP addresses, configure bonding, bridging, and VLANs for network-based installations and remote system deployment.

+

Note

Initialize the network with the dracut tool. For a complete list of dracut options, see the dracut.cmdline(7) man page on your system.

ip=

Use the ip= boot option to configure one or more network interfaces. To configure multiple interfaces, use one of the following methods

  • use the ip option multiple times, once for each interface; to do so, use the rd.neednet=1 option, and specify a primary boot interface using the bootdev option.

  • use the ip option once, and then use Kickstart to set up further interfaces. While the configuration with ip= option is applied early in the installation process, the configuration defined in kickstart is applied at a later stage of installation, after the start of the installation program.

    This option accepts several different formats. The following tables contain information about the most common options. In the following tables:

  • The ip parameter specifies the client IP address and IPv6 requires square brackets, for example 192.0.2.1 or [2001:db8::99].
  • The gateway parameter is the default gateway. IPv6 requires square brackets.
  • The netmask parameter is the netmask to be used. This can be either a full netmask (for example, 255.255.255.0) or a prefix (for example, 64).

  • The hostname parameter is the host name of the client system. This parameter is optional.

    Expand
    Table 23.3. Boot option formats to configure the network interface
    Boot option formatConfiguration method

    ip=method

    Automatic configuration of all interfaces.

    ip=interface:method

    Automatic configuration of a specific interface

    ip=ip::gateway:netmask:hostname:interface:none

    Static configuration, for example, IPv4: ip=192.0.2.1::192.0.2.254:255.255.255.0:server.example.com:enp1s0:none

    IPv6: ip=[2001:db8::1]::[2001:db8::fffe]:64:server.example.com:enp1s0:none

    ip=ip::gateway:netmask:hostname:interface:method:mtu

    Automatic configuration of a specific interface with an override

Configuration methods for the automatic interface

The method automatic configuration of a specific interface with an override opens the interface by using the specified method of automatic configuration, such as dhcp, but overrides the automatically obtained IP address, gateway, netmask, host name or other specified parameters. All parameters are optional, so specify only the parameters that you want to override. For the values of the method parameter, see the dracut.cmdline(7) man page on your system.

Note
  • If you use a boot option that requires network access, such as inst.ks=http://host/path, without specifying the ip option, the default value of the ip option is ip=dhcp..
  • To connect to an iSCSI target automatically, activate a network device for accessing the target by using the ip=ibft boot option.

  • nameserver= - The nameserver= option specifies the address of the name server. You can use this option multiple times.

    Note

    The ip= parameter requires square brackets. However, an IPv6 address does not work with square brackets. An example of the correct syntax to use for an IPv6 address is nameserver=2001:db8::1.

  • bootdev= - The bootdev= option specifies the boot interface. This option is mandatory if you use more than one ip option.

  • ifname= - The ifname= options assigns an interface name to a network device with a given MAC address. You can use this option multiple times. The syntax is ifname=interface:MAC. For example: 

    ifname=eth0:01:23:45:67:89:ab
    Copy to Clipboard Toggle word wrap
    Note

    The ifname= option is the only supported way to set custom network interface names during installation.

  • inst.dhcpclass= - The inst.dhcpclass= option specifies the DHCP vendor class identifier. The dhcpd service recognizes this value as vendor-class-identifier. The default value is anaconda-$(uname -srm). To ensure the inst.dhcpclass= option is applied correctly, request network activation during the early stage of installation by also adding the ip option.
  • inst.waitfornet= - Using the inst.waitfornet=SECONDS boot option causes the installation system to wait for network connectivity before installation. The value given in the SECONDS argument specifies the maximum amount of time to wait for network connectivity before timing out and continuing the installation process even if network connectivity is not present.

  • vlan=- Use the vlan= option to configure a Virtual LAN (VLAN) device on a specified interface with a given name. The syntax is vlan=name:interface. For example: 

    vlan=vlan5:enp0s1
    Copy to Clipboard Toggle word wrap

    This configures a VLAN device named vlan5 on the enp0s1 interface. The name can take the following forms:

    • VLAN_PLUS_VID: vlan0005
    • VLAN_PLUS_VID_NO_PAD: vlan5
    • DEV_PLUS_VID: enp0s1.0005
    • DEV_PLUS_VID_NO_PAD: enp0s1.5

  • bond= - Use the bond= option to configure a bonding device with the following syntax: bond=name[:interfaces][:options]. Replace name with the bonding device name, interfaces with a comma-separated list of physical (Ethernet) interfaces, and options with a comma-separated list of bonding options. For example: 

    bond=bond0:enp0s1,enp0s2:mode=active-backup,tx_queues=32,downdelay=5000
    Copy to Clipboard Toggle word wrap

    For a list of available options, execute the modinfo bonding command.

  • bridge= - Use the bridge= option to configure a bridge device with the following syntax: bridge=name:interfaces. Replace name with the desired name of the bridge device and interfaces with a comma-separated list of physical (Ethernet) devices to be used as underlying interfaces in the bridge device. For example: 

    bridge=bridge0:enp0s1,enp0s2
    Copy to Clipboard Toggle word wrap

23.3. Console boot options
Copiar o link

You can configure boot options for your console, monitor display, and keyboard to customize the installation process.

console=
Use the console= option to specify a device that you want to use as the primary console. For example, to use a console on the first serial port, use console=ttyS0. When using the console= argument, the installation starts with a text UI. If you must use the console= option multiple times, the boot message is displayed on all specified consoles. However, the installation program uses only the last specified console. For example, if you specify console=ttyS0 console=ttyS1, the installation program uses ttyS1.
inst.lang=
Use the inst.lang= option to set the language that you want to use during the installation. To view the list of locales, enter the command locale -a | grep _ or the localectl list-locales | grep _ command.
inst.geoloc=

Use the inst.geoloc= option to configure geolocation usage in the installation program. Geolocation is used to preset the language and time zone, and uses the following syntax: inst.geoloc=value. The value can be any of the following parameters:

  • Disable geolocation: inst.geoloc=0
  • Use the Fedora GeoIP API: inst.geoloc=provider_fedora_geoip. This option is deprecated.
  • Use the Hostip.info GeoIP API: inst.geoloc=provider_hostip. This option is deprecated.
inst.keymap=
Use the inst.keymap= option to specify the keyboard layout to use for the installation.
inst.cmdline
Use the inst.cmdline option to force the installation program to run in command-line mode. This mode does not allow any interaction, and you must specify all options in a Kickstart file or on the command line.
inst.graphical
Use the inst.graphical option to force the installation program to run in graphical mode. The graphical mode is the default.
inst.text
Use the inst.text option to force the installation program to run in text mode instead of graphical mode.
inst.noninteractive
Use the inst.noninteractive boot option to run the installation program in a non-interactive mode. User interaction is not permitted in the non-interactive mode, and inst.noninteractive you can use the inst.nointeractive option with a graphical or text installation. When you use the inst.noninteractive option in text mode, it behaves the same as the inst.cmdline option.
Note

It only makes sense to use the inst.noninteractive option when performing a Kickstart installation.

inst.resolution=
Use the inst.resolution= option to specify the screen resolution in graphical mode. The format is NxM, where N is the screen width and M is the screen height (in pixels). The recommended resolution is 1024x768.
inst.rdp
Use the inst.rdp option to run the graphical installation using remote desktop protocol. If no RDP username (by using inst.rdpuser=) or password (by using inst.rdp.password=) are specified, the installation program asks users to provide interactively. This option only applies if used together with the inst.rdp option.
inst.rdp.password=
Use the inst.rdp.password= option to set a password on the RDP server that is used by the installation program.
modprobe.blacklist=

Use the modprobe.blacklist= option to blocklist or completely disable one or more drivers. Drivers (modules) that you disable using this option cannot load when the installation starts. After the installation finishes, the installed system retains these settings. You can find a list of the blocklisted drivers in the /etc/modprobe.d/ directory. Use a comma-separated list to disable multiple drivers. For example: 

modprobe.blacklist=ahci,firewire_ohci
Copy to Clipboard Toggle word wrap
Note

You can use modprobe.blacklist in combination with the different command line options. For example, use it with the inst.dd option to ensure that an updated version of an existing driver is loaded from a driver update disc: 

modprobe.blacklist=virtio_blk
Copy to Clipboard Toggle word wrap
inst.sshd

Use the inst.sshd option to start the sshd service during installation, so that you can connect to the system during the installation using SSH, and monitor the installation progress. For more information about SSH, see the ssh(1) man page on your system. By default, the sshd service is automatically started only on the 64-bit IBM Z architecture. On other architectures, sshd is not started unless you use the inst.sshd option.

Note

During installation, the root account has no password by default. You can set a root password during installation with the sshpw Kickstart command.

inst.kdump_addon=
Use the inst.kdump_addon= option to enable or disable the Kdump configuration screen (add-on) in the installation program. This screen is enabled by default; use inst.kdump_addon=off to disable it. Disabling the add-on disables the Kdump screens in both the graphical and text-based interface as well as the %addon com_redhat_kdump Kickstart command.

23.4. Debug boot options
Copiar o link

You can use the following options when debugging issues to troubleshoot and fix issues.

inst.rescue
Use the inst.rescue option to run the rescue environment for diagnosing and fixing systems. For more information, see the Red Hat Knowledgebase solution repair a filesystem in rescue mode.
inst.updates=

Use the inst.updates= option to specify the location of the updates.img file that you want to apply during installation. The updates.img file can be derived from one of several sources.

Expand
Table 23.4. updates.img file sources
SourceDescriptionExample

Updates from a network

Specify the network location of updates.img. This does not require any modification to the installation tree. To use this method, edit the kernel command line to include inst.updates.

inst.updates=http://website.com/path/to/updates.img.

Updates from a disk image

Save an updates.img on a USB key.

inst.updates=sda1:/images/updates.img for an updates image located in the images directory on the sda1 device or inst.updates=UUID=b4234403-dafb-44c1-b878-4d57b40c9843:/updates.img for an update image located in the root directory of a partition identified by its UUID.

Updates from an installation tree

If you are using a CD, disk, HTTP, HTTPS, or FTP installation, save the updates.img in the installation tree so that all installations can detect the .img file. The file name must be updates.img.

For NFS installs, save the file in the images/ directory, or in the RHupdates/ directory.

inst.syslog=
Sends log messages to the syslog process on the specified host when the installation starts. You can use inst.syslog=<host>[:port] only if the remote syslog process is configured to accept incoming connections.
inst.virtiolog=
Use the inst.virtiolog=<name> option to specify which virtio port (a character device at /dev/virtio-ports/<name>) to use for forwarding logs. The default value is org.fedoraproject.anaconda.log.0.
rd.live.ram
Copies the stage 2 image in images/install.img into RAM. Note that this increases the memory required for installation by the size of the image, which may result in an additional requirement of approximately 1 GiB of RAM or more.
inst.nokill
Prevent the installation program from rebooting when a fatal error occurs, or at the end of the installation process. Use it capture installation logs which would be otherwise lost upon reboot.
inst.noshell
Prevent a shell on terminal session 2 (tty2) including tmux window 2, during installation.
inst.notmux
Prevent the use of tmux during installation. The output is generated without terminal control characters and is meant for non-interactive uses.

23.5. Storage boot options
Copiar o link

You can specify the following options to customize booting from a storage device.

inst.nompath

Disables support for multipath devices. Use this option only if your system has a false-positive that incorrectly identifies a normal block device as a multipath device.

Warning

Use this option with caution. Do not use this option with multipath hardware. Using this option to install to a single path of a multipath device is not supported.

inst.gpt
Prefer creation of GPT disk labels. This option is deprecated and will be removed in future releases. Use inst.disklabel=gpt instead.
inst.disklabel=
Prefer creation of the specified disk label type. Specify gpt to prefer creation of GPT disk labels (default). Specify mbr to prefer creation of MBR disk labels if supported.
inst.wait_for_disks=
Use the inst.wait_for_disks= option to specify the number of seconds installation program to wait for disk devices to appear at the beginning of the installation. Use this option when you use the OEMDRV-labeled device to automatically load the Kickstart file or the kernel drivers but the device takes a longer time to appear during the boot process. By default, the installation program waits for 5 seconds. Use 0 seconds to minimize the delay.
inst.nonibftiscsiboot
The inst.nonibftiscsiboot option enables placement of the boot loader on iSCSI devices that are not configured through the iSCSI boot firmware table (iBFT).
Voltar ao topo
Red Hat logoGithubredditYoutubeTwitter

Aprender

Experimente, compre e venda

Comunidades

Sobre a documentação da Red Hat

Ajudamos os usuários da Red Hat a inovar e atingir seus objetivos com nossos produtos e serviços com conteúdo em que podem confiar. Explore nossas atualizações recentes.

Tornando o open source mais inclusivo

A Red Hat está comprometida em substituir a linguagem problemática em nosso código, documentação e propriedades da web. Para mais detalhes veja o Blog da Red Hat.

Sobre a Red Hat

Fornecemos soluções robustas que facilitam o trabalho das empresas em plataformas e ambientes, desde o data center principal até a borda da rede.

Theme

© 2025 Red Hat