Limitations and Guidelines for running Hyper-V on Nutanix clusters

  • 26 October 2021
  • 0 replies

Userlevel 2
Badge +4
  • Nutanix Employee
  • 69 replies


Nutanix clusters running Hyper-V have the following limitations. Certain limitations might be attributable to other software or hardware vendors:




Hyper-V 2016 clusters and support for Windows Server 2016.


  • VHD Set files (.vhds) are a new shared Virtual Disk model for guest clusters in Microsoft Server 2016 and are not supported. You can import existing shared .vhdx disks to Windows Server 2016 clusters. New VHDX format sharing is supported. Only fixed-size VHDX sharing is supported.

  • Use the PowerShellAdd-VMHardDiskDrive command to attach any existing or new VHDX file in shared mode to VMs. 

For example: Add-VMHardDiskDrive -VMName Node1 -Path \\gogo\smbcontainer\TestDisk\Shared.vhdx -SupportPersistentReservations.


Upgrading Hyper-V Hypervisor Hosts


  • When upgrading hosts to Hyper-V 2016, 2019 and later versions, the local administrator user name and password is reset to the default administrator name Administrator and password nutanix/4u. Any previous changes to the administrator name and/or password are overwritten.


General Guidelines:

  • Do not add any other device (including guest VMs) to the VLAN to which the CVM and hypervisor host are assigned. Isolate guest VMs on one or more separate VLANs.

  • If you are destroying a cluster and creating a new one and want to reuse the hostnames, failover cluster name and storage object name of the previous cluster, remove their computer accounts and objects from AD and DNS first.



  • Intel Advanced Network Services (ANS) is not compatible with Load Balancing and Failover (LBFO), the built-in NIC teaming feature in Hyper-V. For more information, see the Intel support article, Teaming with Intel Advanced Network Servicesducts.html.

  • Nutanix does not support the online resizing of the shared virtual hard disks (VHDX files).


0 replies

Be the first to reply!