Repository navigation
CloudStack always uses local-lvm on Proxmox instead of shared storage #12163
Description
problem
We have installed the latest CloudStack version 4.22 in our test environment, and we are using Proxmox as the hypervisor. The issue we are facing is that when we create a VM from CloudStack, it is being created on Proxmox’s local-lvm storage, even though we have shared storage attached to Proxmox. According to the documentation, when setting up Proxmox with CloudStack, we create a cluster and add the hypervisors into that cluster, and then enter the key-value details—but nowhere in the process do we define or specify which storage CloudStack should use.
versions
CloudStack: 4.22
Hypervisor: Proxmox VE 8.x
Storage Type: (Shared Storage)
Nodes in cluster: 2
Using Proxmox with CloudStack extension
The steps to reproduce the bug
...
What to do about it?
No response
Activity
boring-cyborg commentedon Nov 28, 2025
Thanks for opening your first issue here! Be sure to follow the issue template!
weizhouapache commentedon Nov 28, 2025
@Asadsid121
choosing storage pool is not supported as of now.
however, you can update the script on the management servers for customizations. it is flexible.
/usr/share/cloudstack-management/extensions/Proxmox/proxmox.sh
you can add more methods and register them as custom actions in cloudstack.
if there are mutiple management servers, sync the script on all mgmt servers.
shwstppr commentedon Dec 3, 2025
Fixed by #12174