Este contenido no está disponible en el idioma seleccionado.
Appendix C. Boot options reference
You can use the boot options to modify the default behavior of the installation program.
C.1. Installation source boot options
This section describes various installation source boot options.
- 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 theinst.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 using different formats. The following table contains details of theinst.repo=
boot option syntax:Table C.1. Types and format for the inst.repo= boot option and installation source Source type Boot option format Source 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, addnfsvers=X
to options, replacing X with the version number that you want to use.
-
an installable tree, which is a directory structure containing the installation program images, packages, and repository data as well as a valid
Set disk device names with the following formats:
-
Kernel device name, for example
/dev/sda1
orsdb2
-
File system label, for example
LABEL=Flash
orLABEL=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 theinst.addrepo=
boot option multiple times during one boot. The following table contains details of theinst.addrepo=
boot option syntax.NoteThe
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.
For more information about unified ISO, see Unified ISO.
Installation source | Boot option format | Additional information |
---|---|---|
Installable tree at a URL |
| Looks for the installable tree at a given URL. |
Installable tree at an NFS path |
|
Looks for the installable tree at a given NFS path. A colon is required after the host. The installation program passes everything after |
Installable tree in the installation environment |
|
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 |
Disk |
| 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 fromimages/install.img
.When you do not specify the
inst.stage2
option, the installation program attempts to use the location specified with theinst.repo
option.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.NoteBy 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 theinst.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.Example when specifying the source using
inst.stage2=
inst.stage2=https://hostname/path_to_install_image/ inst.noverifyssl
Example when specifying the source using
inst.repo=
inst.repo=https://hostname/path_to_install_repository/ inst.noverifyssl
- inst.stage2.all
Use the
inst.stage2.all
boot option to specify several HTTP, HTTPS, or FTP sources. You can use theinst.stage2=
boot option multiple times with theinst.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/
- 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. - inst.proxy=
This boot option is used when performing an installation from a HTTP, HTTPS, and FTP protocol. For example:
[PROTOCOL://][USERNAME[:PASSWORD]@]HOST[:PORT]
- 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 exampleinput_ks
,output_ks
,all_ks
,logs
andall
. You can combine multiple values separated by a comma. For example,inst.nosave=Input_ks,logs
NoteThe
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’smultilib_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.
C.2. Network boot options
If your scenario requires booting from an image over the network instead of booting from a local image, you can use the following options to customize network booting.
Initialize the network with the dracut
tool. For 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 therd.neednet=1
option, and specify a primary boot interface using thebootdev
option. -
use the
ip
option once, and then use Kickstart to set up further interfaces. This option accepts several different formats. The following tables contain information about the most common options.
-
use the
In the following tables:
-
The
ip
parameter specifies the client IP address andIPv6
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.Table C.3. Boot option formats to configure the network interface Boot option format Configuration method ip=method
Automatic configuration of any interface
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 using the specified method of automatic configuration, such asdhcp
, 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.The
method
parameter can be any of the following:- DHCP
-
dhcp
- IPv6 DHCP
-
dhcp6
- IPv6 automatic configuration
-
auto6
- iSCSI Boot Firmware Table (iBFT)
-
ibft
Note-
If you use a boot option that requires network access, such as
inst.ks=http://host/path
, without specifying theip
option, the default value of theip
option isip=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.NoteThe
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 isnameserver=2001:db8::1
.- bootdev=
-
The
bootdev=
option specifies the boot interface. This option is mandatory if you use more than oneip
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 isifname=interface:MAC
. For example:ifname=eth0:01:23:45:67:89:ab
NoteThe
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. Thedhcpd
service recognizes this value asvendor-class-identifier
. The default value isanaconda-$(uname -srm)
. To ensure theinst.dhcpclass=
option is applied correctly, request network activation during the early stage of installation by also adding theip
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 theSECONDS
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 isvlan=name:interface
. For example:vlan=vlan5:enp0s1
This configures a VLAN device named
vlan5
on theenp0s1
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
For a list of available options, execute the
modinfo
bonding command.- team=
Use the
team=
option to configure a team device with the following syntax:team=name:interfaces
. Replace name with the desired name of the team device and interfaces with a comma-separated list of physical (Ethernet) devices to be used as underlying interfaces in the team device. For example:team=team0:enp0s1,enp0s2
ImportantNIC teaming is deprecated in Red Hat Enterprise Linux 9. Consider using the network bonding driver as an alternative. For details, see Configuring a network bond.
- 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
Additional resources
C.3. Console boot options
This section describes how to configure boot options for your console, monitor display, and keyboard.
- 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, useconsole=ttyS0
. When using theconsole=
argument, the installation starts with a text UI. If you must use theconsole=
option multiple times, the boot message is displayed on all specified console. However, the installation program uses only the last specified console. For example, if you specifyconsole=ttyS0 console=ttyS1
, the installation program usesttyS1
. - 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 commandlocale -a | grep _
or thelocalectl 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
. Thevalue
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.
-
Disable geolocation:
- 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, andinst.noninteractive
you can use theinst.nointeractive
option with a graphical or text installation. When you use theinst.noninteractive
option in text mode, it behaves the same as theinst.cmdline
option. - inst.resolution=
-
Use the
inst.resolution=
option to specify the screen resolution in graphical mode. The format isNxM
, where N is the screen width and M is the screen height (in pixels). The recommended resolution is 1024x768. - inst.vnc
-
Use the
inst.vnc
option to run the graphical installation using Virtual Network Computing (VNC). You must use a VNC client application to interact with the installation program. When VNC sharing is enabled, multiple clients can connect. A system installed using VNC starts in text mode. - inst.vncpassword=
-
Use the
inst.vncpassword=
option to set a password on the VNC server that is used by the installation program. - inst.vncconnect=
-
Use the
inst.vncconnect=
option to connect to a listening VNC client at the given host location, for example,inst.vncconnect=<host>[:<port>]
The default port is 5900. You can use this option by entering the commandvncviewer -listen
. - inst.xdriver=
-
Use the
inst.xdriver=
option to specify the name of the X driver to use both during installation and on the installed system. - inst.usefbx
-
Use the
inst.usefbx
option to prompt the installation program to use the frame buffer X driver instead of a hardware-specific driver. This option is equivalent to theinst.xdriver=fbdev
option. - modprobe.blacklist=
Use the
modprobe.blacklist=
option to blocklist or completely disable one or more drivers. Drivers (mods) 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
NoteYou can use
modprobe.blacklist
in combination with the different command line options. For example, use it with theinst.dd
option to ensure that an updated version of an existing driver is loaded from a driver update disc:modprobe.blacklist=virtio_blk
- inst.xtimeout=
-
Use the
inst.xtimeout=
option to specify the timeout in seconds for starting X server. - inst.sshd
Use the
inst.sshd
option to start thesshd
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 thessh(1)
man page on your system. By default, thesshd
option is automatically started only on the 64-bit IBM Z architecture. On other architectures,sshd
is not started unless you use theinst.sshd
option.NoteDuring 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; useinst.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.
C.4. Debug boot options
This section describes the options you can use when debugging issues.
- inst.rescue
-
Use the
inst.rescue
option to run the rescue environment for diagnosing and fixing systems. For example, you can repair a filesystem in rescue mode. - inst.updates=
Use the
inst.updates=
option to specify the location of theupdates.img
file that you want to apply during installation. Theupdates.img
file can be derived from one of several sources.Table C.4. updates.img file sources Source Description Example 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 includeinst.updates
.inst.updates=http://website.com/path/to/updates.img
.Updates from a disk image
Save an
updates.img
on a floppy drive or a USB key. This can be done only with anext2
filesystem type ofupdates.img
. To save the contents of the image on your floppy drive, insert the floppy disc and run the command.dd if=updates.img of=/dev/fd0 bs=72k count=20
. To use a USB key or flash media, replace/dev/fd0
with the device name of your USB flash drive.Updates from an installation tree
If you are using a CD, disk, HTTP, or FTP install, save the
updates.img
in the installation tree so that all installations can detect the.img
file. The file name must beupdates.img
.For NFS installs, save the file in the
images/
directory, or in theRHupdates/
directory.- inst.syslog=
-
Sends log messages to the
syslog
process on the specified host when the installation starts. You can useinst.syslog=
only if the remotesyslog
process is configured to accept incoming connections. - inst.virtiolog=
-
Use the
inst.virtiolog=
option to specify which virtio port (a character device at/dev/virtio-ports/name
) to use for forwarding logs. The default value isorg.fedoraproject.anaconda.log.0
. - rd.live.ram
-
Copies the
stage 2
image inimages/install.img
into RAM. Note that this increases the memory required for installation by the size of the image which is usually between 400 and 800MB. - 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 lost upon reboot.
- inst.noshell
- Prevent a shell on terminal session 2 (tty2) 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.
- inst.remotelog=
-
Sends all the logs to a remote
host:port
using a TCP connection. The connection is retired if there is no listener and the installation proceeds as normal.
C.5. Storage boot options
This section describes the options you can specify to customize booting from a storage device.
- inst.nodmraid
-
Disables
dmraid
support.
Use this option with caution. If you have a disk that is incorrectly identified as part of a firmware RAID array, it might have some stale RAID metadata on it that must be removed using the appropriate tool such as, dmraid
or wipefs
.
- 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.
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
-
Forces the installation program to install partition information to a GUID Partition Table (GPT) instead of a Master Boot Record (MBR). This option is not valid on UEFI-based systems, unless they are in BIOS compatibility mode. Normally, BIOS-based systems and UEFI-based systems in BIOS compatibility mode attempt to use the MBR schema for storing partitioning information, unless the disk is 2^32 sectors in size or larger. Disk sectors are typically 512 bytes in size, meaning that this is usually equivalent to 2 TiB. The
inst.gpt
boot option allows a GPT to be written to smaller disks. - 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 theOEMDRV-labeled
device to automatically load the Kickstart file or the kernel drivers but the device takes longer time to appear during the boot process. By default, installation program waits for5
seconds. Use0
seconds to minimize the delay.
C.6. Deprecated boot options
This section contains information about deprecated boot options. These options are still accepted by the installation program but they are deprecated and are scheduled to be removed in a future release of Red Hat Enterprise Linux.
- method
-
The
method
option is an alias forinst.repo
. - dns
-
Use
nameserver
instead ofdns
. Note that nameserver does not accept comma-separated lists; use multiple nameserver options instead. - ksdevice
Table C.5. Values for the ksdevice boot option Value Information Not present
N/A
ksdevice=link
Ignored as this option is the same as the default behavior
ksdevice=bootif
Ignored as this option is the default if
BOOTIF=
is presentksdevice=ibft
Replaced with
ip=ibft
. Seeip
for detailsksdevice=<MAC>
Replaced with
BOOTIF=${MAC/:/-}
ksdevice=<DEV>
Replaced with
bootdev
C.7. Removed boot options
This section contains the boot options that have been removed from Red Hat Enterprise Linux.
dracut
provides advanced boot options. For more information about dracut
, see the dracut.cmdline(7)
man page on your system.
- askmethod, asknetwork
-
initramfs
is completely non-interactive, so theaskmethod
andasknetwork
options have been removed. Useinst.repo
or specify the appropriate network options. - blacklist, nofirewire
-
The
modprobe
option now handles blocklisting kernel modules. Usemodprobe.blacklist=<mod1>,<mod2>
. You can blocklist the firewire module by usingmodprobe.blacklist=firewire_ohci
. - inst.headless=
-
The
headless=
option specified that the system that is being installed to does not have any display hardware, and that the installation program is not required to look for any display hardware. - inst.decorated
-
The
inst.decorated
option was used to specify the graphical installation in a decorated window. By default, the window is not decorated, so it does not have a title bar, resize controls, and so on. This option was no longer required. - repo=nfsiso
-
Use the
inst.repo=nfs:
option. - serial
-
Use the
console=ttyS0
option. - updates
-
Use the
inst.updates
option. - essid, wepkey, wpakey
- Dracut does not support wireless networking.
- ethtool
- This option was no longer required.
- gdb
-
This option was removed because many options are available for debugging dracut-based
initramfs
. - inst.mediacheck
-
Use the
dracut option rd.live.check
option. - ks=floppy
-
Use the
inst.ks=hd:<device>
option. - display
-
For a remote display of the UI, use the
inst.vnc
option. - utf8
- This option was no longer required because the default TERM setting behaves as expected.
- noipv6
-
ipv6 is built into the kernel and cannot be removed by the installation program. You can disable ipv6 by using
ipv6.disable=1
. This setting is used by the installed system. - upgradeany
- This option was no longer required because the installation program no longer handles upgrades.
- netmask, gateway, hostname
-
The
netmask
,gateway
, andhostname
options are provided as part of theip
option. - ip=bootif
-
A PXE-supplied
BOOTIF
option is used automatically, so there is no requirement to useip=bootif
. - inst.zram
-
The
zram.service
cannot be run anymore. Seezram-generator
for more information. - inst.singlelang
- The single language mode is not supported anymore.
- inst.repo=hd:<device>:<path> for installable tree
- This option cannot be used with installable tree but only with an ISO file.
- inst.loglevel
- The log level is always set to debug.