vSphere Hypervisor (ESXi) — VMware’s bare-metal layer
What it is
ESXi, officially called vSphere Hypervisor, is VMware’s bare-metal hypervisor. You install it straight on the server, no Linux or Windows host underneath. For many datacenters it’s the base layer: stable, predictable, and designed to integrate with the rest of VMware’s stack (vCenter, vMotion, HA, DRS). Free to download, but the good stuff (central management, clustering, API writes) comes only with licenses.
How it really works
– Runs directly on hardware with its own slimmed-down kernel.
– First boot gives you the DCUI — a yellow/black text console. From there you set IP, root password, and not much else.
– Day-to-day management happens remotely via vSphere Client or through vCenter if you have it.
– Guest VMs live on VMFS datastores (clustered FS tuned for SAN/NAS). Local disks, iSCSI, NFS, or Fibre Channel all work.
– Networking uses virtual switches, VLANs, and if licensed, NSX for SDN features.
Technical map
| Area | Notes |
| Type | Type-1 (bare metal) |
| Management | DCUI (basic), vSphere Client, vCenter |
| Guests | Windows, Linux, BSD, Solaris |
| Storage | VMFS, NFS, iSCSI, Fibre Channel |
| Networking | vSwitch, VLAN, SR-IOV, NSX (licensed) |
| Features | Snapshots, vMotion, HA/DRS (with vCenter) |
| License | Free edition (limited) or paid VMware licenses |
| Deployment | Installs directly on server hardware (USB, SD, disk) |
Deployment notes (real world)
– Hardware must match VMware’s HCL. Unsupported NICs and storage controllers are a common headache.
– Many admins boot ESXi from USB or SD card and keep datastores on SAN/NAS.
– Free license is fine for labs but lacks API write access and vCenter integration.
– Patching is done through Lifecycle Manager or CLI; requires subscription.
– Drivers are bundled, but on “whitebox” servers you may need custom images.
Where it’s used
– Enterprise clusters: with vCenter, HA, and DRS turned on.
– Home labs: free edition is still popular for testing, despite restrictions.
– Service providers: as a base for multi-tenant VMware clouds.
– Critical apps: when vendor support contracts are non-negotiable.
Weak spots
– Free ESXi feels crippled — no vCenter, no advanced API.
– Licensing costs grow fast once clusters expand.
– Closed ecosystem: VMFS ties you to VMware’s tooling.
– Whitebox hardware support is hit-or-miss.
Comparison snapshot
| Tool | What stands out | Best fit |
| ESXi (vSphere Hypervisor) | Stable, enterprise features, VMware ecosystem | Enterprises, critical workloads |
| Proxmox VE | Lightweight, open, strong community | SMBs, labs |
| KVM/libvirt | Kernel-integrated, scriptable | Linux shops, OpenStack |
| Hyper-V | Bundled with Windows Server | Microsoft-centric IT |
Quick start sketch
1. Download ESXi ISO from VMware.
2. Install on server (USB, SD, or disk).
3. Set management IP and root password in DCUI.
4. Connect from another machine with vSphere Client.
5. Create datastore, deploy VMs.
Field notes — 2025
– ESXi is still rock solid in enterprises, but Broadcom’s new licensing model caused unease.
– Labs and homelabs use the free version, but sooner or later run into its limits.
– VMFS is reliable but not portable — once you’re in VMware’s world, you stay there.
– For IT teams needing AD integration, NSX networking, and full HA — it’s the default choice.
– For anyone chasing flexibility and low cost, KVM or Proxmox are more attractive.