I've been experimenting with OpenMediaVault 0.6 Kralizec installations. First on a debian OS OpenVZ capable and on a second on a CT OpenVZ container also based on Wheezy into the same VM.
Wheezy 7.4 installation was performed into a KVM virtual machine managed by Proxmox VE 3.2. Once this was successfully, Wheezy was particularized to be able to manage OpenVZ technology based on http://www.howtoforge.com/inst…z-on-debian-squeeze-amd64
On this Wheezy VM, we installed Kralizec smoothly, running all OK for now based on http://forums.openmediavault.org/viewtopic.php?f=12&t=514.
On also wheezy container (CT), implemented into VM Wheezy-Kralizec, we have tried to do the same, having several problems with OMV package installation at collectd, apache2 and monit that we have gradually solved at google. At the end, the CT Kralizec´s web interface works, but every time that we stop CT, we lose name resolution. If we set from the webgui any network parameter, we lose the network configuration. If we touch the DNS parameterization OMV go to hang ..... based on http://www.howtoforge.com/how-…y-testing-openvz-template
All this is aimed to provide OMV as an OpenVZ appliance with performances like baremetal, better than as VM and/or expand the possibilities not only extend its functionality via plugins but also by the multitude of ontainers and turnkeys availables online, multiplying the expansion posibilitiess and decreasing development time. A CT does not need more than the intrinsic development, a plugin needs this development plus the plugin itself, apart from a deep understanding of OMV .
For example OpenVPN access server could be installed as a CT instead of a plugin. There is turnkey of OpenVPN http://www.turnkeylinux.org/openvpn . Also for Owncloud http://www.turnkeylinux.org/owncloud and Drupal, OpenPhoto, OpenLDAP, ..