How to vzmigrate to Proxmox folder rather than /vz folder

[kotakomputer]

When I run vzmigrate from OpenVZ (source file located on /vz) to Proxmox then VM saved to /vz, rather than /var/lib/vz.
How to make vzmigrate migrate the VM to /var/lib/vz ?

 

[dietmar]

create a symlink

 

[kotakomputer]

the problem is vzmigrate create a new /vz folder (and i avoid to use symlink, because I have several machine using CentOS+OpenVZ which use /vz and plan to migrate them to Proxmox) . i read the vzmigrate documentation but i can not found any option to set destination path. maybe time to request new feature to OpenVZ team?

 

[tom]

I do not see a problem with your old centos/openVZ server if you create a symlink on Proxmox VE. why is this a problem?

 

[kotakomputer]

Because there are 2 folders: /vz (symlink) and /var/lib/vz. I want to have 1 path only.

 

[tom]

looks not like a blocker for me. but you can also backup/restore later (after migrations) to have only one path.

 

[kotakomputer]

but you can also backup/restore later (after migrations) to have only one path.

that is the problem. to move it to /var/lib/vz it is not easy for 200 GB VM and there are many hard-links errors I receive when use mv command. using cp/rsync is ok but need twice hdd space.

btw, i just found new bug according to this issue:
- my / partition is 100 GB, my /var/lib/vz is 900 GB
- I do vzmigrate 80 GB VM from centos-openvz and saved to /vz of Proxmox
- I edit Proxmox VM hdd size to 160 GB and no error, but ... when I do #df command, the size still 100 GB (of course because / was 100 GB).
- I guess ... maybe Proxmox check /var/lib/vz partition size rather than actual /vz

 

[dietmar]

Why don't you symlink /vz to /var/lib/vz?

 

[kotakomputer]

Symlink is working fine, but I like to make it simple, that's why I avoid symlink as much as possible. I like to standardize all of my Proxmox machines, this make simplicity for next maintenance and upgrading.