Move Application Migration

Nutanix Move 4.0.0 was just released today.You can read more about it in our product updates community section.Let me know what you think about this release.Be sure to register for our annual .NEXT user conference happening September 20-23, 2021 online. It’s Cloud on your terms.

I am trying to move a VM from EXSI to AHV. When I try the move I get the error “VMTools is not running.” any suggestions?

After converting a VM running Windows 2012 r2 from VMware to Nutanix using Move version 3.4.1, we are receiving event IDs 257 and 259 regularly as shown below.Log Name:      ApplicationSource:        vmStatsProviderDate:          3/15/2021 8:35:34 AMEvent ID:      257Task Category: GeneralLevel:         ErrorKeywords:      ClassicUser:          N/AComputer:      ServerADescription:The "vmStatsProvider" can not be initialized. "vmGuestLib" returns error "VMware Guest API is not running in a Virtual Machine" (2). Log Name:      ApplicationSource:        vmStatsProviderDate:          3/15/2021 8:35:34 AMEvent ID:      259Task Category: Guest Library APILevel:         ErrorKeywords:      ClassicUser:          N/AComputer:      ServerADescription:Unable to start "vmGuestLibrary". Error: "VMware Guest API is not running in a Virtual Machine" (2).

Today we have an Openedge Progress Database running in a VMware cluster.Is it homologated to Nutanix AHV if we migrate?

We’ve migrated a handful of test VMs from our vSphere legacy architecture to Nutanix (also running ESXi)  Both on ESXi 6.5 and latest Prism/software builds, etc.  When using Nutanix Move to do the migration, we’ve noticed that the migrated VM is taking on GMT for its time when the VM boots up.  We are in Michigan so the VM is five hours ahead, but the local windows timezone Eastern. After logging in and/or rebooting, the time typically syncs up fine.  However, this proved to be a major problem when we moved a domain controller and it caused time to be off everywhere.   ncc health_checks network_checks check_ntp all comes back fine and our time sources are defined properly both in Nutanix as well as NTP oin the ESXi host.  What are we missing or is this a bug?

We are migrating workloads from VMware (vSphere 6.5) to Nutanix AHV (AOS 5.15 LTS). With regards to VM templates, any advantage in creating new templates on AHV? Any gotchas if we migrate (as per procedure, prepare and use Nutanix Move) VM templates to AHV? Anyway, we will have to migrate most workloads, but was wondering about VM templates. We’re leaning towards erring on the side of caution and creating new templates (Linux/Windows) on AHV. However, I just wanted to know if anybody experienced issues with VMs built from migrated templates on AHV and any feedback.

I’m trying to move a VM (Ubuntu 18.04), when the cutover is done and i make a console connection the VM, at first the screen is blank, but after a few enters, i start getting the following signs on the console:Anyone has any ideas how to avoid this? I’ve tried installing NGT prior to moving the VM - no luck. On the initial GNU GRUB screen where I choose which OS to boot, everything is fine.

When migrating Windows VMs from AWS into a Nutanix cluster and while using automatic Windows VM preparation, it is important to verify permissions configurations in two places within AWS. Specifically, the permissions for the AWS account that is provided when adding an AWS source into Move and the permissions of the IAM profile associated with the VM instance to be migrated. AWS allows permissions configurations to be viewed/updated in a JSON format. Further, the Move User Guide also lists the necessary permissions for these entities in a JSON format. These JSON values can then be reviewed/compared and, if any of the permissions are missing or configured incorrectly from AWS, simply update the permissions accordi

If I want to migrate Linux (Centos,RHEL,Ubuntu/SUSE) Vms from VMware to AHV using Nutanix move then is below information enough.Below are the configuration settings to look out for when migrating a Linux VM using credentials. Ensure ssh localhost using only password authentication, ie. set “PasswordAuthentication yes” in sshd_config Ensure using sudo, user assume root privileges without entering a password Ensure read and write permission for /tmp. root access, sshd service running If this is correct then I can normally migrate the Linux VMs same as I migrated the Windows VM?

So guys I’ve got a flexlm license server running Windows Server 2019 that I am trying to use Move to migrate into my AHV cluster.  I tried migrating it once and it blew up the license server since I guess it builds a unique machine ID using a disk and perhaps CPU ID. Any idea on how to clone this in Move so when it comes across FlexLM and other license daemons are none the wiser?

I am moving virtual machines with Move 3.6.2 from Hyper-V to an AHV CE cluster. Everything goes well, but after the cutover the AHV VM is stuck at the ‘Press F2 for EFI boot manager’ screen and cpu usage around 52%. Pressing FN+F2, F2, CTRL+F2, ALT+F2 or other combinations have no effect. Please advise. Hyper-V host is Win2019, VM is 2019 with boot from bootmgfw.efi and secure boot disabled. Also tried with Edge, Chrome and IE, same result, stuck at ‘Press F2 for EFI boot manager’ screen.

These days I’m managing, for one of customer, the migration of its virtual infrastructure to a Nutanix AHV farm from an old ESXi. It has some old VMs, with Windows XP as guest OS, that have to be migrated in Nutanix. Those VMs have installed custom software that cannot be installed in newer versions of Windows because they have been written in old VB6, so my question are:Can they be migrated over AHV? If yes, can I manage the migration with Nutanix Move or there is another way?

where  i can download move software for conversation 

When trying to move from esxi to AHV of a VM with OS Debian 10, I get an error This VM is not on the AHV supported OS list. To proceed with migrating this VM, please be sure to bypass guest operations and take care of installing AHV device drivers separately. This VM has a guest OS which is not supported on ESXi. Please remove the vm from the migration plan if migrating to ESXi. Is it OS not supported?

There are several ways to move a VM from one cluster to another.A. For moving a VM from Non-Nutanix cluster to Nutanix use Nutanix Move available on the PortalNutanix Move is a cross-hypervisor mobility solution to move VMs with minimal downtime.B. For Moving a VM from one Nutanix cluster to another use Asynchronous Disaster Recovery Between On Premise Data CentersSummary of stepsConfigure a Remote Site on Cluster A Create a Protection Domain on Cluster A. Add the VM to be moved to this Protection Domai

I attempted several times to move a test VM over and I am running into a issue with the Mount Container process. Is there a fix for this. I suspect it to be an Firewall issue, Any help would be appreciated.Failed VM Migration: prepare target: [[Location="/hermes/go/src/tgtagent/ahvtargetprovider.go:567", Msg="Error creating target path [Container="default-container-90861820611740", Err="exit status 32", Location="/hermes/go/src/libcloud/prism/ahvmountimpl.go:146"] Container mount failed (error=0x4012)"] Target agent error (error=0x4003)]

Looking on OS supported to migrate with Nutanix Move v3.6.0 I see CentOS 8.2 as supported but when I add a CentOS 8.2.2004 VM to be migrated from ESXi 6.7u2 to AHV 20170830.434 I get this warning:This VM is not on the AHV supported OS list. To proceed with migrating this VM, please be sure to bypass guest operations and take care of installing AHV device drivers separately. This VM has a guest OS which is not supported on ESXi. Please remove the vm from the migration plan if migrating to ESXi.Is this expected?

Looking for advise, Trying to add a Hyper-V host to Move 3.5.0, but just getting the following error and nothing else, Hyper-V operation [Get Process Info] failed. Getting no other alerts/Errors.

We are transferring vdisks from one Nutanix environment to another.  We are going from Euphrates 5.5.8 to Euphrates  5.9. The copy seems to work but then after a while (maybe 15 minutes) the files in the new environment disappear. We’ve tried this several times with the same results. One vDisk is around 26 GB and the other is 2 TB. Has anyone seen this and what is the problem and the solution?

Nutanix Move (a.k.a Move) is a cross-hypervisor mobility solution to move VMs with minimal downtime. Move supports migration from the following sources to targets, with first platform being the source and second platform being the target.VMware ESXi to Nutanix AHV VMware ESXi on legacy infrastructure to VMware ESXi on Nutanix Microsoft Hyper-V to Nutanix AHV AWS EC2 to Nutanix AHV AWS EC2 to VMware ESXi on Nutanix Nutanix AHV to AWS EC2Since infrastructure underneath platform is different, a small downtime is incurred during cutover from any of the preceding sources to targets.If this sounds Interesting, but you have a lot queries about this Amazing Solution i.e. NUTANIX MOVE.Relax…!!Here is link to answer most of your queries –

Good afternoon, all!I’m setting up a Move project to migrate some VMs from Hyper-V to AHV. In the 3.6 Move user guide, it says “You need PowerShell version 4.0 or later.” Do we need it on each source VM, on the HV hosts, on the management workstation, or all three?Thanks to all for looking! Gregg

We need to migrate one VM (a virtual appliance) from one AHV to another with no p connection between the two The AHV versions are different (Euphrates 5.5.8 and Euphrates  5.9). What is the best way to accomplish this.?

How to migrate ESX VM with independent disks and PCIE to AHV

This video demonstrate how Nutanix Calm with the help of Nutanix Move can migrate workloads from the public cloud to on-prem as day-2 operations. This custom integration uses Move APIs to automate the entire process via Calm.   Let the community know how you are using Nutanix Calm and Move. Share your thoughts in the forums.    

We are excited to announce the release of Nutanix Move 3.6.0 Adopting new infrastructure platforms often requires organizations to migrate existing workloads against tight timelines. Nutanix Move simplifies this process with infrastructure-level bulk VM migrations, removing the friction associated with onboarding new infrastructure, and enabling businesses to quickly leverage the full potential of Nutanix Enterprise Cloud, with near-zero VM or application service outage during migrations. Nutanix Move 3.6.0 is released and the bits are available on the portal for download. Release Notes User Guide