WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
  • VKS
  • Homelab
    • Resources
    • Nested Virtualization
  • VMware Nostalgia
  • Apple
You are here: Home / ESXi / Quick Tip - ESXi 7.0 Update 3f now includes all Intel I219 devices from Community Networking Driver Fling

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

07.18.2022 by William Lam // 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? 😀

More from my site

  • Updated findings for passthrough of Intel NUC Integrated Graphics (iGPU) with ESXi
  • Updates to USB Network & NVMe Community Driver for ESXi 7.0 Update 3
  • vCenter Server 6.0 Tidbits Part 4: Finding all deployed vCenter Servers
  • Automating Dead Space Reclamation in ESXi 5.0u1
  • VMware nested easter egg

Categories // ESXi, Home Lab, vSphere 7.0 Tags // ESXi 7.0 Update 3

Thanks for the comment!Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Thank Author

Author

William is Distinguished Platform Engineering Architect in the VMware Cloud Foundation (VCF) Division at Broadcom. His primary focus is helping customers and partners build, run and operate a modern Private Cloud using the VMware Cloud Foundation (VCF) platform.

Connect

  • Bluesky
  • Email
  • GitHub
  • LinkedIn
  • Mastodon
  • Reddit
  • RSS
  • Twitter
  • Vimeo

Recent

  • Programmatically accessing the Broadcom Compatibility Guide (BCG) 05/06/2025
  • Quick Tip - Validating Broadcom Download Token  05/01/2025
  • Supported chipsets for the USB Network Native Driver for ESXi Fling 04/23/2025
  • vCenter Identity Federation with Authelia 04/16/2025
  • vCenter Server Identity Federation with Kanidm 04/10/2025

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2025