[SOLVED] qm disk import from vmdk with lvm shows no partition on destination

[raphr]

Hello community !
We have Installed and configure on new hardware a proxmox cluster with 3 nodes and a Ceph pool with 18 disks.
All seems working as expected.

proxmox 8.2.7 with no-subsctipyion repository

We tried then to migrate some vms from an existing vmware cluster
First method we used was to attach esxi servers as storage and use import wizard. It has worked but slow as hell. Unusable.

Second method was to attach iscsi LUN directly from the vmware storage, mount it readonly with vmfs6-tools and use qm import disk commands.
That was much better transfet rate.

On one VM there is a 150GB disk with lvm volume.
we use this command :

qm disk import VMID file.vmdk Ceph-Volume --format raw

Import finished successfully, then attach the disk to the vm as SCSI1

Problem is that migrated disk doesn't seems to have lvm partition.
After booting the vm in maintenance mode,

fdisk -l /dev/sdb

or

lsblk

shows coorect disk size but no partition.


Any idea ?

Thanks !

 

[raphr]

Hello again,
I have imported with same method another VM containig lvm partitions which works perfectly.
So my first import was a bad example. No luck.

The bogus VM is an old ubuntu system installed in 2012 and upgraded until 18.04 LTS.
Maybe the vmdk is in older format not compatible with qm importdisk ?

Anyway this disk is just a volume for apt-cacher needed for som Debain machines not connected directly to Internet.
So not critical.

I just hope there are no other vms like this.

Regards

 

[alexskysilk]

how certain are you the vmdk is valid?
mount the vmdk locally. inspect.

(you'll need to install libguestfs-tools; after which you can use guestmount.)

 

[raphr]

Hello,
Thanks for suggestion.
Weird thing is that the vm works good on the esxi hosts (version 6.5)

Things I've done on proxmox :

# virt-filesystems -lha mydisk.vmdk
Name  Type  VFS  Label  Size  Parent

The vmdk seems empty

On the esxi host :

# vmkfstools -x check mydisk.vmdk
Disk is error free

no probelm

Then I decided to clone the vmdk

# vmkfstools -i mydisk.vmdk myclonedisk.vmdk -d thin
...

Clone: 100%

Again no problem

I check the new disk on proxmox

# virt-filesystems -lha myclonedisk.vmdk
Name                Type        VFS   Label  Size  Parent
/dev/vg0/apt-cache  filesystem  ext4  -      99G   -
/dev/vg0/lv-var     filesystem  ext4  -      47G   -

This is much better.

To conclude the source vmdk was in a bad state for proxmox but not for esxi.
clone the disk in a new vmdk solved the problem.
This VM was originaly on a vsphere 5.5 (back to Windows and Vsphere client days), could be the reason.

Thanks for help !