ESXi Import fails when using "Live-Import"

MWerler

New Member
Mar 28, 2024
1
0
1
Hi,

I am currently attempting to use the new automatic import interface for importing a Test-VM from VMWare ESXi to Proxmox.
This works very well when using the regular import function, however the "Live-Import" doesn't seem to work. Upon starting the import it creates the VM in proxmox but fails to actually import it;


Logical volume "vm-107-disk-0" created.
scsi0: successfully created disk 'local-lvm:vm-107-disk-0,size=16G'
restore-scsi0: transferred 0.0 B of 16.0 GiB (0.00%) in 0s
restore-scsi0: stream-job finished
restore-drive jobs finished successfully, removing all tracking block devices
An error occurred during live-restore: VM 107 qmp command 'blockdev-del' failed - Node 'drive-scsi0-restore' is busy: node is used as backing hd of '#block217'

TASK ERROR: live-restore failed

This leaves me with a now VM, which is locked and non responsive.
Does anyone know what causes this problem or how I would go about to fixing this.
 
Yes, same problem here. Cold migrate works perfectly but on live migrate :

Rounding up size to full physical extent 4.00 MiB
Logical volume "vm-102-disk-0" created.
transferred 0.0 B of 128.0 KiB (0.00%)
transferred 128.0 KiB of 128.0 KiB (100.00%)
transferred 128.0 KiB of 128.0 KiB (100.00%)
efidisk0: successfully created disk 'serv6-nvme-TP:vm-102-disk-0,size=4M'
Logical volume "vm-102-disk-1" created.
sata1: successfully created disk 'serv6-nvme-TP:vm-102-disk-1,size=40G'
restore-sata1: transferred 0.0 B of 40.0 GiB (0.00%) in 0s
restore-sata1: stream-job finished
restore-drive jobs finished successfully, removing all tracking block devices
An error occurred during live-restore: VM 102 qmp command 'blockdev-del' failed - Node 'drive-sata1-restore' is busy: node is used as backing hd of '#block663'

TASK ERROR: live-restore failed

I also modified on the vmware side these two options at 0 (see screenshot) like indicated in this thread https://forum.proxmox.com/threads/proxmox-8-1-esxi-import-storage-error-500.144049/
 

Attachments

  • Capture d'écran 2024-04-11 093649.png
    Capture d'écran 2024-04-11 093649.png
    18.7 KB · Views: 29
Last edited:
For anyone stumbling upon this thread when searching for a solution.

The source VM on ESXi has to be powered off first before starting the import. In the guide it says "Please note that the VM on the ESXi is still switched off", but that just means you have to switch it off, not that it is powered off by the importer.
 
  • Like
Reactions: PwrBank