This post is also available in: Italian

Reading Time: 3 minutes

In a VMware infrastructure, when you build a new VM, the default compatibility level could depend on your vSphere version, from which client you are using (the legacy vSphere Client does not ask for VM virtual hardware version in the default wizard), but also from your cluster settings.

VM virtual hardware version defines exactly the compatibility level, but you can define the default level using the vSphere Web Client or the new HTML5 Client.

Using the HTML5 client you can find the menu directly on the contextual menu of your cluster: just choose the “Edit Default VM Compatibility” voice.

At this point, you can simply choose the VM hardware version, with the details of the expected ESXi compatibility:

From the vSphere Web Client it’s equally simple, by going in the Manage tab of your cluster and select the general options:

Then will be exactly the same:

Why could be important define a lower compatibility level? There are several reasons:

  • Of course to export and import your VM across multiple VMware based environment. OVF format it’s standard, but cannot change the VM hardware level.
  • During a rolling update, of course, you need to keep the right level; but also after could be important stay with the old level in order to have a short term rollback plan, if needed.
  • You may need to extend the on-prem environment with a public cloud in a hybrid approach: but to ensure VM mobility you must use the lower compatibility level.
  • Maybe you don’t have yet a DR site, but in the future you may implement it and in this case could be important ensure the same compatibility. If you re-use old servers for the DR environment, maybe you cannot install the lastest version of vSphere.
Share

Related Posts

  • VM does not start on VMware vSphere

    There are a lot of different possible reasons why a VM does not power on a VMware vSphere infrastructure, but usually, the error message can really help to found the reason or the root cause. Maybe not available resources, maybe some files that are missing,…

  • VMware vSphere 5.1 upgrade path - VM

    After that the vCenter and the ESXi part are upgrade, you can work on the VM part. The VM upgrade is the easy part, but it require VM downtime, so must be planned well. There are two different upgrade for the VM part: VMware Tools…

  • VMware vSphere 5.1 upgrade path - VM

    Dopo la parte relativa all'aggiornamento di vCenter e i vari ESXi, vi è la parte relativa alle VM. Parte relativa semplice, ma che a differenza delle precedenti, richide un certo downtime delle VM, quindi deve essere pianificata attentamente (può comunque essere schedulata). Per quanto riguarda…

Virtualization, Cloud and Storage Architect. Tech Field delegate. VMUG IT Co-Founder and board member. VMware VMTN Moderator and vExpert 2010-24. Dell TechCenter Rockstar 2014-15. Microsoft MVP 2014-16. Veeam Vanguard 2015-23. Nutanix NTC 2014-20. Several certifications including: VCDX-DCV, VCP-DCV/DT/Cloud, VCAP-DCA/DCD/CIA/CID/DTA/DTD, MCSA, MCSE, MCITP, CCA, NPP.