migration from esxi to proxmox: disk is not recognized

Hello,

How did you go with this? I'm trying the same procedure but am finding that the filesystem of my VM is in a very damaged (beyond repair) state. Attempts to run fsck on the disk end up crashing the VM!

I have tried the OVF tool method as per the article OP linked, and I've also tried using the vmdk from ESXi and running:

Bash:
qemu-img convert -p -O qcow2 myVM.vmdk  myVM.qcow2

qm create 201  --name myVM  \
    --sockets 1 --cores 2 --vcpus 2 --cpu host \
    --memory 2048 \
    --ostype l26 --arch x86_64 \
    --agent enabled=1 \
    --scsihw virtio-scsi-pci \
    --bootdisk scsi0 \
  
qm importdisk 201 /path/to/image/myVM.qcow2 local-lvm --format=qcow2
qm set 201 --scsi0 local-lvm:vm-120-disk-0


Both the OVF Tool method AND the VMDK (qemu-img convert) method land at the same BusyBox / fsck error.

I'm hoping to avoid building the VMs from scratch.
 

Attachments

  • BusyBoxDump.png
    BusyBoxDump.png
    36.1 KB · Views: 7

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!