nvme disk devices and mobility agent

Copper Contributor

Hi everyone,

I'm doing some tests regarding the migration of Linux ec2 instances from AWS to Azure,

I have followed the docs for the modernized experience described here but the installation

on the ec2 vms fails because the instalelr cannot find a scsi disk
the error is for example : "AddDiskDiscoveryInfo failed: Error: no attribute found for key scsi_bus"

My undestanding is that the installer expect to find some scsi reference under the linux userspace and since it cannot find it exit with errors.

The vm I'm trying to migrate is based on suse linux 12, the disks of that vm are mapped like this :

 

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
nvme0n1 259:0 0 10G 0 disk
├─nvme0n1p1 259:1 0 2M 0 part
├─nvme0n1p2 259:2 0 20M 0 part /boot/efi
└─nvme0n1p3 259:3 0 10G 0 part /
nvme1n1 259:4 0 1G 0 disk

 

and lsscsi does not return any output, so for modern linux kernels nvme devices and scsi devices are different things, I think that the mobility agent should consider this and have an alternate way to identify disks/partitions  when nvme is found.

1 Reply

note: in older linux kernel there was an nvme <-> scsi "translation"

function , but this has been dropped.

See this post for further information.