[SOLVED] TASK ERROR: live-restore failed

jaronski

New Member
Apr 8, 2025
2
0
1
Hi,

I am currently trying to import some of my ESXi VMs to Proxmox.
I am using a CEPH Cluster with three nodes and I've set up the ESXi as a Storage in the Datacenter.
My goal is to be able to migrate all my VMs with minimal downtime from VMware to Proxmox and only use Proxmox instead.

While importing I get - depending if I want to live migrate or not - two different errors:

1. Live migrate

scsi0: successfully created disk 'storage0:vm-100-disk-0,size=16G'
kvm: -drive file.filename=rbd:storage0/vm-100-disk-0:conf=/etc/pve/ceph.conf:id=admin:keyring=/etc/pve/priv/ceph/storage0.keyring,if=none,id=drive-scsi0,format=alloc-track,file.driver=rbd,cache=none,aio=io_uring,file.detect-zeroes=on,backing=drive-scsi0-restore,auto-remove=on: warning: RBD options encoded in the filename as keyvalue pairs is deprecated
restore-scsi0: transferred 0.0 B of 16.0 GiB (0.00%) in 0s
restore-scsi0: Cancelling block job
restore-scsi0: Done.
An error occurred during live-restore: block job (stream) error: restore-scsi0: Input/output error (io-status: ok)

TASK ERROR: live-restore failed

2. Not live migrating
create full clone of drive ([vmdk file])
transferred 0.0 B of 16.0 GiB (0.00%)
qemu-img: error while reading at byte 0: Input/output error
Removing image: 1% complete...
Removing image: 2% complete...
Removing image: 3% complete...
Removing image: 4% complete...
Removing image: 5% complete...
[...]
Removing image: 95% complete...
Removing image: 96% complete...
Removing image: 97% complete...
Removing image: 98% complete...
Removing image: 99% complete...
Removing image: 100% complete...done.
TASK ERROR: unable to create VM 100 - cannot import from '[vmdk file]' - copy failed: command '/usr/bin/qemu-img convert -p -n -f vmdk -O raw /run/pve/import/[vmdk file]'zeroinit:rbd:storage0/vm-100-disk-0:conf=/etc/pve/ceph.conf:id=admin:keyring=/etc/pve/priv/ceph/storage0.keyring'' failed: exit code 1



While searching the web I couldn't really find any information about this problem. One user mentioned it could be caused by not having the permission in the VMware ESXi storage. But I am logged in as the root user, so this shouldn't really be a problem.

Any advice or suggestions would be greatly appreciated.

Thanks in advance for your help!

Jaronski
 
Last edited:
Welcome to the Proxmox forum, Jaronski!

Could it be that the ESXi guests are still running at the time of the migration (either the live migration or the cold migration)?

Currently, the live migration in Proxmox VE for ESXi guests is implemented in such a way, that ESXi guests need to be shutdown before migrating them to Proxmox VE, but will start as soon as possible as the bootdisk is available to start the operating system. Any other hard disks are imported asynchronously in the background, while the VM is already running. See the section about Live-Import here for more details on this [0].

[0] https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE#Live-Import
 
  • Like
Reactions: Lukas Moravek