Dell NativeEdge: Imported Virtual Machine with Multiple Disks Fails to Boot

When importing a VM from VMware vCenter, a VM may fail to boot depending on the VM disk controller configuration.
Errors like "bad scsi device lun: x" or "domain already contains a disk with that address" maybe observed in the libvirt log.

In deployment log an error similar to the log snippet is observed:

2025-12-02T07:16:03.902Z  nativeedge_event Task failed 'nativeedge_plugin.tasks.update_apply' -> Update deployment status is in error state: failed to update vm: internal error: process exited while connecting to monitor: 2025-12-02T07:15:51.465168Z qemu-system-x86_64: -device {"driver":"scsi-hd","bus":"scsi0.0","channel":0,"scsi-id":0,"lun":3,"device_id":"drive-ua-5e7daee5-877b-4365-a9d9-102ba34caa78","drive":"libvirt-2-format","id":"ua-5e7daee5-877b-4365-a9d9-102ba34caa78"}: bad scsi device lun: 3 [retry 1/360]

In Dell Automated Platform 1.0 and 1.1 NativeEdge VMs, we create a single Small Computer System Interface (SCSI) controller following configuration of the main disk, and all SCSI disks are attached to that controller.

However if the VM being imported has multiple disks and multiple SCSI controllers this may affect the VM's ability to boot.

Fix:

This issue is scheduled to be resolved in DAP 1.2 and later.

Workaround:

On the source VM prior to import:

• Install VMware Tools
  • Ensure VMware Tools are installed in the Windows VM. This provides the necessary Paravirtual (PVSCSI) driver.
• Add a Temporary Disk with PVSCSI Controller
  • Power on the VM.
  • In vSphere Client, edit the VM settings.
  • Add a new virtual disk (small size, e.g., 1 GB).
  • When adding the disk, select New SCSI Controller - VMware Paravirtual.
  • Attach the new disk to this new controller.
  • Boot the VM and let Windows detect the new controller and install the driver.
• Verify Driver Installation
  • In Windows, open Device Manager - Storage Controllers
  • Confirm that VMware PVSCSI Controller is listed.
• Shut down the VM
  • Remove the temporary disk (optional).
  • Change the existing SCSI controller for the OS disk from LSI Logic to VMware Paravirtual.
• Power On and Test
  • Boot the VM. It should now use the PVSCSI controller without issues.