ELM won't boot after migrating ELM from VMWare to Nutanix AHV

ELM won't boot after migrating ELM from VMWare to Nutanix AHV

book

Article ID: CTX691281

calendar_today

Updated On:

Description

Migrating ELM from VMWare to Nutanix AHV Hypervisor using the Nutanix Move appliance. After migration the ELM fails to boot entirely and you see the "dracut" prompt on the ELM from the hypervisor console.

Environment

Citrix is not responsible for and does not endorse or accept any responsibility for the contents or your use of these third party Web sites. Citrix is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement by Citrix of the linked Web site. It is your responsibility to take precautions to ensure that whatever Web site you use is free of viruses or other harmful items.

Resolution

The Linux device path mappings on the appliance are using /dev/sdX when deployed on VMware. Nutanix will default to VirtIO PCI devices that use /dev/vdX mappings. The existing LVM logical volume on the appliance will not be able to find the existing physical volumes when this mapping changes. The easiest way to correct that is to remount the OS and repository disks on the ELM as SCSI disks.

Per this chart provided by Nutanix, anything but the PCI disk (VirtIO-pci) should provide /dev/sdX mappings.

  • SCSI disk (scsi.2): /dev/sde (pci-0000:00:04.0-scsi-0:0:2:0)
  • PCI disk (pci.0): /dev/vda (virtio-pci-0000:00:07.0)
  • IDE disk(ide.1): /dev/sdi (pci-0000:00:01.1-ata-1.1)
  • SATA disk (sata.1): /dev/sdg (pci-0000:00:06.0-ata-2.0)
  • Volume group (scsi.1 index 1): /dev/sdc (pci-0000:00:04.0-scsi-0:0:1:1)

Please see here for the source article:
https://portal.nutanix.com/page/documents/kbs/details?targetId=kA00e000000Cv84CAC

 

Please open a support case if alternate methods for migration are needed.


Problem Cause

Linux disk device mappings change depending on the type of interface used.