Windows drive size is incorrect

[anrutez]

Hello! Help advice!

I needed to migrate Windows Server 2016 from the server to the ProxMox virtual environment. Everything turned out, but the disks in Windows have the wrong size (the size remains from the previous system). Larger than there is on a virtual disk (qcow2).

The qcow2 disk was created with a size of 80Gb, and on Windows it is displayed as 240Gb. I tried to compress the disk using Windows 2016, but swears that the volume of the disk does not allow this (((

Please tell me how to bring the wheels to the correct size!

 

[aaron]

Qcow2 is thin provisioned. This means that only the space that is not zeros is used. How much of the disk is used according to Windows?

Can you show the config of the VM? qm config <VMID> in the CLI for example.

 

[NickDragon]

Hello!
I have exactly the same situation, what should I do? Here is qm config 105:
agent: 1
bios: ovmf
boot: order=scsi0
cores: 8
efidisk0: local-zfs:vm-105-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
machine: pc-i440fx-7.2
memory: 32768
meta: creation-qemu=7.2.0,ctime=1724094992
name: pm
net0: virtio=1E:AB:2F:64:90:9B,bridge=vmbr4,firewall=1
numa: 0
ostype: win11
parent: part2
scsi0: pm:vm-105-disk-0,iothread=1,size=200G
scsi1: pm_base:vm-105-disk-0,iothread=1,size=500G
scsihw: virtio-scsi-single
smbios1: uuid=99923266-c752-4b7b-ab52-a933fe04a204
sockets: 2
tpmstate0: local-zfs:vm-105-disk-1,size=4M,version=v2.0
vmgenid: 4a02187e-a362-4d3f-9cc9-dfc45009089f
The disk was 500 in size, I reduced it to 200, but Windows left 319 GB unallocated and when trying to expand the volume it gives an error: there is not enough free space on the disk to perform this operation. Even if I try to expand it by 1 GB