5.2. Chainbooting virtual machines


Some virtualization hypervisors use iPXE as primary firmware for PXE booting. Because of this, you can chainboot without TFTP and PXELinux.

Chainbooting virtual machine workflow

Using virtualization hypervisors removes the need for TFTP and PXELinux. It has the following workflow:

  1. Virtual machine starts
  2. iPXE retrieves the network credentials using DHCP
  3. iPXE retrieves the HTTP address using DHCP
  4. iPXE chainloads the iPXE template from the template Capsule
  5. iPXE loads the kernel and initial RAM disk of the installer

If you want to use the discovery service with iPXE, see 「Setting up the Discovery Service for iPXE」.

Ensure that the hypervisor that you want to use supports iPXE. The following virtualization hypervisors support iPXE:

  • libvirt
  • Red Hat Virtualization
  • RHEV

Configuring Satellite Server to use iPXE

You can use the default template to configure iPXE booting for hosts. If you want to change the default values in the template, clone the template and edit the clone.

Procedure

  1. Copy a boot file to the TFTP directory on your Satellite Server:

    • For EFI systems, copy the ipxe.efi file:

      # cp /usr/share/ipxe/ipxe.efi /var/lib/tftpboot/
      Copy to Clipboard Toggle word wrap
    • For BIOS systems, copy the undionly.kpxe file:

      # cp /usr/share/ipxe/undionly.kpxe /var/lib/tftpboot/undionly.0
      Copy to Clipboard Toggle word wrap
  2. In the Satellite web UI, navigate to Hosts > Provisioning Templates, enter Kickstart default iPXE and click Search.
  3. Optional: If you want to change the template, click Clone, enter a unique name, and click Submit.
  4. Click the name of the template you want to use.
  5. If you clone the template, you can make changes you require on the Template tab.
  6. Click the Association tab, and select the operating systems that your host uses.
  7. Click the Locations tab, and add the location where the host resides.
  8. Click the Organizations tab, and add the organization that the host belongs to.
  9. Click Submit to save the changes.
  10. Navigate to Hosts > Operating systems and select the operating system of your host.
  11. Click the Templates tab.
  12. From the iPXE Template list, select the template you want to use.
  13. Click Submit to save the changes.
  14. Navigate to Hosts > All Hosts.
  15. In the Hosts page, select the host that you want to use.
  16. Select the Templates tab.
  17. From the iPXE template list, select Review to verify that the Kickstart default iPXE template is the correct template.
  18. To use the iPXE bootstrapping feature for Satellite, configure the dhcpd.conf file as follows:

    if exists user-class and option user-class = "iPXE" {
      filename "http://satellite.example.com/unattended/iPXE?bootstrap=1";
    } elsif option architecture = 00:06 {
      filename "ipxe.efi";
    } elsif option architecture = 00:07 {
      filename "ipxe.efi";
    } elsif option architecture = 00:09 {
      filename "ipxe.efi";
    } else {
      filename "undionly.0";
    }
    Copy to Clipboard Toggle word wrap

    If you use an isolated network, use a Capsule Server URL with TCP port 8000, instead of the URL of Satellite Server.

    注記

    Use http://satellite.example.com/unattended/iPXE?bootstrap=1 when Capsule HTTP endpoint is disabled (installer option --foreman-proxy-http false). Template Capsule plug-in has the default value 8000 when enabled and can be changed with --foreman-proxy-http-port installer option. In that case, use http://capsule.example.com:8000. You must update the /etc/dhcp/dhcpd.conf file after every upgrade.

トップに戻る
Red Hat logoGithubredditYoutubeTwitter

詳細情報

試用、購入および販売

コミュニティー

Red Hat ドキュメントについて

Red Hat をお使いのお客様が、信頼できるコンテンツが含まれている製品やサービスを活用することで、イノベーションを行い、目標を達成できるようにします。 最新の更新を見る.

多様性を受け入れるオープンソースの強化

Red Hat では、コード、ドキュメント、Web プロパティーにおける配慮に欠ける用語の置き換えに取り組んでいます。このような変更は、段階的に実施される予定です。詳細情報: Red Hat ブログ.

会社概要

Red Hat は、企業がコアとなるデータセンターからネットワークエッジに至るまで、各種プラットフォームや環境全体で作業を簡素化できるように、強化されたソリューションを提供しています。

Theme

© 2025 Red Hat