Timed out waiting for device after migrate VM Hyper-v to Proxmox 7.3-3

[matfinch]

Hello,
I have problem when I will running VM migrate from Hyper-V (MS 2012) to Proxmox 7.3-3. My error "Timed out waiting for device dev-mapper-ol\x2dswap.device"
VM MS 2012 is Generation 2

I greatly appreciate any suggestions on fixing this problem.

Thanks in advance

 

[fiona]

Hi,
is the error within the VM? Can you check if the relevant virtual disk is selected when you go to the VM's Options tab in the UI and click on Boot Order (only those devices will be visible to the VM during early boot)? What is the output of

pvs
vgs
lvs

 

[matfinch]

Hi,
yes this is the VM. On Boot Order I have selected boot disk. I can't execute pvs, vgs and lvs in dracut console.

I executed in source VM:

# pvs
  PV         VG Fmt  Attr PSize   PFree
  /dev/sda3  ol lvm2 a--  158,41g    0
# vgs
  VG #PV #LV #SN Attr   VSize   VFree
  ol   1   9   0 wz--n- 158,41g    0
# lvs
  LV     VG Attr       LSize  Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  backup ol -wi-ao---- 40,00g                                                   
  home   ol -wi-ao----  3,55g                                                   
  opt    ol -wi-ao---- 80,00g                                                   
  root   ol -wi-ao---- 10,00g                                                   
  swap   ol -wi-ao---- <3,86g                                                   
  tmp    ol -wi-ao----  5,00g                                                   
  usr    ol -wi-ao----  6,00g                                                   
  var    ol -wi-ao----  6,00g                                                   
  varlog ol -wi-ao----  4,00g

I attach screen with journal -b. I don't see mount disk.

 

[fiona]

Hi,
yes this is the VM. On Boot Order I have selected boot disk. I can't execute pvs, vgs and lvs in dracut console.

I executed in source VM:

# pvs
  PV         VG Fmt  Attr PSize   PFree
  /dev/sda3  ol lvm2 a--  158,41g    0
# vgs
  VG #PV #LV #SN Attr   VSize   VFree
  ol   1   9   0 wz--n- 158,41g    0
# lvs
  LV     VG Attr       LSize  Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  backup ol -wi-ao---- 40,00g                                                  
  home   ol -wi-ao----  3,55g                                                  
  opt    ol -wi-ao---- 80,00g                                                  
  root   ol -wi-ao---- 10,00g                                                  
  swap   ol -wi-ao---- <3,86g                                                  
  tmp    ol -wi-ao----  5,00g                                                  
  usr    ol -wi-ao----  6,00g                                                  
  var    ol -wi-ao----  6,00g                                                  
  varlog ol -wi-ao----  4,00g

I attach screen with journal -b. I don't see mount disk.

So the ol/swap LV is on /dev/sda3 and I assume that's the disk selected in the boot order, so I don't know why it doesn't get found. IIUC, the failing service is a "resume from hibernate"-service. You could try to migrate the VM when it's fully shut down and see if that works?

 

[matfinch]

I created new VM with one disk and only ol/root LV. I fully shut down and unfortunately the same error

 

[fiona]

I created new VM with one disk and only ol/root LV. I fully shut down and unfortunately the same error

Are you sure it didn't hibernate, because why would it want to resume from hibernation otherwise? And it tries to activate ol/swap even though that never existed in the new VM?

Or do you mean you only exported/copied ol/root from the existing VM on Hyper-V to a new disk?

 

[matfinch]

I'm sure that it didn't hibernate. When I import the same disk for another Hyper-V it's work.

 

[matfinch]

I upgrade OS OL8 to OL9 and I have the same problem.

 

[fabian]

likely the disk topology/slots are different. I'd boot a live CD and see if the PVs/VGs/LVs are visible there. if they are, the fastest way to correct the issue is probably to regenerate the initrd - how exactly that works depends on the distro (I guess ol stands for oracle linux?)

edit: else, please post both the config of the original VM and the "migrated" one..

 

[toomanylogins]

I have migrated many server 2012 2016 from Hyper V to PVE. I do as follows works every time.
1. Shut down hyper v vm.
2. Convert hyper v disks with starwind converter I use qcow2 as pve format
3. create new pve vm with empty sata disk
4. upload new qcow2 image to pve server replacing the empty pve image see /mnt/pve/dev-xxx/images/num of vm
5. Start the new vm and update scsi drivers with virtio then rebott and change to virtio check boot order.

Once you have a functioning server you can move disk to new storage lvm etc. I have tried all methods qm import etc and this works every time. Make sure you choose sata for first boot to avoid windows activation