It seems like there are so many ways this whole concept could go wrong.
http://www.virtualizor.com/wiki/Multi_Virtualization
http://www.virtualizor.com/wiki/Multi_Virtualization
This has been enabled in Proxmox for years.It seems like there are so many ways this whole concept could go wrong.
http://www.virtualizor.com/wiki/Multi_Virtualization
I think you may be misunderstanding this, I do not read this as running KVM inside OpenVZ, but running OpenVZ+KVM on the same node is my takeaway from reading the wiki page. Virtualizor already has KVM nesting if you choose to enable the feature, and I do agree, why would anyone run KVM inside OpenVZ containers, yet, I have seen users run qemu in their OpenVZ container, my guess is to run Windows.Ah, I'm not much of a Proxmox user, so I wasn't aware of that.
What makes no sense to me, is who the hell in their right mind would try and run KVM from an OpenVZ container? That's just .... stupid, and I doubt either vendor would support anything about it, There are some legitimate reasons (usually HA deployments as I'm sure you're aware) for running containers inside KVM. That's how I do all my QA now. Done properly and not as a cheap overselling trick split 20 ways, and nothing incredibly mission-critical, I see nothing horribly wrong with a "slab" so long as it does what it's supposed to... But again, what the shit is with KVM inside OpenVZ? Who would even....? Is there something beneficial to having that as an ability? I didn't think it was technically possible... :/ Who knows, maybe there is and I've been hanging with containers too long to notice, but it seems like you'd be in overhead city with a setup like that.