We use both features, but I would keep 2 separate flavors of proxmox if that's the only way of having the most up to date of both worlds.
In any case, we need the most recent version of kvm possible, we'd better have that tan openvpz. You can always have proxmox on a KVM VM inside proxmox.
My vote is, keep up with KVM if I have to choose. The good thing of proxmox in not only it has OpenVZ AND KVM. KVZ is the only solution (OSS or comercial) that supports 16 vcpus, nor xen nor vmware do that on a windows guest, and we need that feature plus the option to assign cores to guest as logical cores, not sockets. That's what we are waiting to see in KVM in proxmox soon.
In any case, we need the most recent version of kvm possible, we'd better have that tan openvpz. You can always have proxmox on a KVM VM inside proxmox.
My vote is, keep up with KVM if I have to choose. The good thing of proxmox in not only it has OpenVZ AND KVM. KVZ is the only solution (OSS or comercial) that supports 16 vcpus, nor xen nor vmware do that on a windows guest, and we need that feature plus the option to assign cores to guest as logical cores, not sockets. That's what we are waiting to see in KVM in proxmox soon.