Migrate from VMware to AHV - stuck Booting from Hard Disk...

Hi
Do you have Mobility/NGT installed on the original VM while running on ESXi, or try booting with IDE as a controller (NOT RECOMMENDED)?
When u create VM from ADFS did u select the vmdk-flat file?

Why not use Xtract for VM to simplify the migration.

https://portal.nutanix.com/#/page/xtract

F>P

Hi farhanparkar,
thank you for the quick reply.
I dont have Mobility/NGT installed on the VMDK File. (this vmdk file is the file I got from other poc environment. VMware environment is no longer available. If I plug the vmdk file as a second disk to another machine it works fine.)
I've tried booting with IDE but no luck.
I'm actually a beginner about Nutanix. I did not know Xtract.

thx

Hi OnderAvcu

Take a look here to learn more about access to Xtract for VMs [go]. Also check out this blog - Day in the life of a Migration with Nutanix Xtract for Virtual Machines. Let me know if this helps!

Hi Aluciani,

this vmdk file is the file I got from other poc environment. VMware environment is no longer available. it is not possible to solve it in a different way 😞
I have to solve the boot problem.

thx

Hi,

Whats the actual size of vmdk file, can u try creating VM as IDE controller.

F>P

OnderAvcuAre you migration a UEFI enabled vm disk?

vmdk file size is 250 GB (30 GB used space)

Hi Sandeepmp,

I did not check. 😕

Hi,
Looking at the provided info below things can be tried,
1) Try to identify the original environment where the file was created, if it was VMware Workstation then vmdk is ok, if VMware ESXi it should be vmname-flat.vmdk. Try to use the file at the source like environment (ESXi or Workstation) again to make sure the file itself is not corrupted.
2) What operating system was installed, as you said there is no NGT installed hence the AHV SCSI controller will not be detected by the installed OS, re-create using IDE as controller and verify if it is booting. If it works then you can install NGT and update to SCSI controller.
3) Possibly VM was using UEFI at source if yes then u need to set it using acli.
The below link should work.
http://vmwaremine.com/2015/08/27/migrate-windows-2012r2-server-from-esxi-to-ahv

F>P

hi,

Thanks for your help. I will be back at the customer location on Wednesday. I will try the suggestions.

regards,

OnderAvcu

Before migrating VMs to AHV you need to make sure to uninstall the VMware tools and install NGT tools.

Refer the below guide to verify the pre-requirements.

https://portal.nutanix.com/#/page/docs/details?targetId=Migration-Guide-AOS-v51:vmm-vms-migrating-non-ntnx-ahv-t.html


Or if you are moving a UEFI enabled vms to AHV from ESXi , then this is an un-supported configuration.

" VMs Requiring a Rebuild Before Migrating
Windows VMs using Unified Extensible Firmware Interface (UEFI) in ESXi clusters are not supported for migration in AOS or AHV."

https://portal.nutanix.com/#/page/docs/details?targetId=Migration-Guide-AOS-v51:vmm-vm-migration-prereqs-windows-c.html

Do you find the solution OnderAvcu?? I have the same issue.

sandeepmp wrote:

OnderAvcu

Before migrating VMs to AHV you need to make sure to uninstall the VMware tools and install NGT tools.

Refer the below guide to verify the pre-requirements.

https://portal.nutanix.com/#/page/docs/details?targetId=Migration-Guide-AOS-v51:vmm-vms-migrating-non-ntnx-ahv-t.html


Or if you are moving a UEFI enabled vms to AHV from ESXi , then this is an un-supported configuration.

" VMs Requiring a Rebuild Before Migrating
Windows VMs using Unified Extensible Firmware Interface (UEFI) in ESXi clusters are not supported for migration in AOS or AHV."

https://portal.nutanix.com/#/page/docs/details?targetId=Migration-Guide-AOS-v51:vmm-vm-migration-prereqs-windows-c.html

You could change vm BIOS to UEFI:

1. power off your vm
2. ssh to you CVM
3. acli vm.update your_vm_name uefi_boot=True

Assuming that what is on the vmdk is actually a valid installation of Windows and all that is missing is the Virtio SCSI driver, I have successfully used the following procedure:

• Deploy Windows Repair ISO (matching the version on vmdk) and VirtIO driver ISO with Image Service
• Assign Windows Repair ISO to VM's CDROM drive
• create a second CDROM for VM and assign VirtIO ISO to it
• Boot from first CDROM
• In Windows Repair Options, load SCSI driver from second CDROM to gain access to Windows volume on virtual disk.
• Launch a DOS-Box.
• Launch diskpart, type list vol and take note of drive letters of Windows drive and driver CDROM. Make sure that Windows partition is flagged active. Exit Diskpart
• In DOS Box enter dism /image:[WindowsDrive]:\ /add-driver /Driver:"[DriverCDROM]:\[OS-Version]\amd64" /recurse (Replace WindowsDrive and DriverCDROM with letters and OS-Version with a path on Driver-CDROM. Note that paths on the VirtIO CD may contain spaces, hence the quotes.
• Example: dism /image:C:\ /add-driver /Driver:"E:\Windows 7\amd64" /recurse
• Eject both CD images from Prism.
• Reboot VM

DASR wrote:

sandeepmp wrote:

OnderAvcu

Before migrating VMs to AHV you need to make sure to uninstall the VMware tools and install NGT tools.

Refer the below guide to verify the pre-requirements.

https://portal.nutanix.com/#/page/docs/details?targetId=Migration-Guide-AOS-v51:vmm-vms-migrating-non-ntnx-ahv-t.html


Or if you are moving a UEFI enabled vms to AHV from ESXi , then this is an un-supported configuration.

" VMs Requiring a Rebuild Before Migrating
Windows VMs using Unified Extensible Firmware Interface (UEFI) in ESXi clusters are not supported for migration in AOS or AHV."

https://portal.nutanix.com/#/page/docs/details?targetId=Migration-Guide-AOS-v51:vmm-vm-migration-prereqs-windows-c.html

You could change vm BIOS to UEFI:

1. power off your vm
2. ssh to you CVM
3. acli vm.update your_vm_name uefi_boot=True

The source virtual machine is using UEFI. I ran the command vm.update uefi_boot=True and the operating system does not load.

Is there another procedure that I can do?

MMSW_DE wrote:

Assuming that what is on the vmdk is actually a valid installation of Windows and all that is missing is the Virtio SCSI driver, I have successfully used the following procedure:

• Deploy Windows Repair ISO (matching the version on vmdk) and VirtIO driver ISO with Image Service
• Assign Windows Repair ISO to VM's CDROM drive
• create a second CDROM for VM and assign VirtIO ISO to it
• Boot from first CDROM
• In Windows Repair Options, load SCSI driver from second CDROM to gain access to Windows volume on virtual disk.
• Launch a DOS-Box.
• Launch diskpart, type list vol and take note of drive letters of Windows drive and driver CDROM. Make sure that Windows partition is flagged active. Exit Diskpart
• In DOS Box enter dism /image:undefinedindowsDrive]:\ /add-driver /Driver:"undefinedriverCDROM]:\undefinedersion]\amd64" /recurse (Replace WindowsDrive and DriverCDROM with letters and OS-Version with a path on Driver-CDROM. Note that paths on the VirtIO CD may contain spaces, hence the quotes.
• Example: dism /image:C:\ /add-driver /Driver:"E:\Windows 7\amd64" /recurse
• Eject both CD images from Prism.
• Reboot VM

Do you tested with virtual machines that are using UEFI?

jalfarosv wrote:

Do you tested with virtual machines that are using UEFI?

No, unfortunately I didn't.

MMSW_DE wrote:

jalfarosv wrote:

Do you tested with virtual machines that are using UEFI?

No, unfortunately I didn't.

Have you ever migrated vms from VMware to Nutanix that are using UEFI?

jalfarosv wrote:

DASR wrote:

sandeepmp wrote:

OnderAvcu

Before migrating VMs to AHV you need to make sure to uninstall the VMware tools and install NGT tools.

Refer the below guide to verify the pre-requirements.

https://portal.nutanix.com/#/page/docs/details?targetId=Migration-Guide-AOS-v51:vmm-vms-migrating-non-ntnx-ahv-t.html


Or if you are moving a UEFI enabled vms to AHV from ESXi , then this is an un-supported configuration.

" VMs Requiring a Rebuild Before Migrating
Windows VMs using Unified Extensible Firmware Interface (UEFI) in ESXi clusters are not supported for migration in AOS or AHV."

https://portal.nutanix.com/#/page/docs/details?targetId=Migration-Guide-AOS-v51:vmm-vm-migration-prereqs-windows-c.html

You could change vm BIOS to UEFI:

1. power off your vm
2. ssh to you CVM
3. acli vm.update your_vm_name uefi_boot=True

The source virtual machine is using UEFI. I ran the command vm.update uefi_boot=True and the operating system does not load.

Is there another procedure that I can do?

In the vm disk list, select appropriate boot disk by clicking in the "boot device" column. VM must be powered off. You can try recover boot with a repair cd/dvd of the operational system.

MMSW_DE wrote:

Assuming that what is on the vmdk is actually a valid installation of Windows and all that is missing is the Virtio SCSI driver, I have successfully used the following procedure:

• Deploy Windows Repair ISO (matching the version on vmdk) and VirtIO driver ISO with Image Service
• Assign Windows Repair ISO to VM's CDROM drive
• create a second CDROM for VM and assign VirtIO ISO to it
• Boot from first CDROM
• In Windows Repair Options, load SCSI driver from second CDROM to gain access to Windows volume on virtual disk.
• Launch a DOS-Box.
• Launch diskpart, type list vol and take note of drive letters of Windows drive and driver CDROM. Make sure that Windows partition is flagged active. Exit Diskpart
• In DOS Box enter
• [WindowsDrive]
• :\ /add-driver /Driver:"
• [DriverCDROM]
• (Replace WindowsDrive and DriverCDROM with letters and OS-Version with a path on Driver-CDROM. Note that paths on the VirtIO CD may contain spaces, hence the quotes.
• Example: dism /image:C:\ /add-driver /Driver:"E:\Windows 7\amd64" /recurse
• Eject both CD images from Prism.
• Reboot VM

Thanks @MMSW_DE
That saved our life today!
If we ever meet us on a .Next i need to spend you a beer😉

Another work around is create a new IDE disk cloned from the C drive and boot up the vm from there. It will be slow but allows you to install the virtio drivers. After that just clone the C drive again but using scsi bus (acli vm.disk_create bus=scsi clone_from_vmdisk=), delete IDE drive and the vm will be back to life. This works great for vms with the blue screen error inaccessible boot device.