WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
  • VKS
  • Homelab
    • Resources
    • Nested Virtualization
  • VMware Nostalgia
  • Apple
You are here: Home / ESXi 5.5 introduces a new Native Device Driver Architecture Part 1

ESXi 5.5 introduces a new Native Device Driver Architecture Part 1

10.28.2013 by William Lam // 12 Comments

With a new release of vSphere, many of us are excited about all the new features that we can see and touch. However, what you may or may not notice are some of the new features and enhancements that VMware Engineering has made to the underlying vSphere platform to continue making it better, faster and stronger. One such improvement is the introduction of a new Native Device Driver architecture in ESXi 5.5. Though this feature is primarily targeted at our hardware ecosystem partners, I know some of you have asked about this and I thought it might be useful to share some of the details.

Note: If you are a hardware ecosystem partner and would like to learn more, please reach out to your VMware TAP account managers.

If we take a look back at the early days of ESX, VMware made a decision to use Linux derived drivers to provide the widest variety of support for storage, network and other hardware devices for ESX. Since ESX and specifically the VMkernel is NOT Linux, to accomplish this we built a translation (shim) layer module called vmklinux which sits in between the VMkernel and drivers. This vmklinux module is what enables ESX to function with the linux derived drivers and provides an API which can speak directly to the VMkernel.

Here is a quick diagram of what that looks like:

So why the change in architecture? Since the stability, reliability and performance of these device drivers are importantly critical to ESX(i) second to the VMkernel itself. There is actually a variety of challenges with this architecture in addition to the overhead that is introduced with the translation layer. The vmklinux module must be tied to a specific Linux kernel version and the continued maintenance of vmklinux to provide backwards compatibility across both new and old drivers is quite challenging. From a functionality perspective, we are also limited by the capabilities of the Linux drivers as they are not built specifically for the VMkernel and can not support features such as hot-plug/ To solve this problem, VMware developed a new Native Device Driver model interface that allows a driver to speak directly to the VMkernel and removing the need for the “legacy” vmklinux interface.

Here is a quick diagram of what that looks like:
What are some of the benefits of this new device driver model?
  • More efficient and flexible device driver model compared to vmklinux
  • Standardized information for debugging/troubleshooting
  • Improved performance as we no longer have a translation layer
  • Support for new capabilities such as PCIe hot-plug

This new architecture was developed with backwards compatibility in mind as we all know it is not possible for our entire hardware ecosystem to port their current drivers in one release. To that extent, ESXi 5.5 can run a hybrid of both “legacy” vmklinux drivers as well as the new Native Device Driver. Going forward, VMware will be primarily investing in the Native Device Driver architecture and encourage new device drivers to be developed using the new architecture. VMware also provides an NDDK (Native Driver Development Kit) to our ecosystem partners as well as a sample Native Device Driver which some of you may have seen in the release of vSphere 5.1 with a native vmxnet3 VMkenel module for nested ESXi.

Hopefully this has given you a good overview of the new Native Device Driver architecture and in part 2 of the article I will go into a bit more details on where to find these drivers, which vendor supports this new architecture today and how they are loaded.

More from my site

  • ESXi 5.5 introduces a new Native Device Driver Architecture Part 2
  • A killer custom Apple Mac Mini setup running VSAN
  • Does VSAN work with Free ESXi?
  • ESXi 5.5 Kickstart script for setting up VSAN
  • Does reinstalling ESXi with an existing VSAN Datastore wipe your data?

Categories // Uncategorized Tags // ESXi 5.5, native device driver, nddk, vmklinux, vSphere 5.5

Comments

  1. *protectedOlivier Hault says

    11/27/2013 at 4:39 pm

    Is VMware Virtual SAN a Native Device Driver too once installed into your ESXi host ?

    Reply
  2. *protectedWilliam Lam says

    11/27/2013 at 5:50 pm

    VSAN is not installed on an ESXi host, it IS already part of an ESXi 5.5 host as it's built right into the VMkernel itself.

    Reply
  3. *protectedAkhil Bhansali says

    07/16/2014 at 6:54 am

    Hello William, thank you for sharing the details. Look forward to Part2 of this article!

    Reply

Trackbacks

  1. TinkerTry IT @ home | What does long list of consumer devices deprecated and unsupported in ESXi 5.5 mean? says:
    06/09/2014 at 1:26 am

    […] 11 2013 Update: Excellent article2 now available, a two partner: ESXi 5.5 introduces a new Native Device Driver Architecture Part 1 by William Lam, Oct 28 2013. ESXi 5.5 introduces a new Native Device Driver Architecture Part […]

    Reply
  2. VMware ESXi - async drivers | vTricks.com says:
    06/28/2014 at 12:02 pm

    […] the way ESXi 5.5 introduced a new driver architecture called Native Device Driver. Currently a ESXi can run in hybrid mode to support the new and the “legacy” driver which is […]

    Reply
  3. VMware Link Collection | Life says:
    10/31/2014 at 4:07 am

    […] Version 10-dilemma (running-system.com) VMware vSphere 5.5 Physical Host Maximums (TechHead) ESXi 5.5 introduces a new Native Device Driver Architecture Part 1 (Virtually Ghetto) ESXi 5.5 introduces a new Native Device Driver Architecture Part 2 (Virtually […]

    Reply
  4. כמה עדכונים על וירטואליזציות שונות | בלוג יעוץ בנושאי וירטואליזציה says:
    12/07/2014 at 2:56 am

    […] מי שמעוניין לקרוא קצת יותר מה שכתבו על כך, אפשר לקרוא כאן. אני אתייחס לאספקט טיפה […]

    Reply
  5. Architecture Device Driver | Become Architecture Fan says:
    05/15/2016 at 1:59 am

    […] ESXi 5.5 native device driver architecture – virtuallyGhetto – So why the change in architecture? Since the stability, reliability and performance of these device drivers are importantly critical to ESX(i) second to the VMkernel … […]

    Reply
  6. ESXi 6.5 support for Apple Mac Pro 6,1 | virtuallyGhetto says:
    01/09/2017 at 8:44 am

    […] to the AHCI driver which gave me an idea. The specific driver shown in the logs is the new AHCI Native Driver which is new in ESXi 6.5. Perhaps, the new driver is not able to claim the disk drives and is […]

    Reply
  7. vmkドライバーとネイティブドライバーの違い | VMwareな日々 says:
    02/13/2019 at 9:51 pm

    […] http://www.virtuallyghetto.com […]

    Reply
  8. What is the Impact of the VMKlinux Driver Stack Depreciation? – VMPRO.AT – all about virtualization says:
    04/11/2019 at 2:45 am

    […] ESXi 5.5 introduces a new Native Device Driver Architecture Part 1 […]

    Reply
  9. What is the Impact of the VMKlinux Driver Stack Deprecation? – VMPRO.AT – all about virtualization says:
    04/11/2019 at 7:43 am

    […] ESXi 5.5 introduces a new Native Device Driver Architecture Part 1 […]

    Reply

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