This is a fresh install of Prox 4.3.
Converted .vmdk to qcow2
root@proxie:~# qemu-img convert -f vmdk image-wmps-fireeyenx1500v-disk1.vmdk -O qcow2 image-wmps-fireeyenx1500v-disk1.qcow2
However, any instructions I can find say to copy create a VM (say 104) and and copy the qcow2 image to /var/lib/vz/images/104 but there is nothing in the /var/lib/images directory at all...
My guess is that is has something to do with the way the storage is configured by default in 4.3:
root@proxie:/var/lib/vz/images# 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
The webUI shows that all VM's are being created on local-lvm, but I'n not well versed on what lvmthin is doing.
Thanks for any pointers.
-Steve
Converted .vmdk to qcow2
root@proxie:~# qemu-img convert -f vmdk image-wmps-fireeyenx1500v-disk1.vmdk -O qcow2 image-wmps-fireeyenx1500v-disk1.qcow2
However, any instructions I can find say to copy create a VM (say 104) and and copy the qcow2 image to /var/lib/vz/images/104 but there is nothing in the /var/lib/images directory at all...
My guess is that is has something to do with the way the storage is configured by default in 4.3:
root@proxie:/var/lib/vz/images# 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
The webUI shows that all VM's are being created on local-lvm, but I'n not well versed on what lvmthin is doing.
Thanks for any pointers.
-Steve