An OpenVZ container (102) running in PVE 1.8 was backed up and restored onto another container (102) in PVE 1.9 machine and retained the /etc/vz/conf/102.conf file intact but was very slow to load for the first 2 times.
Another container 104 was created from the same template compiled in dab for PVE 1.9.
The two conf files were compared and the differences were:
102.conf (PVE 1.8)
==============
VMGUARPAGES="262144:9223372036854775807"
OOMGUARPAGES="262144:9223372036854775807"
LOCKEDPAGES="131072:131072"
104.conf (PVE 1.9)
==============
VMGUARPAGES="262144:unlimited"
OOMGUARPAGES="262144:unlimited"
LOCKEDPAGES="131072"
Now when porting it back from PVE 1.9 to PVE 1.8, will the "unlimited" parameter cause any backward-compatible issues?
- Ap.Muthu
Another container 104 was created from the same template compiled in dab for PVE 1.9.
The two conf files were compared and the differences were:
102.conf (PVE 1.8)
==============
VMGUARPAGES="262144:9223372036854775807"
OOMGUARPAGES="262144:9223372036854775807"
LOCKEDPAGES="131072:131072"
104.conf (PVE 1.9)
==============
VMGUARPAGES="262144:unlimited"
OOMGUARPAGES="262144:unlimited"
LOCKEDPAGES="131072"
Now when porting it back from PVE 1.9 to PVE 1.8, will the "unlimited" parameter cause any backward-compatible issues?
- Ap.Muthu