Taking Server Virtualization Down from the Clouds to Real Life Experience: Overcoming Challenges with ESXi 6.0U1a and Skylake Motherboards

As more organizations embrace server virtualization, the demand for reliable and efficient virtualized infrastructure continues to grow. VMware’s ESXi hypervisor is a popular choice for many IT professionals, offering a robust and feature-rich platform for hosting virtual machines. However, as with any technology, there are challenges that arise when deploying ESXi in real-world environments, especially when using the latest Skylake motherboards. In this article, we will delve into some of the issues that readers have encountered while setting up ESXi 6.0U1a on their Skylake systems and provide solutions to overcome these challenges.

Community-Developed NIC Drivers and Their Impact on ESXi Deployments

One common issue that many readers have faced is the use of community-developed NIC drivers, specifically the “Chilly” driver referenced in this VMware community post. While these drivers can provide much-needed support for older hardware, they can also cause compatibility issues with newer ESXi versions like 6.0U1a. Chris, one of our readers, experienced this problem firsthand when trying to deploy ESXi 6.0U1a on his Dell desktop with a customized community-developed NIC driver.

To resolve this issue, Chris was advised to remove the community driver and use the official VMware driver instead. This fix worked successfully, as Chris confirmed in his follow-up comment. However, this raises an important question: why do community-developed drivers sometimes conflict with official ESXi releases? The answer lies in the differences between these two types of drivers.

Official VMware drivers are thoroughly tested and certified by VMware to ensure compatibility and optimal performance. In contrast, community-developed drivers may not undergo the same rigorous testing and certification process, leading to potential conflicts with other ESXi components. While these drivers can provide support for older hardware, they may also introduce new challenges when upgrading to newer ESXi versions.

Skylake Motherboards and ESXi 6.0U1a: A Rocky Road to Success

Another challenge that our readers have faced is the compatibility of Skylake motherboards with ESXi 6.0U1a. Matt, one of our readers, had to try three different methods to get a working ESXi 6.0U1a host on his ASUS Z170M-Plus motherboard with a Skylake i7 6700 3.4Ghz CPU. These methods included installing ESXi onto a USB flash drive, creating a custom ISO using ESXi-Customizer-PS-v2.4.ps1, and upgrading from ESXi 5.5U3a to 6.0U1a via the command line.

While these methods may seem daunting at first, they highlight some important considerations for IT professionals when deploying ESXi on Skylake systems. Firstly, it is essential to ensure that the motherboard and CPU are supported by ESXi 6.0U1a. This can be verified using VMware’s hardware compatibility list (HCL). Secondly, using a custom ISO can help to address potential issues with the onboard NIC, as Matt discovered. Finally, upgrading from ESXi 5.5U3a to 6.0U1a via the command line can be a viable option for those who prefer a more hands-on approach.

Fredfox_uk, another reader, also faced similar challenges with his ASRock H170M-ITX/AC motherboard and onboard i219 NIC. However, by using the process outlined in this article, he was able to successfully upgrade from ESXi 5.5U3a to 6.0U1a and retain the i219 NIC driver. This highlights the importance of carefully planning and testing any ESXi deployment, especially when dealing with newer hardware and software combinations.

Conclusion

In conclusion, deploying ESXi 6.0U1a on Skylake systems can be a challenging but rewarding experience. By understanding the potential pitfalls of community-developed NIC drivers and carefully planning our deployments, we can overcome these challenges and create robust virtualized infrastructures that meet the needs of our organizations. We hope that this article has provided valuable insights and solutions for our readers who are facing similar issues in their ESXi deployments. As always, please feel free to share your own experiences and questions in the comments section below. All comments are moderated to ensure a productive and respectful discussion.