WilliamLam.com

Homelab considerations for vSphere 8

by // 111 Comments

There has been a lot of great technical content from both VMware and the broader community since the announcement of vSphere 8, which happened a few weeks ago. I know many of you are excited to get your hands on both vSphere 8 and vSAN 8 and while we wait for GA, I wanted to share some of my own personal experiences but also some of the considerations for those interested in running vSphere 8 in their homelab.

As with any vSphere release, you should always carefully review the release notes when they are made available and verify that all of your hardware and the underlying components are officially listed on the VMware HCL, which will be updated when vSphere 8 and vSAN 8 GA's. This is the only way to ensure that you will have the best possible experience and a supported configuration from VMware.

Disclaimer: The following considerations are based on early observations using pre-GA builds of vSphere 8 and it does not reflect any official guidance or support from VMware.

[Read more...]

vSphere 8 productizes Community Networking Driver Fling for ESXi

by // 6 Comments

Back in July with the release of vSphere 7.0 Update 3f, I had shared that all Intel i219 devices from the Community Networking Driver Fling for ESXi is now part of default ESXi 7.0 Update 3f installation. This simplified the ESXi installation process as customers no longer needed to create a custom ESXi ISO that contains the Fling driver.

While the e1000-community module within the Community Networking Driver Fling for ESXi has been productized, the Fling also includes another driver module called igc-community which adds support for Intel i220, i225 & i226 PCIe-based network devices. For recent Intel NUC platforms like the Intel NUC 11 (Panther Canyon & Tiger Canyon), Intel NUC 11 Extreme (Beast Canyon), Intel NUC 12 Extreme (Dragon Canyon) and Intel NUC 12 Pro (Wall Street Canyon) the Fling is still required for ESXi to recognize the onboard network interfaces.

As of vSphere 8, which was recently announced at VMware Explore US, I am happy 😆 (or jacked, jazzed, or pumped) to share that the Community Networking Driver Fling for ESXi will be fully productized! Customers who install ESXi 8.0 will no longer need to create a custom ESXi Image and the network devices listed on the Fling page will automatically be detected by ESXi.

Changes to vSphere Client Login UI customizations in vSphere 6.7

by // 11 Comments

For those that have customized their vSphere Client Login UI using the instructions here and here, it looks like the process can not be applied to the vSphere 6.7 release. From what I can tell, it looks like we have now consolidated the various WAR files into a single file /usr/lib/vmware-sso/vmware-sts/webapps/ROOT.war. The original contents of the websso directory, which pertains to the UI customization, is now located here. This was a fairly minor change, but something to be aware of and for details on how to persist your configuration changes, please see the instructions below.

UPDATE (11/19/22) - As of vSphere 8, the webapp WAR file is now located in /var/lib/sso/webapps/ROOT.war

Disclaimer: This is not officially supported by VMware. If you decide to enable this, please use at your own risk and ensure you backup all original files in case you need revert back to the original configuration.

As part of looking into this, I also had some fun incorporating a cool little animated login page directly into the vSphere UI which I had shared on Twitter yesterday. Stay tuned for more details on #vYetti 🙂

[Read more...]