Display disk size as GB and not KB/MB
- Thread starter Alyke
- Start date
Yes. You can change that simply to edit your VM configuration.
Code:
nano /etc/pve/qemu-server/129.confAnd change a line like this (for example) to GB -> size=35G
Code:
scsi0: local-lvm:vm-123-disk-1,discard=on,iothread=1,size=35G,ssd=1
Even if there's a decimal value?
From summary it shows 931.51GB
and is the disk 0 from the screen: 976762584K
As for now i don't remember the exact size of the original disk, but can i change in the config and setting like 932GB? Will it still work?
i just tried to create another vm with a decimal disk and it show as KB and not GB, maybe the problem is the decimal value?
Yes exactly, I always make it a bit bigger.
Yes exactly, that's the reason. Just use full GB sizes. e.g. 44GB, 51GB, 2TB, etc.
Hi,
please note that editing the configuration file does not actually change the size of the disk. The value in the configuration is only informational and Proxmox VE will query the actual disk size if required. E.g.
Proxmox VE will display the value as e.g. 932G if it is actually aligned to that size, you can use
please note that editing the configuration file does not actually change the size of the disk. The value in the configuration is only informational and Proxmox VE will query the actual disk size if required. E.g.
qm rescan --vmid <ID> will update the sizes in the configuration to their actual values again. Simply editing the configuration is just lying to yourself Proxmox VE will display the value as e.g. 932G if it is actually aligned to that size, you can use
qm disk resize for that.Can I make a friendly suggestion to have an option in the GUI to change the display size?
I appreciate that KB/MB is more granular but in my opinion it opens users up to user error when performing actions like resizing disks if they have to convert between the two. I also think having to manually change the config file size is both too manual (I assume it also doesn't change if the disk size does, so you're just asking for it to mismatch and cause issues) and too easy to screw up.
For example; just now I wanted to resize a default Ubuntu setup from 3584M to 80GB. I assumed (yes, I know what they say about assuming!
) that the resize option would be in the same format as the displayed size, so I pulled up a converter to work out 80 GB logical as MB, minus 3584, to get to 80 GB. (78,336 if you're curious!) Instead, I created an 80,000 GB disk! Now naturally that wasn't going to work, but since you can't reduce disk sizes, only increase them, I had to restart from scratch. Not a big deal as it was a new VM but rather annoying, and can you imagine if that was a well established VM?
If the display size can be adjusted--and bonus points if you can display it with a rounded and then full size number, e.g.
Anyway thanks for your consideration regardless and for all the help in general in forums and docs. You're appreciated, Proxmox team!
I appreciate that KB/MB is more granular but in my opinion it opens users up to user error when performing actions like resizing disks if they have to convert between the two. I also think having to manually change the config file size is both too manual (I assume it also doesn't change if the disk size does, so you're just asking for it to mismatch and cause issues) and too easy to screw up.
For example; just now I wanted to resize a default Ubuntu setup from 3584M to 80GB. I assumed (yes, I know what they say about assuming!
) that the resize option would be in the same format as the displayed size, so I pulled up a converter to work out 80 GB logical as MB, minus 3584, to get to 80 GB. (78,336 if you're curious!) Instead, I created an 80,000 GB disk! Now naturally that wasn't going to work, but since you can't reduce disk sizes, only increase them, I had to restart from scratch. Not a big deal as it was a new VM but rather annoying, and can you imagine if that was a well established VM?If the display size can be adjusted--and bonus points if you can display it with a rounded and then full size number, e.g.
disk=3.5G (3584.2MB)--then you can comprehend the difference between human numbering and logical, and adjust accordingly. I also just think the displayed size and the increment size must be in parity - or else dumb users like me (I own the title!) will screw it up as above!Anyway thanks for your consideration regardless and for all the help in general in forums and docs. You're appreciated, Proxmox team!
Hi,
IMHO, it would be good to improve the resize dialog to display old and new size and be able to select the increment unit there:
EDIT: opened two issues now:
https://bugzilla.proxmox.com/show_bug.cgi?id=5871
https://bugzilla.proxmox.com/show_bug.cgi?id=5872
feel free to open a feature request on the bugtracker (after checking none exists already): https://bugzilla.proxmox.com/Can I make a friendly suggestion to have an option in the GUI to change the display size?
I appreciate that KB/MB is more granular but in my opinion it opens users up to user error when performing actions like resizing disks if they have to convert between the two. I also think having to manually change the config file size is both too manual (I assume it also doesn't change if the disk size does, so you're just asking for it to mismatch and cause issues) and too easy to screw up.
For example; just now I wanted to resize a default Ubuntu setup from 3584M to 80GB. I assumed (yes, I know what they say about assuming!
If the display size can be adjusted--and bonus points if you can display it with a rounded and then full size number, e.g.disk=3.5G (3584.2MB)--then you can comprehend the difference between human numbering and logical, and adjust accordingly. I also just think the displayed size and the increment size must be in parity - or else dumb users like me (I own the title!) will screw it up as above!
Anyway thanks for your consideration regardless and for all the help in general in forums and docs. You're appreciated, Proxmox team!
IMHO, it would be good to improve the resize dialog to display old and new size and be able to select the increment unit there:
EDIT: opened two issues now:
https://bugzilla.proxmox.com/show_bug.cgi?id=5871
https://bugzilla.proxmox.com/show_bug.cgi?id=5872
Last edited:
Thanks Fiona and apologies for the delay in saying as much!! Help and consideration like this is always greatly appreciated!