Hi,
yes, I know this is not supported yet, but I guess after seeing this there needs to be some migration-tool anyways
I simply took a small debian lenny (5.0.9) openvz-VPS and migrated it from a V1.9 PVE system to the current beta.
the VPS itself is running fine, but the PVE2.0 GUI is really challenged:
it sees 36028797018963970 MB RAM
manually setting the values for RAM corrects the whole vz.conf-file and everything keeps working fine and it is also fine to see RAM and SWAP within the VPS!
IPv6 also working - yeah!
It is only a cosmetic problem, but I suggest to plan for some vz.conf-migration-setting to not have to fix all VPS'es manually.
Regards,
hk
yes, I know this is not supported yet, but I guess after seeing this there needs to be some migration-tool anyways
I simply took a small debian lenny (5.0.9) openvz-VPS and migrated it from a V1.9 PVE system to the current beta.
the VPS itself is running fine, but the PVE2.0 GUI is really challenged:
it sees 36028797018963970 MB RAM
manually setting the values for RAM corrects the whole vz.conf-file and everything keeps working fine and it is also fine to see RAM and SWAP within the VPS!
IPv6 also working - yeah!
It is only a cosmetic problem, but I suggest to plan for some vz.conf-migration-setting to not have to fix all VPS'es manually.
Regards,
hk
Last edited: