Nutanix Move is a cross-hypervisor mobility solution to move VMs with minimal downtime.
What's New in Release 4.9.1
Upgrade to Move 4.9.1
- Move can be upgraded to version 4.9.1 from the Move versions 4.6.0, 4.7.0, 4.8.0, and 4.9.0.
Support for migration of VM with virtual Trusted Platform Module (vTPM) enabled
- Move now supports the migration of vTPM-enabled VM from ESXi to AHV with Prism Central (PC) as the target.
Support for migration of VM with virtualization-based security (VBS) enabled
- Move now supports the migration of VBS-enabled VM from ESXi to AHV.
- VBS is known as Windows Defender Credential Guard in AHV.
Support for AWS migration with user having Explicit Deny
- Move now supports AWS migration with a user account having Explicit Deny by IP address.
General Availability for additional migrations
- The following migrations are now General Available (GA) with this release:
- AHV to NC2 (on AWS/Azure)
- NC2 (on AWS/Azure) to AHV
- NC2 (on Azure) to NC2 (on Azure)
Filter VMs by tag
- You can filter VMs by tag during the creation of a migration plan.
Change the SSH port number
- You can change the SSH port number and access Move VMs using the new SSH port number.
Support for migration of 100 VMs
- Move now supports the migration of 100 VMs in a migration plan from ESXi to AHV.
Support for configuration of Security Group and Public IP address
- Move now supports the configuration of Security Group and Public IP address for migrations from AHV to AWS/Azure.
New guest operating systems qualification
- The following guest operating systems have been qualified.
- ESXi to AHV: OEL 9.1, Windows Desktop 11
- ESXi to ESXi on Nutanix: Windows Server 2022 (UEFI, BIOS, and Secure Boot)
- AHV to AHV: Windows Desktop 10
- Hyper-V to AHV: RHEL 9.1
- Azure to AHV: Windows Server 2022
Resolved Issues | 4.9.1
Following is the resolved issue that is common for migration from all sources.
- Fixed the issue where the Grafana container would go into a restart loop in Move dark site.
Hyper-V to AHV
Following is the resolved issue for migration from Hyper-V to AHV.
- VM does not boot when fstab has boot points added as comments.
- Post VM migration, the Linux VMs may fail to boot with file system mount failure. This is due to the missing UUID mapping of the boot disk in fstab.
- Enable the fix for this issue by following the steps detailed in KB-15335.