|This article relies on references to primary sources. (November 2011)|
|Stable release||5.5 Update 1 (Build 1623387) / 11 March 2014|
|Platform||i386 (discontinued in 4.0 onwards), x86-64|
VMware ESX is an enterprise-level computer virtualization product offered by VMware. ESX is a component of VMware's larger offering, VMware Infrastructure, which adds management and reliability services to the core server product. VMware is replacing the original ESX with ESXi.
VMware ESX and VMware ESXi are Type 1 hypervisors that are VMware's enterprise software hypervisors for guest virtual servers that run directly on host server hardware without requiring an additional underlying operating system.
The host server requires some form of persistent storage (typically an array of hard disk drives) that store the hypervisor and support files. A smaller footprint variant, ESXi, does away with the first requirement by permitting placement of the hypervisor on a dedicated compact storage device. Both variants support the services offered by VMware Infrastructure.
- 1 Naming
- 2 Technical description
- 3 Versions
- 4 Related or additional products
- 5 Known limitations
- 6 See also
- 7 References
- 8 External links
VMware, Inc. refers to the hypervisor used by VMware ESX as "vmkernel".
VMware states that the ESX product runs on bare metal. In contrast to other VMware products, it does not run atop a third-party operating system, but instead includes its own kernel. A Linux kernel is started first, and is then used to load a variety of specialized virtualization components, including VMware's vmkernel component. This previously booted Linux kernel then becomes the first running virtual machine and is called the service console. Thus, at normal run-time, the vmkernel is running on the bare computer and the Linux-based service console runs as the first virtual machine. As of version 4.1, VMWare has dropped development of ESX and now focuses exclusively on ESXi which does not include a Linux kernel.
- guest systems
- service console (Console OS)
Interface to hardware
The vmkernel handles CPU and memory directly, using scan-before-execution (SBE) to handle special or privileged CPU instructions and the SRAT (system resource allocation table) to track allocated memory.
Access to other hardware (such as network or storage devices) takes place using modules. At least some of the modules derive from modules used in the Linux kernel. To access these modules, an additional module called
vmklinux implements the Linux module interface. According to the README file, "This module contains the Linux emulation layer used by the vmkernel."
The vmkernel uses the device drivers:
These drivers mostly equate to those described in VMware's hardware compatibility list. All these modules fall under the GPL. Programmers have adapted them to run with the vmkernel: VMware Inc has changed the module-loading and some other minor things.
In ESX (and not ESXi), the Service Console is a vestigial general purpose operating system most significantly used as bootstrap for the VMware kernel, vmkernel, and secondarily used as a management interface. Both of these Console Operating System functions are being deprecated from version 5.0, as VMware migrates exclusively to the 'embedded' ESXi model, current version being ESXi. The Service Console, for all intents and purposes, is the operating system used to interact with VMware ESX and the virtual machines that run on the server.
ESX uses a Linux kernel to load additional code: often referred to by VMware, Inc. as the "vmkernel". The dependencies between the "vmkernel" and the Linux part of the ESX server have changed drastically over different major versions of the software. The VMware FAQ states: "ESX Server also incorporates a service console based on a Linux 2.4 kernel that is used to boot the ESX Server virtualization layer". The Linux kernel runs before any other software on an ESX host. On ESX versions 1 and 2, no VMkernel processes run on the system during the boot process. After the Linux kernel has loaded, the S90vmware script loads the vmkernel. VMware Inc states that vmkernel does not derive from Linux, but acknowledges that it has adapted certain device-drivers from Linux device drivers. The Linux kernel continues running, under the control of the vmkernel, providing functions including the proc file system used by the ESX and an environment to run support applications. ESX version 3 loads the VMkernel from the Linux initrd, thus much earlier in the boot-sequence than in previous ESX versions.
In traditional systems, a given operating system runs a single kernel. The VMware FAQ mentions that ESX has both a Linux 2.4 kernel and vmkernel – hence confusion over whether ESX has a Linux base. An ESX system starts a Linux kernel first, but it loads vmkernel (also described by VMware as a kernel), which according to VMware 'wraps around' the linux kernel, and which (according to VMware Inc) does not derive from Linux.
The ESX userspace environment, known as the "Service Console" (or as "COS" or as "vmnix"), derives from a modified version of Red Hat Linux, (Red Hat 7.2 for ESX 2.x and Red Hat Enterprise Linux 3 for ESX 3.x). In general, this Service Console provides management interfaces (CLI, webpage MUI, Remote Console).
As a further detail which differentiates the ESX from other VMware virtualization products: ESX supports the VMware proprietary cluster file system VMFS. VMFS enables multiple hosts to access the same SAN LUNs simultaneously, while file-level locking provides simple protection to file-system integrity.
Purple diagnostic screen
In the event of a hardware error, the vmkernel can 'catch' a Machine Check Exception. This results in an error message displayed on a purple diagnostic screen. This is colloquially known as a purple diagnostic screen, or purple screen of death (PSOD, cf. Blue Screen of Death (BSOD)).
Upon displaying a purple diagnostic screen, the vmkernel writes debug information to the core dump partition. This information, together with the error codes displayed on the purple diagnostic screen can be used by VMware support to determine the cause of the problem.
vMotion: live migration
Live migration (vMotion) in ESX allows a virtual machine to move between two different hosts. Live storage migration (Storage vMotion) enables live migration of virtual disks on the fly. During vMotion Live Migration (vLM) of a running virtual machine (VM) the content of the (RAM) memory of the VM is sent from the running VM to the new VM (the instance on another host that will become the running VM after the vLM). The content of memory is by its nature changing all the time. ESX uses a system where the content is sent to the other VM and then it will check what data is changed and send that, each time smaller blocks. At the last moment it will very briefly 'freeze' the existing VM, transfer the last changes in the RAM content and then start the new VM. The intended effect of this process is to minimize the time during which the VM is suspended; in a best case this will be the time of the final transfer plus the time required to start the new VM.
VMware ESX is available in two main types: ESX and ESXi, although since version 5 only ESXi is continued.
Version release history:
- VMware (7 January 2002)
VMware ESX 1.5
- VMware ESX Server 1.5 (13 May 2002)
VMware ESX 2.0 (21 July 2003)
- VMware ESX Server 2.1 Build 22983 (13 April 2006)
- VMware ESX Server 2.0.2 Build 23922 (May 4, 2006)
VMware ESX 2.5 (14 December 2004)
- VMware ESX Server 2.5.0 Build 11343 (29 November 2004)
- VMware ESX Server 2.5.1 Build 13057 (20 May 2005)
- VMware ESX Server 2.5.1 Build 14182 (20 June 2005)
- VMware ESX Server 2.5.2 Build 16390 (15 September 2005)
- VMware ESX Server 2.5.3 Build 22981 (13 April 2006)
- VMware ESX Server 2.5.4 Build 32233 (October 5, 2006)
- VMware ESX Server 2.5.5 Build 57619 (October 8, 2007)
VMware Infrastructure 3.0 (VI3) (5 June 2006)
- VMware ESX Server 3.0 Build 27701 (13 June 2006)
- VMware ESX Server 3.0.1 Build 32039 (25 September 2006)
- VMware ESX Server 3.0.2 Build 52542 (31 July 2007)
- VMware ESX Server 3.0.3 Build 104629 (8 August 2008)
- VMware ESX Server 3.0.3 Update 1 Build 231127 (8 March 2010)
- VMware ESX Server 3.5 (10 December 2007)
- VMware ESX Server 3.5 Build 64607 (20 February 2008)
- VMware ESX Server 3.5 Update 1 Build 82663 (10 April 2008)
- VMware ESX Server 3.5 Update 2 Build 110268 (13 August 2008)
- VMware ESX Server 3.5 Update 3 Build 123630 (6 November 2008)
- VMware ESX Server 3.5 Update 4 Build 153875 (30 March 2009)
- VMware ESX Server 3.5 Update 5 Build 207095 (20 December 2009) This was the last version to support 32-bit systems 
VMware vSphere 4.0 (20 May 2009)
- VMware ESX 4.0 Build 164009 (21 May 2009)
- VMware ESX 4.0 Update 1 Build 208167 (19 November 2009)
- VMware ESX 4.0 Update 2 Build 261974 (10 June 2010)
- VMware ESX 4.0 Update 3 Build 398348 (5 May 2011)
- VMware ESX 4.0 Update 4 Build 504850 (17 November 2011)
- VMware ESX 4.1 Build 260247 (13 July 2010)
- VMware ESX 4.1 Update 1 Build 348481 (10 February 2011)
- VMware ESX 4.1 Update 2 Build 502767 (27 October 2011)
- VMware ESX 4.1 Update 3 Build 800380 (30 August 2012)
18 July 2010 vSphere 4.1 and its subsequent update and patch releases are the last releases to include both ESX and ESXi hypervisor architectures. Future major releases of VMware vSphere will include only the VMware ESXi architecture. For this reason, VMware recommends that deployments of vSphere 4.x utilize the ESXi hypervisor architecture.
|Stable release||5.5 (build 1331820) / 22 September 2013|
|Type||Virtual machine monitor|
VMware ESXi is a smaller footprint version of ESX that does not include the ESX Service Console. It is available without the need to purchase a vCenter license as a free download from VMware with some features disabled.
VMware ESXi was originally a compact version of VMware ESX that allowed for a smaller 32 MB disk footprint on the Host. With a simple configuration console for mostly network configuration and remote based VMware Infrastructure Client Interface, this allows for more resources to be dedicated to the Guest environments.
There are two variations of ESXi, VMware ESXi Installable and VMware ESXi Embedded Edition. The same installation media will install to either one or the other of these installation modes depending on the size of the target media. It has the ability to upgrade to VMware Infrastructure 3 or VMware vSphere 4.0 ESXi.
Originally named VMware ESX Server ESXi edition, through several revisions the product finally became VMware ESXi 3. New editions then followed: ESXi 3.5, ESXi 4 and now ESXi 5.
To virtualize Windows 8 or Windows Server 2012 as guest operating systems, the ESXi version must be 5.0 update 1 or later.
Version release history:
- VMware ESX 3.0.0 GA (Build 27701) (16 June 2006 )
- VMware ESX 3.0.1 GA (Build 32039) (25 September 2006 )
- VMware ESX 3.0.2 GA (Build 52542) (26 July 2007 )
- VMware ESX 3.0.3 GA (Build 104629) (14 July 2008 )
- VMware ESXi 3.5 GA (Build 64607) (20 February 2008 )
- VMware ESXi 3.5 Update 1 (Build 82663) (10 April 2008 )
- VMware ESXi 3.5 Update 2 (Build 103909) (13 August 2008 )
- VMware ESXi 3.5 Update 3 (Build 123629) (6 November 2008 )
- VMware ESXi 3.5 Update 4 (Build 153875) (30 March 2009 )
- VMware ESXi 3.5 Update 5 (Build 207095) (3 December 2009 )
- VMware ESXi 4.0 GA (Build 164009) (21 May 2009 )
- VMware ESXi 4.0 Update 1 (Build 208167) (19 November 2009 )
- VMware ESXi 4.0 Update 2 (Build 261974) (10 June 2010 )
- VMware ESXi 4.0 Update 3 (Build 403554) (5 May 2011 )
- VMware ESXi 4.0 Update 4 (Build 523315) (17 November 2011 )
- VMware ESXi 4.1 GA (Build 260247) (13 July 2010 )
- VMware ESXi 4.1 Update 1 (Build 351620) (10 February 2011 )
- VMware ESXi 4.1 Update 2 (Build 502767) (27 October 2011 )
- VMware ESXi 4.1 Update 3 (Build 800380) (30 August 2012 )
- VMware ESXi 5.0 GA (Build 469512) (24 August 2011 )
- VMware ESXi 5.0 Update 1 (Build 623860) (15 March 2012 )
- VMware ESXi 5.0 Update 2 (Build 914586) (20 December 2012 )
- VMware ESXi 5.0 Update 3 (Build 1311175) (17 October 2013 )
- VMware ESXi 5.1 GA (Build 799733) (10 September 2012 )
- VMware ESXi 5.1 Update 1 (Build 1065491) (25 April 2013 )
- VMware ESXi 5.1 Update 2 (Build 1483097) (16 January 2014 )
- VMware ESXi 5.5 GA (Build 1331820) (22 September 2013 )
- VMware ESXi 5.5 Update 1 (Build 1623387) (11 March 2014 )
Related or additional products
||This section's use of external links may not follow Wikipedia's policies or guidelines. (November 2012)|
The following products operate in conjunction with ESX:
- vCenter Server, enables monitoring and management of multiple ESX, ESXi and GSX servers. In addition, users must install it to run infrastructure services such as:
- vMotion (transferring virtual machines between servers on the fly whilst they are running, with zero downtime)
- svMotion aka Storage vMotion (transferring virtual machines between Shared Storage LUNs on the fly, with zero downtime)
- enhanced vMotion aka evMotion (a simultaneous vMotion and svMotion, supported on version 5.1 and above)
- DRS (automated vMotion based on host/VM load requirements/demands)
- HA (restarting of Virtual Machine Guest Operating Systems in the event of a physical ESX Host failure)
- Fault Tolerance (almost instant stateful fail-over of a VM in the event of a physical host failure)
- Converter, enables users to create VMware ESX Server- or Workstation-compatible virtual machines from either physical machines or from virtual machines made by other virtualization products. Converter replaces the VMware "P2V Assistant" and "Importer" products — P2V Assistant allowed users to convert physical machines into virtual machines; and Importer allowed the import of virtual machines from other products into VMware Workstation.
- vSphere Client (formerly VMware Infrastructure Client), enables monitoring and management of a single instance of ESX or ESXi server. After ESX 4.1, vSphere Client was no longer available from the ESX/ESXi server, but must be downloaded from the VMware web site.
Cisco Nexus 1000v
Network-connectivity between ESX hosts and the VM's running on it relies on virtual NIC's (inside the VM) and virtual switches. The latter exists in two versions: the 'standard' vSwitch allowing several VM's on a single ESX host to share a physical NIC and the 'distributed vSwitch' where the vSwitches on different ESX hosts together form one logical switch. Cisco offers in their Cisco Nexus product-line the Nexus 1000v, an advanced version of the standard distributed vSwitch. A Nexus 1000v consists of two parts: a supervisor module (VSM) and on each ESX host a virtual ethernet module (VEM). The VSM runs as a virtual appliance within the ESX cluster or on dedicated hardware (Nexus 1010 series) and the VEM runs as module on each host and replaces a standard dvS (distributed virtual switch) from VMware. Configuration of the switch is done on the VSM using the standard NX-OS CLI. It offers capabilities to create standard port-profiles which can then be assigned to virtual machines using vCenter.
There are several differences between the standard dvS and the N1000v, one is that the Cisco switch generally has full support for network technologies such as LACP link aggregation or that the VMware switch supports new features such as routing based on physical NIC load. However the main difference lies in the architecture: Nexus 1000v is working in the same way as a physical Ethernet switch does while dvS is relying on information from ESX. This has consequences for example in scalability where the limit for a N1000v is 2048 virtual ports against 60000 for a dvS. The Nexus1000v is developed in co-operation between Cisco and VMware and uses the API of the dvS
Third party management tools
Because VMware ESX is a leader in the server-virtualisation market, software and hardware vendors offer a range of tools to integrate their products or services with ESX. Examples are the products from Veeam with backup and management applications and a plugin to monitor and manage ESX using HP OpenView, Quest Software with a range of management and backup-applications and most major backup-solution providers have plugins or modules for ESX. Using Microsoft Operations Manager (SCOM) 2007/2012 with a Bridgeways ESX managementpack gives you a realtime ESX datacenter healthview.
Also hardware-vendors such as HP and Dell include tools to support the use of ESX(i) on their hardware platforms. An example is the ESX module for Dell's OpenManage management platform.
VMware have added a Webclient since v5 but it will work on vCenter only and contains not all features. vEMan is a Linux application which is trying to fill that gap. These are just a few examples: there are numerous 3rd party products to manage, monitor or backup ESX infrastructures and the VM's running on them
Known limitations of VMware ESXi, as of June 2013, include the following:
- Guest system maximum RAM: 1 TB
- Host system maximum RAM: 2 TB
- Number of hosts in a high availability cluster: 32
- Number of hosts in a Distributed Resource Scheduler cluster: 32
- Maximum number of processors per virtual machine: 64
- Maximum number of processors per host: 160
- Maximum number of virtual CPUs per physical CPU core: 25
- Maximum number of virtual machines per host: 512
- Maximum number of virtual disks per virtual machine: 60
- VMFS5 maximum volume size: 64 TB, but maximum file size is 2TB -512 bytes
In terms of performance, virtualization imposes a cost in the additional work the CPU has to perform to virtualize the underlying hardware. Instructions that perform this extra work, and other activities that require virtualization, tend to lie in operating system calls. In an unmodified operating system, OS calls introduce the greatest portion of virtualization "overhead".
Paravirtualization or other virtualization techniques may help with these issues. VMware developed the Virtual Machine Interface for this purpose, and selected operating systems currently[update] support this. A comparison between full virtualization and paravirtualization for the ESX Server shows that in some cases paravirtualization is much faster.
- 64 ESX/ESXi hosts per VSM (Virtual Supervisor Module)
- 2048 virtual ethernet interfaces per VMWare vDS (virtual distributed switch)
- and a maximum of 216 virtual interfaces per ESX/ESXi host
- 2048 active VLAN's (one to be used for communication between VEM's and VSM)
- 2048 port-profiles
- 32 physical NIC's per ESX/ESXi (physical) host
- 256 port-channels per VMWare vDS (virtual distributed switch)
- and a maximum of 8 port-channels per ESX/ESXi host
- Comparison of platform virtual machines
- KVM Linux Kernel-based Virtual Machine – an open source hypervisor platform
- Hyper-V – a competitor of VMware ESX from Microsoft
- Xen – an open source hypervisor platform
- Virtual appliance
- Virtual machine
- Virtual disk image
- VMware VMFS
- x86 virtualization
- "VMware ESX 4.0 only installs and runs on servers with 64bit x86 CPUs. 32bit systems are no longer supported.". VMware, Inc.
- VMWare website on ESXi 5.0:Upgrade to ESXi, visited 2 February 2012
- "ESX Server Architecture". Vmware.com. Archived from the original on 2009-11-07. Retrieved 2009-10-22.
- "Meet the Next Generation of Virtual Infrastructure Technology". VMware. Retrieved 2007-09-21.
- "What does ESX stand for?"
- "Glossary". Developer’s Guide to Building vApps and Virtual Appliances: VMware Studio 2.5. Palo Alto: VMware Inc. 2011. p. 153. Retrieved 2011-11-09. "ESXi[:] Elastic Sky X (ESX) pared down to a bare-metal server [...]"
- "ESX Server Datasheet"
- "ESX Server Architecture". Vmware.com. Archived from the original on 29 September 2007. Retrieved 2009-07-01.
- "ESX machine boots". Video.google.com.au. 12 June 2006. Retrieved 2009-07-01.
- "Support for 64-bit Computing". Vmware.com. 19 April 2004. Retrieved 2009-07-01.
- Gerstel, Markus: "Virtualisierungsansätze mit Schwepunkt Xen"[dead link]
- VMware ESX
- "VMware ESX Server 2: NUMA Support". Palo Alto, California: VMware Inc. 2005. p. 7. Retrieved 2011-03-29. "SRAT (system resource allocation table) – table that keeps track of memory allocated to a virtual machine."
- "ESX Server Open Source". Vmware.com. Retrieved 2009-07-01.
- "ESX Hardware Compatibility List". Vmware.com. 10 December 2008. Retrieved 2009-07-01.
- "ESXi vs. ESX: A comparison of features". Vmware, Inc. Retrieved 2009-06-01.
- VMware FAQ[dead link]
- ESX Server Advanced Technical Design Guide[dead link]
- "KB: Decoding Machine Check Exception (MCE) output after a purple diagnostic screen |publisher=VMware, Inc."
- The Design and Evolution of Live Storage Migration in VMware ESX
- VMWare Blog by Kyle Gleed: vMotion: what's going on under the covers, 25 February 2011, visited: 2 February 2012
- VMware website vMotion brochure. Retrieved 3 February 2012
- VMWare KBArticle Windows 8/Windows 2012 doesn't boot on ESX, visited 12 September 2012
- "Correlating vCenter Server and ESXi/ESX host build numbers to update levels (1014508)". VMware, Inc.
- "Download VMware vSphere Hypervisor (ESXi)". www.vmware.com. Retrieved 22 July 2014.
- "Getting Started with ESXi Installable". https://www.vmware.com/. VMware. Retrieved 22 July 2014.
- "VMware ESX and ESXi 4.1 Comparison". Vmware.com. Retrieved 2011-06-09.
- http://www.v-front.de/2013/03/esxi-embedded-vs-esxi-installable-faq.html. Missing or empty
- "Free VMware ESXi: Bare Metal Hypervisor with Live Migration". Vmware.com. Retrieved 2009-07-01.
- Overview of the Nexus 1000v virtual switch, visited 9 July 2012
- VMware continues virtualization market romp, 18 April 2012. Visited: 9 July 2012
- About Veeam, visited 9 July 2012
- Veeam Openview plugin for VMware, visited 9 July 2012
- OpenManage (omsa) support for ESXi 5.0, visited 9 July 2012
- VMware info about Webclient – VMware ESXi/ESX 4.1 and ESXi 5.0 Comparison
- Availability of vSphere Client for Linux systems – What the webclient can do and what not
- vEMan website vEMan – Linux vSphere client
- Petri website 3rd party ESX tools, 23 December 2008. Visited: 9 July 2012
- "Configuration Maximums" (PDF). VMware, Inc. 13 August 2012. Retrieved 2012-08-13.
- "What's new in VMware vSphere 4: Performance Enhancements" (PDF). VMware, Inc.
- "Performance of VMware VMI" (PDF). VMware, Inc. 13 February 2008. Retrieved 2009-01-22.