WilliamLam.com

Quick Tip - ESXi 7.0 Update 3f now includes all Intel I219 devices from Community Networking Driver Fling

by // Leave a Comment

Thanks to Reuben F who left a comment on the Community Networking Driver for ESXi Fling asking about something interesting he saw in the latest ESXi 7.0 Update 3f release notes regarding Intel ne1000 driver.

ESXi 7.0 Update 3f upgrades the Intel-ne1000 driver to support Intel I219-LM devices that are required for newer server models, such as the Intel Rocket Lake-S platform. The TCP segmentation offload for the I219 devices is deactivated because of known issues in the hardware DMA.

He asked whether the Community Networking Driver for ESXi Fling was still needed to support the various Intel I219 devices on the Fling requirements page?

First off, thank you Reuben for making me aware of this, which I totally missed while reading the release notes. Secondly, I reached out to Songtao, one of the Engineers on Fling and he was also surprised by the news. He checked the source and then confirmed that all listed Intel I219 devices in the Fling has actually been incorporated into the latest ESXi 7.0 Update 3f release and the Fling would no longer be required for these specific devices and we have Shu, another Engineer on the Fling to thank for this awesome update! Thank you Shu!

Songtao, Shu and myself had released the Community Networking Driver for ESXi Fling back in early 2021 to help support some of the networking devices that we had observed in the community and there have been a number of releases that has added additional devices. It is always a great feeling to see your work not only being well adopted but also now productized. This is one of the many benefits of the VMware Fling's program and being able to share a solution that solves an immediate problem and iterating on feedback from our users, we have the opportunity to enhance and improve our products/services. Thank you to all the VMware customers who have and continue to support us! 🙏

Who knows ... maybe the network devices under the igc-community module in the Fling will be productized next? 😀

Emulating a Virtual USB storage device using Nested ESXi

by // 3 Comments

My buddy Alan Renouf had pinged me earlier today and asked whether it was possible to emulate a USB storage device that could aide him in the testing the installation of ESXi from a USB device but without having to use a real USB device. I honestly was not aware of any mechanisms that would allow for this and I normally would just passthrough a real USB device to a Nested ESXi VM for this type of testing purposes.

While thinking about his question, I also recall we had made some enhancements to our Virtual USB interface that would allow user to back it using a disk file. While searching further, I came to learn that not only was this possible, but it was also a common method for testing USB-based installation without the hassle of messing with physical hardware. It turns out you can just present a Virtual Disk (VMDK) to a VM running ESXi (Nested ESXi) and through a special driver, it will recognize the device as a USB storage device!

I definitely wish I had learned about this earlier and it goes to show, all the hard engineering efforts made by our VMware Engineers to make testing and using our software as easy as possible even without needing real physical hardware 😀

[Read more...]

Quick Tip - Using ESXi Scripted Installation (kickstart) to configure IPv6 networking

by // 5 Comments

I have written numerous articles on the topic of ESXi Scripted Installation aka Kickstart, which is just one of the many options that enables customers to fully automate the installation and configuration of their ESXi hosts. An interesting question that recently came up internally was whether you could configure ESXi networking using IPv6, rather than IPv4 using the default ESXi Kickstart network parameters?

If you look at the ESXi network params as they are labeled such as netmask, it would seem that these are only applicable to IPv4. Although my personal experience has been exclusively IPv4, I figure I would take a quick look at the python code which powers the ESXi Kickstart infrastructure which is located under /usr/lib/vmware/weasel directory. Although I am not a Developer, from what I could grok, it seems like IPv6 might actually be possible using these exact same parameters.

Using Nested ESXi and the new vSphere 7.0 Update 2 feature HTTP Boot over virtual EFI, I was able to setup a quick prototype to validate that you can indeed configure IPv6 using the same ESXi networking parameters, which are applicable to both IPv4 and IPv6.

[Read more...]