VMware ESXi Fundamentals

By Kokil Thapa | Last reviewed: September 2026

VMware ESXi fundamentals matter when you outgrow a single Linux box but are not ready to move every workload to AWS or GCP. ESXi is a bare-metal Type-1 hypervisor. It runs directly on server hardware and hosts multiple virtual machines on one physical host. If you have ever installed Ubuntu on VMware Workstation for local testing, ESXi is the production-side cousin that lives on real server iron. This guide covers architecture, install steps, networking, storage, and practical decision criteria for developers and small ops teams.

What is VMware ESXi and how does it differ from vSphere?

ESXi is the hypervisor kernel. It schedules CPU, RAM, and I/O for each guest VM. vSphere is the broader product suite. It wraps ESXi hosts, vCenter Server, licensing, and management tools into one platform.

Think of ESXi as the engine. vCenter is the control panel for many engines at once. A single-host lab can run ESXi alone. A production cluster almost always adds vCenter for HA, vMotion, and centralized inventory.

ESXi vs Workstation vs KVM at a glance

On client projects I often run Laravel stacks on plain Ubuntu with Apache and PHP-FPM. ESXi enters the picture when the client buys a dedicated server and wants staging, production, and a database VM on one box. That pattern mirrors what many Nepal SMBs do before they adopt full public cloud.

Official product naming now sits under Broadcom after the 2023 acquisition. VMware documentation still refers to ESXi 8.x as the current major line. Always verify licensing on the VMware vSphere documentation portal before you plan a multi-host deployment.

How do you install and configure VMware ESXi on bare-metal hardware?

Installation is straightforward if your hardware appears on the VMware Compatibility Guide. A common mistake is skipping that check and then fighting a NIC driver for hours.

Pre-install checklist

1. Confirm CPU virtualization (Intel VT-x or AMD-V) is enabled in BIOS.
2. Verify NIC, RAID controller, and HBA models against the compatibility list.
3. Prepare a USB installer from the ESXi ISO using Rufus or dd.
4. Plan a static IP, gateway, DNS, and hostname before first boot.
5. Document root and any local datastore naming convention upfront.

Minimum hardware for a lab host is modest. Production hosts need more headroom. Plan for RAM overhead: the hypervisor itself consumes roughly 4–8 GB before any guest starts.

# Create bootable USB on Linux (replace /dev/sdX carefully)
sudo dd if=VMware-VMvisor-Installer-8.0.x.iso of=/dev/sdX bs=4M status=progress conv=fdatasync

# After install, access Host Client in browser
https://<esxi-host-ip>/ui

# Default login: root + password set during install

First-boot configuration through the DCUI (Direct Console User Interface) covers network, DNS, and NTP. Accurate time matters for TLS certificates, log correlation, and vCenter integration later.

Post-install hardening steps

• Change the default root password and store it in a password manager — try the secure password generator for policy-compliant secrets.
• Enable SSH and the ESXi Shell only when you need them, then disable again.
• Apply the latest ESXi patch from the Broadcom support portal promptly.
• Join the host to Active Directory or lock down local accounts if your org requires it.
• Configure a remote syslog target or vCenter logging for audit trails.

For teams that prefer managed Linux over self-hosted hypervisors, Linux system administration on bare Ubuntu often costs less in licensing and ops time. ESXi wins when you need live migration, snapshot discipline, and vendor support on the same platform.

How does networking work on an ESXi host?

ESXi networking revolves around virtual switches (vSwitches) and port groups. Physical NICs (vmnics) uplink to the vSwitch. Port groups tag VLANs and apply security policies to VM vNICs.

A typical two-NIC layout uses one vSwitch for management and VM traffic. A better production layout separates management, VM production, and storage (iSCSI or NFS) onto dedicated port groups or physical NICs.

Key networking concepts

Standard vSwitch (vSS): Configured per host. Fine for single-host labs. Changes do not replicate automatically.

Distributed vSwitch (vDS): Requires vCenter. One logical switch spans many hosts. Essential for vMotion and consistent VLAN policy at scale.

VMkernel port: A special interface for management, vMotion, iSCSI, or NFS. It is not a guest VM NIC.

Understanding L2/L3 basics helps here. If VLAN tagging confuses you, read TCP/IP fundamentals for DevOps first. The same subnet, gateway, and DNS rules apply inside VMs.

Promiscuous mode, MAC address changes, and forged transmits are security settings on each port group. Leave them disabled unless a nested hypervisor or specific appliance requires otherwise.

How do you manage storage and datastores on ESXi?

Every VM lives on a datastore. ESXi supports local VMFS volumes, NFS mounts, and iSCSI LUNs. VMFS (Virtual Machine File System) is VMware's clustered filesystem for block storage.

Datastore design affects backup, snapshot growth, and performance. Splitting OS disks from database volumes is a pattern I use on production Laravel hosts running MySQL 9.7 or PostgreSQL 18 in separate VMs.

Provisioning and snapshot discipline

Thin provisioning saves disk until the guest writes data. Thick eager zeroes blocks at creation. Production database VMs often use thick or thin with careful monitoring — not unlimited thin without alerts.

Snapshots are not backups. They grow delta files and hurt performance when left open for weeks. Schedule proper image-level or agent-based backups instead.

# ESXi Shell — list datastores
esxcli storage filesystem list

# List VMs and their datastore paths
vim-cmd vmsvc/getallvms

# Create snapshot (use sparingly, name with date)
vim-cmd vmsvc/snapshot.create <vmid> pre-patch-2026-09-11 "Before ESXi patch"

# Remove snapshot after verification
vim-cmd vmsvc/snapshot.remove <vmid> <snapshot-id>

For distributed storage at scale, compare ESXi VMFS with Ceph RBD backends in Ceph storage fundamentals. Ceph suits custom cloud builds. VMFS plus vSAN suits teams already invested in the VMware stack.

How do you create and manage virtual machines on ESXi?

VM lifecycle management is the daily work on any ESXi host. You create a VM, attach an ISO or template, install the guest OS, install VMware Tools, then clone or template for repeatability.

Resource allocation best practices

• Set CPU and memory reservations only when SLA guarantees require them.
• Use shares for contention priority, not as a substitute for right-sizing.
• Enable CPU and memory hot-add only if the guest OS supports it.
• Install VMware Tools on every Linux and Windows guest for clean shutdown and time sync.
• Tag VMs by environment (dev, staging, prod) for chargeback and firewall rules.

On infrastructure projects like SRP Infrastructure Development Nepal, separating environments onto distinct VMs reduces blast radius. One bad deploy should not take down the database and cache layer together.

Automation options include PowerCLI, the REST API, Terraform with the vSphere provider, and Ansible modules. Store infrastructure definitions in Git the same way you store application code. That habit aligns with patterns in AWS CloudFormation fundamentals even when the backend is on-prem ESXi instead of EC2.

When should you choose ESXi over cloud VMs or Proxmox?

The right answer depends on budget, staff skills, compliance, and uptime targets. ESXi is not automatically better or worse than AWS, Proxmox, or plain Linux containers.

Nepal businesses with steady traffic on a law portal or eCommerce store sometimes keep production on a Kathmandu colo ESXi host. Burst campaigns may still front the site with CDN and run ads landing pages in cloud. Hybrid beats pure either-or.

Compare multi-site strategies in active-active vs active-passive multi-cloud. ESXi often anchors the passive or primary on-prem side of that diagram.

Monitoring ESXi hosts with Prometheus exporters or vCenter alarms parallels Prometheus metrics monitoring fundamentals. Watch CPU ready time, memory ballooning, datastore latency, and host hardware sensors.

Common production gotchas

CPU ready time above 5%: The host is oversubscribed. Add cores or migrate VMs.

NTP drift: Breaks TLS and distributed logs. Point ESXi and every guest at the same stratum-2 source.

Snapshot chains: Fill datastores silently. Audit weekly.

License expiry after Broadcom changes: Hosts enter evaluation mode with feature limits. Track renewal dates like any other SaaS bill — roughly Rs 15,000–80,000/year per socket depending on bundle, ~USD 110–580 at 2026 rates.

Firmware mismatch on NICs: Causes intermittent vMotion failures. Match driver, firmware, and compatibility guide entries.

If you are migrating off aging ESXi hardware to cloud or bare Linux, website migration services and hosting planning should cover DNS cutover, rsync or snapshot export, and rollback windows — not just VM export alone.

Key Takeaways

• ESXi is a Type-1 hypervisor on bare metal; vSphere adds multi-host management, HA, and vMotion.
• Verify hardware compatibility, enable VT-x/AMD-V, and harden the host before deploying production VMs.
• Separate management, VM, and storage traffic with vSwitches, port groups, and VLANs.
• Treat snapshots as short-term rollback aids — not a backup strategy for VMFS datastores.
• Match ESXi, public cloud, or Proxmox to workload predictability, licensing budget, and team skills.
• Automate VM provisioning with templates, Git-tracked config, and monitoring for CPU ready and datastore growth.

People Also Ask

Is VMware ESXi free to use?

VMware discontinued the free ESXi hypervisor license in 2024 as part of Broadcom's subscription restructuring. Evaluation mode allows a 60-day full-feature trial. Production use now requires a paid vSphere subscription bundle. Check current terms on the official Broadcom VMware portal before planning a long-term homelab or SMB deployment.

What is the difference between ESXi and vCenter?

ESXi runs virtual machines on physical hardware. vCenter Server is a separate appliance or Windows service that manages many ESXi hosts from one console. You can run ESXi standalone via the Host Client. vCenter unlocks cluster features like HA, DRS, and distributed vSwitches across multiple hosts.

Can you run Docker containers directly on ESXi?

ESXi hosts VMs, not containers natively. You deploy a Linux VM on ESXi and run Docker or containerd inside that guest. For Kubernetes on VMware, operators typically use Tanzu or install K8s on VMs. Nested virtualization is possible but adds overhead and support complexity.

How much RAM does ESXi need for a home lab?

Allocate at least 8 GB for the hypervisor overhead on a lab host. Plan 16 GB or more if you run multiple VMs concurrently — for example one Ubuntu dev box, one Windows test VM, and one database instance. Production hosts with mixed workloads often start at 128 GB and scale up.

Build a virtualization strategy that fits your stack

VMware ESXi fundamentals come down to one idea: isolate workloads on shared hardware with predictable resource boundaries. Whether you host a Laravel booking platform, a WooCommerce store, or internal APIs, the hypervisor layer should match your ops capacity and budget. I have spent years on Ubuntu production servers and GitLab CI deploy pipelines. ESXi sits naturally in the same toolbox when a client owns hardware and wants VM-level isolation without monthly cloud compute bills.

Need help choosing between on-prem VMs, cloud VPCs, or a hybrid layout for your next project? Review the portfolio for real deployments, explore enterprise application development options, or contact us to map VMware ESXi fundamentals to your actual traffic, compliance, and budget constraints.