Starting version 8.9.03, BMC Server Automation is renamed to TrueSight Server Automation. This space contains information about BMC Server Automation 8.9.02 and previous versions. For TrueSight Server Automation 8.9.03 and later releases, see TrueSight Server Automation 8.9.

ESXi 4.0 image type

The Add/Edit Image dialog box lets you define or edit the configuration settings of the ESXi 4.0 image file type.

Image file

The path to the folder containing the vmkboot.gz image file.
For example, the image folder should reside at: /tftproot/X86PC/pxelinux. If the image folder is named ESX4i, then you would set the Image file field to: ESX4i/vmkboot.gz


(Optional) Description of the image file

Kernel name

The kernel to be loaded when the device boots from the PXE server. Specify a path to the folder that contains the mboot.c32 file.
For example: ESX4i/mboot.c32

Kernel commandline

Command line arguments that the kernel requires at boot time. Separate arguments with a dash (---). Each argument should include the path to the folder containing the file (vmk.gz, sys.vgz, cim.vgz, oem.tgz, and license.tgz).
For example:

--- ESX4i/vmk.gz --- ESX4i/sys.vgz --- ESX4i/cim.vgz --- ESX4i/oem.tgz --- ESX4i/license.tgz ipappend 2

64-bit image

Because ESXi 4.0 can be used to provision only 64 bit devices, this option is checked and disabled.
If you want to use an x86 image, you must create a custom image.

Set as default image

The default image is the image that the system uses for auto-discovery. For example, when an unknown device PXE boots on your network, the system sends this device the default image.
Because auto-discovery is not supported for the ESXi 4.0 image, you cannot set this image as the default.


You can also provision ESX and ESXi systems using Gentoo and Skip Linux boot images similar to Red Hat.

Was this page helpful? Yes No Submitting... Thank you