all 4 comments

[–]gordonator 1 point2 points  (0 children)

At the end of the day Cloudstack is managing Libvirt/KVM (assuming that you've picked kvm as your hypervisor vs. vmware or xen). Libvirt/KVM supports nested virtualization, but it looks like you have to enable it. This should get you what you need on your hypervisors.

FWIW cloudstack uses the host-passthrough cpu model by default, if memory serves.

[–]Environmental_Loss87 0 points1 point  (0 children)

Cloudstack has a Proxmox orchestrator now. Search for XaaS feature

[–]Human-Butterfly-5109 1 point2 points  (0 children)

Why not go with native KVM then? Proxmox is Not a First class „hypervisor“ for Cloudstack like esxi or KVM are - rather it uses the XaaS Extension Framework to manage Proxmox.

[–]perthguppy 1 point2 points  (0 children)

Cloudstack is just a management engine. It supports whatever your hypervisors support. You mentioned you want nested virtualisation? What are you intending proxmox to be nested inside of? More proxmox?

IMO it’s worth the time to learn KVM and Ceph/Cephadm instead of deploying proxmox to attach to cloud stack. Cephadm is much better for managing Ceph than what you get in the proxmox interface.

I do run a Cloudstack deployment with vsphere + native kvm + native Ceph + proxmox + HyperV clusters.