GitHub user mbertolina added a comment to the discussion: Not able to deploy
VM: Insufficient un-allocated capacity on StoragePool
Hi @DaanHoogland and @weizhouapache , thanks for your quick response.
I believe the previous points do not apply to this case. I am deploying a VM
with only one ROOT disk, using the following configuration:
Hypervisor: KVM
Disk format: qcow2
Template physical size: 20.81 GB
Template virtual size: 1,912.00 GB
On:
Storage pool: SharedMountPoint
Storage pool disk size: 4,095.5 GB (x1.0)
During the VM deployment, StorageManagerImpl reports the following:
maxSize : (3.9995 TB) 4397514358784
**totalAllocatedSize : (1.8672 TB) 2052994367488**
askingSize : (1.8672 TB) 2052994367488
allocated threshold: 0.85
`2026-09-01 16:08:27,820 DEBUG [c.c.s.StorageManagerImpl]
(API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67)
Checking pool: StoragePool
{"id":38,"name":"wtc2b1f_ds_rp01_01","poolType":"SharedMountPoint","uuid":"b9dec035-9ef1-496f-9285-11eb50dad305"}
for storage allocation, maxSize : (3.9995 TB) 4397514358784,
totalAllocatedSize : (1.8672 TB) 2052994367488, askingSize : (1.8672 TB)
2052994367488, allocated disable threshold: 0.85`
What I don't understand is why StorageManagerImpl is calculating askingSize as
1.8672 TB (2052994367488 bytes) and, at the same time, reporting the same value
for totalAllocatedSize.
This seems inconsistent with the actual physical usage of the storage pool.
Just a few milliseconds earlier, the pool was reporting only ~0.05% physical
usage:
`2026-09-01 16:08:27,803 DEBUG [c.c.s.StorageManagerImpl]
(API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67)
Checking pool StoragePool
{"id":38,"name":"wtc2b1f_ds_rp01_01","poolType":"SharedMountPoint","uuid":"b9dec035-9ef1-496f-9285-11eb50dad305"}
for storage, totalSize: 4397514358784, usedBytes: 2170425344, usedPct:
4.935573069055687E-4, disable threshold: 0.85`
So the main question is:
Why does StorageManagerImpl use 1.8672 TB as both askingSize and
totalAllocatedSize when the storage pool has only ~2.17 GB physically used
(~0.05%) and the VM being deployed has a single ROOT disk? (considering
overprovisioning factor = 1)
I am wondering if this value comes from the template's virtual size (1,912 GB)
rather than its physical size (20.81 GB)?
GitHub link:
https://github.com/apache/cloudstack/discussions/14045#discussioncomment-18268918
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
