VM Location

[addy]

Where are the VMs created on Proxmox are located? As per the link below :
https://pve.proxmox.com/wiki/Storage:_Directory

It should be under
var/lib/vz/images/<VMID>

But I have nothing inside images, eventhough I have 2 VMs on my proxmox. My aim is to push the .raw file into the placeholder which I created for migrating a VMDK.

Thanks in advance.

 

[wolfgang]

Hi,

the default "local" storage is located under /var/lib/vz/images/<VMID>
but "local-lvm" is no dir storage it is a thin-lvm.

 

[addy]

SO in that case where should I go to push my converted VM that I brought from VMWARE? I followed all the steps from the wiki page and used the QEMU to covert the Image. I have also created the placeholder for the new VM on the GUI. And since there is nothing under images I am not sure where to move that VM to access it via proxmox.

 

[wolfgang]

Please send the following output

lsblk
cat /etc/pve/storage.cfg

 

[addy]

Please send the following output

lsblk
cat /etc/pve/storage.cfg

root@proxmox:~# cat /etc/pve/storage.cfg
dir: local
path /var/lib/vz
content iso,vztmpl,backup

lvmthin: local-lvm
thinpool data
vgname pve
content rootdir,images

 

[wolfgang]

I do not see the output of

lsblk

 

[addy]

root@proxmox:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931.5G 0 disk
├─sda1 8:1 0 1M 0 part
├─sda2 8:2 0 256M 0 part /boot/efi
└─sda3 8:3 0 931.3G 0 part
├─pve-swap 253:0 0 8G 0 lvm [SWAP]
├─pve-root 253:1 0 96G 0 lvm /
├─pve-data_tmeta 253:2 0 8.1G 0 lvm
│ └─pve-data-tpool 253:4 0 795G 0 lvm
│ ├─pve-data 253:5 0 795G 0 lvm
│ ├─pve-vm--100--disk--1 253:6 0 100G 0 lvm
│ └─pve-vm--101--disk--1 253:7 0 60G 0 lvm
└─pve-data_tdata 253:3 0 795G 0 lvm
└─pve-data-tpool 253:4 0 795G 0 lvm
├─pve-data 253:5 0 795G 0 lvm
├─pve-vm--100--disk--1 253:6 0 100G 0 lvm
└─pve-vm--101--disk--1 253:7 0 60G 0 lvm
nvme0n1 259:0 0 953.9G 0 disk
├─nvme0n1p1 259:1 0 400M 0 part
├─nvme0n1p2 259:2 0 100M 0 part
├─nvme0n1p3 259:3 0 128M 0 part
├─nvme0n1p4 259:4 0 952.3G 0 part
└─nvme0n1p5 259:5 0 977M 0 part

 

[wolfgang]

As you see the disk of the two VM are shown in the output of lsblk.
This are lv on a thin-lvm. You can tread them like a normal block device.
path to this device are "/dev/mapper/pve-vm--100--disk--1"
You can convert the vmdk direct with

qemu-img convert -f vmdk -O raw <path to vmdk>  <path to lv>

fore this method you lv must have the same size or bigger than the vmdk.

The other method is to use the importdisk command.

qm importdisk 100  <path to vmdk> local-lvm

after this command, you see the disk in your VM config.

 

[addy]

Thank you for the help. I did run the command as u said :
I ran the
1) Ran File:Mergeide.zip.
2)"C:\Program Files\VMware\VMware Server\vmware-vdiskmanager" -r win2003.vmdk -t 0 win2003-pve.vmdk
3) Created a placeholder on proxmox with the same configuration
3)Moved the file to the proxmox machine
4)qemu-img convert -f vmdk -O raw win2016.vmdk /dev/mapper/pve-vm--102--disk--1

But now once I try to start the VM it says nothing to boot. ( PFA)

 

[ColeTrain]

As you see the disk of the two VM are shown in the output of lsblk.
This are lv on a thin-lvm. You can tread them like a normal block device.
path to this device are "/dev/mapper/pve-vm--100--disk--1"
You can convert the vmdk direct with

qemu-img convert -f vmdk -O raw <path to vmdk>  <path to lv>

fore this method you lv must have the same size or bigger than the vmdk.

The other method is to use the importdisk command.

qm importdisk 100  <path to vmdk> local-lvm

after this command, you see the disk in your VM config.

you may have retired, but 6 years later, you are still helping people!