[Feature Request] - Support for XCP-ng as AutoScaling provider

[0lini]

Existing Resources

• [x] Please search the existing issues for related items
• [x] Consult the product documentation : Docs
• [x] Consult the FAQ : FAQ
• [x] Consult the Troubleshooting Guide : Guide
• [x] Reviewed existing training videos: Youtube

Is your feature request related to a problem? Please describe. We are currently using XCP-ng as our primary hypervisor platform. However, Kasm Workspaces does not support XCP-ng as an AutoScale provider, which limits our ability to efficiently scale resources in our environment.

Describe the solution you'd like Add native support for XCP-ng as an AutoScale provider in Kasm Workspaces. Ideally, this would include:

• Discovery and management of VMs via Xen Orchestra API or XCP-ng API
• Support for VM templating, cloning, and lifecycle operations
• Ability to scale workspaces dynamically based on load and user demand
• Compatibility with existing AutoScale settings and policies in Kasm

Describe alternatives you've considered

• Manually provisioning VMs and registering them with Kasm – labor-intensive and not scalable.
• Using intermediate platforms like Proxmox or VMware – introduces unnecessary complexity and cost.

Additional context XCP-ng is a widely used, open-source virtualization platform with an active community and robust API access through Xen Orchestra. Adding support for XCP-ng would broaden Kasm’s compatibility and make it more appealing to infrastructure teams using open-source stacks.