Go to main content

Booting and Shutting Down Oracle® Solaris 11.3 Systems

Exit Print View

Updated: October 2017

x86: Where the GRUB 2 PXE Boot Image Is Installed

Similar to GRUB Legacy, the GRUB 2 PXE boot image is installed in the root directory of the TFTP server. The name of the boot image depends on how AI was configured. The appropriate DHCP BootFile option contains the name of the PXE boot image. Both BIOS and UEFI firmware types are supported automatically, if the AI image is GRUB 2 based. No special arguments are required.

On an installed Oracle Solaris instance, the PXE boot images for both a BIOS-targeted and UEFI-targeted images are stored in boot/grub, in the root directory of the AI image, for example, /export/auto_install/my_ai_service/boot/grub.

This directory contains the following contents:

bash-4.1$ cd grub/
bash-4.1$ ls
grub_cfg_net i386-pc splash.jpg x86_64-efi
grub2netx64.efi pxegrub2 unicode.pf2 

There are firmware-specific subdirectories for GRUB 2 modules that are in the i386-pc directory for systems with BIOS firmware, and the x64_64-efi directory for 64-bit UEFI systems. However, files in these directories are not used during a network boot (modules are built into the GRUB 2 images and are not transferred over TFTP).

Note -  If you are using a DHCP server that is not managed by the installadm command, you will need to configure the DHCP server in accordance with how the installadm command normally configures an accessible DHCP server, which is to set up the BootFile based on the client architecture identifier. As an aid to the administrator, the installadm command prints out the client arch boot file paths that should be set for manually configured DHCP servers.