In this post we’ll take a look at how we can run the light-weight and efficient Alpine Linux OS on a ESXi host running on a Raspberry Pi
Finally the highly anticipated ESXi on ARM is available! In this post I’ll run through the steps needed to get ESXi installed on a Raspberry Pi 4 8GB
This post shows how you can create your very own custom iso image with host specific customizations for a completely unattended ESXi installation
This blog post will be building on a previous post where I built a small PXE server environment for ESXi installation. In this post we will enhance the PXE install with customized kickstart files specific for the hardware we want to install. There’s two new components to discuss here. The kickstart file (ks.cfg) it self and how to point to it during PXE boot. Let’s take a look at the current environment The tftp server root is located at /var/lib/tftpboot and my images is stored as directories under this directory.
In our environment we run ESXi primarily on HPE Proliant servers. We use OneView for managing the hardware it self (i.e. monitoring, firmware), but for provisioning ESXi to the servers we have been doing some of it manually and some of it with HPE Insight Control Server Provisioning (ICsp). When preparing for deployment of a new batch of servers we found that Proliant Gen10 servers is not supported by ICsp. Furthermore after an unofficial chat with a HPE employee it seems that it won’t be anytime soon either.