Where are the images of virtual machines on Proxmox?

Question

Backup

Good afternoon. I got a server under the state contract from a supplier with virtual machines on proxmox.
In the admin panel, I see 2 storages created:
local, type Directory, content backup
iso and pve type LVM, content images.
There are 2 parallel tasks:
1- I want to transfer virtual machines from proxmox to vmware, I can’t find where on the server the machine images are in raw format, so that I can convert it to vmware format.
2 - I want to transfer virtual machines to another server, I installed proxmox on it, copied backup images to the /var/lib/vz/dump folder, I don’t see them in the admin panel. How can I restore them on a new server?

Answer 1

1) /var/lib/vz/images/ , unless otherwise specified, you can generally look through the web face Datacenter-Storage. There may not be a RAW format, all machines may be in a more modern qcow2, then we will first convert to raw, then to vmware.
2) You did not specify that the backups should be there, go to the Datacenter-Storage, open it for local change, select the ...backup... field there.
PS I understand that you have already seen the price for vmware, agreed with the management and it is ready to pay a lot of money for your inability to use open source tools, Proxmox is no worse in even hands, and in a situation where many containers are even better than vmware products, what is the point of switching if everything works anyway?

Answer 2

1) I looked at /var/lib/vz/ via mc, there is no images folder.
In the web muzzle, there is such a setting:
2) Thank you, I missed this mark. I restored the virtual machine on the new Proxmox VE 3.4 server, before that the virtual machine was spinning on the older Proxmox 2.6.32.-16.
When starting the restored virtual machine, an error occurs:

kvm: -drive file=/var/lib/vz/images/102/vm-102-disk-1.raw,if=none,id=drive-virtio0,format=raw,aio=native,cache=none,detect-zeroes=on: file system may not support O_DIRECT
kvm: -drive file=/var/lib/vz/images/102/vm-102-disk-1.raw,if=none,id=drive-virtio0,format=raw,aio=native,cache=none,detect-zeroes=on: could not open disk image /var/lib/vz/images/102/vm-102-disk-1.raw: Could not open '/var/lib/vz/images/102/vm-102-disk-1.raw': Invalid argument
TASK ERROR: start failed: command '/usr/bin/kvm -id 102 -chardev 'socket,id=qmp,path=/var/run/qemu-server/102.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/102.vnc,x509,password -pidfile /var/run/qemu-server/102.pid -daemonize -name IPA-CentOS-6.3-x64 -smp '2,sockets=1,cores=2,maxcpus=2' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga cirrus -cpu kvm64,+lahf_lm,+x2apic,+sep -m 4096 -k en-us -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:2abbc53a20a0' -drive 'file=/var/lib/vz/images/102/vm-102-disk-1.raw,if=none,id=drive-virtio0,format=raw,aio=native,cache=none,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap102i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'rtl8139,mac=6E:0D:E8:9B:99:16,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'' failed: exit code 1

I can't figure out what he's complaining about.
PS Looked at prices vmware. I just started doing visualization, and I still don't know what to choose.
And another question, when I add an LVM partition to proxmox, the "Partition group" field is empty, where should I fill it?

Answer 3

You have written that 'Could not open '/var/lib/vz/images/102/vm-102-disk-1.raw'
means it is not there. This prevents the VM from starting.
I doubt that it will be better / more convenient / more productive on VMWARE, especially considering its cost.