Updated on: 02 February 2017 ESXi 6.5.0a | 02 FEB 2017 | ISO Build 4887370 Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

• What's New
• Earlier Releases of ESXi 6.5
• Internationalization
• Patches Contained in this Release
• Resolved Issues
• Known Issues

What's New

This release of ESXi 6.5.0a adds support for NSX 6.3.0. This release also delivers a bug fix that has been documented in the Resolved Issues section.

Earlier Releases of ESXi 6.5

For compatibility, installation and upgrades, product support notices, and features see the earlier release notes of ESXi,

VMware vSphere 6.5 Release Notes

Internationalization

VMware vSphere 6.5 is available in the following languages:

• English
• French
• German
• Japanese
• Korean
• Simplified Chinese
• Traditional Chinese

Components of VMware vSphere 6.5, including vCenter Server, ESXi, the vSphere Web Client, and the vSphere Client do not accept non-ASCII input.

Patches Contained in this Release

This release contains all bulletins for ESXi that were released earlier to the release date of this product. See the My VMware page for more information about the individual bulletins.

Patch Release ESXi650-201701001 contains the following individual bulletins:

• VMware ESXi 6.5, Patch ESXi650-201701401-BG: Updates esx-base,vsan, and vsanhealth

Patch Release ESXi650-201701001 contains the following image profiles:

• VMware ESXi 6.5, Patch ESXi-6.5.0-20170104001-standard
• VMware ESXi 6.5, Patch ESXi-6.5.0-20170104001-no-tools

Resolved Issues

This section describes the resolved issue:

• Attempts to perform vMotion of VMs from earlier releases of ESXi to ESXi 6.5 might fail with an error
  Attempts to perform vMotion of VMs from earlier releases of ESXi to ESXi 6.5 might fail with a purple diagnostic screen with a stack trace similar to the following:
  
  #GP Exception 13 in world XXXXXX:vmm3:XXXXXXXX @ 0xXXXXXXXXXXXXxxxx-xx-xxTxx:xx:xx.xxxZ cpu16:XXXXXX)Backtrace for current CPU #16, worldID=XXXXXX,fp=0x0xxxx-xx-xxTxx:xx:xx.xxxZcpu16:XXXXXX)0xXXXXXXXXXXXX:[0xXXXXXXXXXXXX]VmAnon_AllocVmmPages@vmkernel#nover+0x3b stack: 0xXXXXXXXXX, 0xXXXXXXXXX, 0xXXXXXXXXXXXX, 0x6, 0xXXXXXXXXXXXXxxxx-xx-xxTxx:xx:xx.xxxZ cpu16:XXXXXX)0xXXXXXXXXXXXX:[0xXXXXXXXXXXXX]VMMVMKCall_Call@vmkernel#nover+0x157 stack: 0xXXXXXXXXXXXX, 0xXXXXXXXXXXXX, 0xXXXXXXXXXXXX, 0xfffffffffc606d00, 0x0 xxxx-xx-xxTxx:xx:xx.xxxZ cpu16:XXXXXX)0xXXXXXXXXXXXX:[0xXXXXXXXXXXXX]VMKVMM_ArchEnterVMKernel@vmkernel#nover+0xe stack: 0x0, 0xfffffffffc4074b3, 0x0, 0x0, 0x0 xxxx-xx-xxTxx:xx:xx.xxxZ cpu16:XXXXXX)Panic: 623: Halting PCPU 16. xxxx-xx-xxTxx:xx:xx.xxxZ cpu20:XXXXXX)Panic: 514: Panic from another CPU (cpu 20, world 187418): ip=0xXXXXXXXXXXXX randomOff=0x21c00000:
  
  The issue occurs when the VM meets the following conditions:
  • The VM was previously running on an earlier release of ESXi such as 5.5 or 6.0
  • The VM is NUMA aware (with more than 8 vCPUs)
  • The VM is configured with non-default vNUMA options (like coresPerSocket, numa.autosize.once = false etc.)

  This issue is resolved in this release.

Known Issues

To view the list of known issues applicable from earlier release, please see Known Issues section in the VMware vSphere 6.5 Release Notes.