Move Application Migration

Long story short, W2016 server moving from HV to AHV. VirtIO drivers are installed but whenever the machine boots after migrating to AHV, it's bsods with inaccessible boot device. If I go through the whole booting to recovery, deleting the driver and injecting the driver, it boots up but thats a lot of manual handling.When MOVE migrates to AHV it boots up as SATA drive then it seems to clone the disk and reattaches it as a SCSI drive. It boots to the desktop as SATA but then as a SCSI drive it fails, so the driver issue makes sense. The issue is why the drivers are not working when they're installed on the HV machine before migration and don't work after.

The following migrations are not recommended, but can be performed with some limitations. Exchange should be migrated by installing newer versions of Exchange Server in parallel with existing production environments, then move user mailboxes from the old system to the new one. Domain controllers should be migrated by preparing a new domain controller, and then migrating the Flexible Single Master Operations (FSMO) roles. Move migrates database VMs similar to any other VMs;however, the migration happens at the VM level, not the application level. Move will not perform any application-level changes, disk layout updates or best practices on the migrated VM. The above approach should be fine for smaller SQL DB servers and for servers without PCI Pass-through, pRDM disks or multi-writer disks (clustered NTFS). Also, for larger SQL DB servers, Nutanix recommends you to apply Nutanix best practices to create additional vDisks and rebalance data across those disks to take advantage o

I am getting this error when adding my AWS environment to Nutanix Move toolAWS Authorization Error. RequestCanceled: request context canceled caused by: context deadline My move tool version is 4.0.0

Is it possible for purposes of DR in a cloud solution to move just the VMWare environment?Can you replicate your Production Nutanix VMware environment to a cloud based solution? Say IBM cloud? They say you can but i guess i am having a hard time seeing how that will work? I am really new to the whole cloud solution arena and my company wants to move our DR\Datacenter to cloud? We have business reasons for using IBM cloud but they do not have a nutanix cloud infrastructure but tell us we can bring our VMWare environment. 

I’m just getting started with Move. We need to move VMs from an ESXi cluster to a new Nutanix AHV cluster. The ESXi hosts are managed by vCenter.Do I start by deploying the Move appliance in vCenter or on the Prism Central or PE?The Release Notes for 4.0 show our versions of ESXi, vCenter, AOS and Prism Central are supported.

I have just install Move 4.0.0 and need to set the static IP address. I am using the procedures in the Move User Guide. When I bring up the console from PE, I am having prompt synchronization problems.The prompt appears after I provide the input. For example, I do not get a login prompt, but type the user id, then I get no prompt for password but enter the password. I was able to figure out the sequence to get through the password change without prompts, but now I can’t make it through the static IP configuration.Is any else having this problem and knows how to fix it?

Hi All,Does Nutanix Move support to move from google cloud platform (GCP) workflow to Nutanix AHV (On-premise)? Is there any alternative way for this?

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).VMware Tools is still installed on the server however it won’t uninstall cleanly after the migration so I’ve disabled all of the ‘VMware’ services i

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 according to the User Guide values. Also, it should be verified that the Windows VM instance is properly managed by the AWS SSM Manager prior to a migration attempt. Further information regarding this can be found within the AWS to Nutanix Clusters on AWS and AHV VM Migration section

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 Domain. Power Off the VM Create a schedule for (N) hours temporarily and initiate a full replication. After replication is complete, restore the VM from snapshot on cluster B and power on the VM. Unprotect the VM from Protection Domain, Delete the schedule, snapshots and Protection Domain on cluster A. Un-configure the Remote Site on Cluster AConfiguring Remote Sites (Part 1) : https://www.youtube.com/watch?v=5lva3Z_HDPc&ab_channel=NutanixUniversityConfiguring Remote Sites (Part 2) : http

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.