STEP 14 – Test PXE Boot and Kickstart installation.
Just create a new VM instance, and don’t provide it with any installation media.
Of course it will need a vdisk for the installation to work, use ~6 or 8gb set as NVMe.
For headless servers, there usually isn’t any need for Bluetooth, Sound, 3D Video, or a Printer Port. I remove all of those from VM hardware profile.
The PXE/Kickstart install image the clients will boot utilizes a ramdisk. In current/recent versions of CentOS, Fedora, RedHat, and Oracle linux clients need 1,536 MB of vRAM to load this installation image. As soon as the installation is completed, and the VM is capable from using it’s own disk, then the VM hardware memory allocation can be reduced… for many of my server VMs, I set it at 512MB.
1 vCPU is adequate.
Of course it will need a virtual network interface configured on the same VMNET as Fusion is providing DHCP with the PXE (“next-server”) option.
That’s it… start the VM.
If it works, there will be a lot of scrolling text… then eventually a prompt to quit/reboot… and you’ll have a working VM.
If something goes wrong, watch the screens, it’ll provide pretty good clues. There are also methods to access (tail) the installation logs… but I’ll leave you to read up on that. Most of the problems with relatively simple PXE/Kickstart setups like this are due to typos in the *.ks script or the “default” pxe boot menu.