13장. Starting Kickstart installations


You can start Kickstart installations in multiple ways:

  • Automatically by editing the boot options in network boot configuration.
  • Automatically by providing the file on a volume with a specific name.
  • Manually by providing inst.ks= kernel command line option in bootloader menu.

You can register RHEL using the Red Hat Content Delivery Network (CDN). CDN is a geographically distributed series of web servers. These servers provide, for example, packages and updates to RHEL hosts with a valid subscription.

During the installation, registering and installing RHEL from the CDN offers following benefits:

  • Utilizing the latest packages for an up-to-date system immediately after installation and
  • Integrated support for connecting to Red Hat Lightspeed and enabling System Purpose.

13.1. Starting a Kickstart installation automatically by using PXE or UEFI HTTP boot

AMD64, Intel 64, and 64-bit ARM systems and IBM Power Systems servers have the ability to boot by using a PXE server. When you configure the PXE server or UEFI HTTP boot, add the boot option into the boot loader configuration file. It in turn starts the installation automatically. By using this approach, it is possible to automate the installation completely, including the boot process.

This procedure is intended as a general reference; detailed steps differ based on your system’s architecture, and not all options are available on all architectures (for example, you cannot use PXE boot on 64-bit IBM Z).

Prerequisites

  • You have a Kickstart file ready in a location accessible from the system to be installed.
  • You have a PXE server that can be used to boot the system and begin the installation and/or an HTTP server configured for UEFI HTTP boot.

Procedure

  1. Open the boot loader configuration file on your PXE server, and add the inst.ks= boot option to the appropriate line. The name of the file and its syntax depends on your system’s architecture and hardware:

    1. On AMD64 and Intel 64 systems with BIOS, the file name can be either default or based on your system’s IP address. In this case, add the inst.ks= option to the append line in the installation entry. A sample append line in the configuration file looks similar to the following:

      append initrd=initrd.img inst.ks=http://192.168.124.2/kickstarts/ks.cfg
    2. On systems using the GRUB2 boot loader (AMD64, Intel 64, and 64-bit ARM systems with UEFI firmware and IBM Power Systems servers), the file name will be grub.cfg. In this file, append the inst.ks= option to the kernel line in the installation entry. A sample kernel line in the configuration file will look similar to the following:

      linuxefi /redhat/images/pxeboot/vmlinuz inst.ks=http://192.168.124.2/kickstarts/ks.cfg
  2. If you want to configure an automated Kickstart installation by using UEFI HTTP boot, locate the bootloader configuration file (grub.cfg) served by the HTTP server and edit it in a similar way as in step 1.b:

    linuxefi /redhat/images/pxeboot/vmlinuz inst.ks=http://192.168.124.2/kickstarts/ks.cfg
  3. Boot the installation from the network server.

    The installation begins now by using the installation options specified in the Kickstart file. If the Kickstart file is valid and contains all required commands, the installation is completely automated.

    참고

    If you have installed a Red Hat Enterprise Linux Beta release, on systems having UEFI Secure Boot enabled, then add the Beta public key to the system’s Machine Owner Key (MOK) list.

Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2026 Red Hat
맨 위로 이동