The recent DAB.pm changes in the git repo reference /etc/pve/openvz folder in the new PVE 3 instead of the original /etc/vz/conf folder in the old PVE 1.9.
Whilst the former folder does not exist in the PVE 1.9, the latter is symlinked to the former in PVE3 and both symlinks point to /etc/pve/nodes/[hostname_of_pve3]/openvz in PVE3.
Hence if OpenVZ templates are compiled for PVE 1.9, it should run in PVE 3 as far as this issue is concerned. However, if the OpenVZ template is compiled in v3.0 with this Git fix, then it may be prudent to create a symlink in PVE 1.9 as /etc/pve/openvz pointing to the actual folder /etc/vz/conf to enable it's usage in PVE 1.9.
Whilst the former folder does not exist in the PVE 1.9, the latter is symlinked to the former in PVE3 and both symlinks point to /etc/pve/nodes/[hostname_of_pve3]/openvz in PVE3.
Hence if OpenVZ templates are compiled for PVE 1.9, it should run in PVE 3 as far as this issue is concerned. However, if the OpenVZ template is compiled in v3.0 with this Git fix, then it may be prudent to create a symlink in PVE 1.9 as /etc/pve/openvz pointing to the actual folder /etc/vz/conf to enable it's usage in PVE 1.9.