Disk usage shown by ConnectGetAllDomainStats is incorrect about go-libvirt HOT 3 CLOSED

This is really a question of understanding what the libvirt API does: libvirt virConnectGetAllDomainStats. If you scroll down on that page to the section about "VIR_DOMAIN_STATS_BLOCK" , it describes what each of those fields mean.

None of them are going to be filesystem-aware and some will depend on how the device is being attached (i.e. is it being attached as a virtio device? are unmap operations supported?). The way I read that documentation, physical is probably the closest to what you're looking for, but it's aware of the blocks of the device as a whole and not your internally formatted partition. You might also be running into some oddities with how fallocate is virtualized for your disk in particular... maybe see what happens if you create the file using something like dd with /dev/random as input.

Regardless, this isn't related to go-libvirt, but libvirt itself. Hopefully the above information helps, but you could also try follow up there.

from go-libvirt.

Creating a file with /dev/random data did indeed grow the disk size, it seems fallocate won't cut it in VMs. For anyone that ends up here, the only way I have found of accurately measuring disk space used by a VM from the host is through the virt-df command. It's quite computationally costly, and it's not fast, but it outputs the data correctly.

from go-libvirt.

from go-libvirt.