The best and first place to consult when you are having an issue with options is the "man page".
"man qm" gives us the following for "qm disk resize" (for which "qm resize" is an alias):
Code:
qm disk resize <vmid> <disk> <size> [OPTIONS]
Extend volume size.
<vmid>: <integer> (1 - N)
The (unique) ID of the VM.
<disk>: <efidisk0 | ide0 | ide1 | ide2 | ide3 | sata0 | sata1 | sata2 | sata3 | sata4 | sata5 | scsi0 | scsi1 | scsi10 | scsi11 | scsi12 | scsi13 | scsi14 | scsi15 | scsi16 | scsi17 | scsi18 |
scsi19 | scsi2 | scsi20 | scsi21 | scsi22 | scsi23 | scsi24 | scsi25 | scsi26 | scsi27 | scsi28 | scsi29 | scsi3 | scsi30 | scsi4 | scsi5 | scsi6 | scsi7 | scsi8 | scsi9 | tpmstate0 | virtio0 |
virtio1 | virtio10 | virtio11 | virtio12 | virtio13 | virtio14 | virtio15 | virtio2 | virtio3 | virtio4 | virtio5 | virtio6 | virtio7 | virtio8 | virtio9>
The disk you want to resize.
<size>: \+?\d+(\.\d+)?[KMGT]?
The new size. With the + sign the value is added to the actual size of the volume and without it, the value is taken as an absolute one. Shrinking disk size is not supported.
--digest <string>
Prevent changes if current configuration file has different SHA1 digest. This can be used to prevent concurrent modifications.
--skiplock <boolean>
Ignore locks - only root is allowed to use this option.
as you can see it specifically calls out "Extend" and mentions nothing of reduce.
Disk reduction operation is generally much more complex than extension. It involves reducing file system allocation, partitions, etc. A lot has to be done as prep-work in the VM. In short - it cant be easily expressed in single command of a hypervisor. Too many things can go wrong.
A google search should give you many references to manual disk reduction, your VM OS and layout play a big role in this procedure, and sometimes it is simply not possible.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox