Problem with resize disk

[Mouse]

Hello all,

i have problem with disk resize.

I try to change size in Proxmox, but show size in virtual machine not showing.

But if I try qemu-img info vm-100-disk-1.qcow2 i have this result:

image: vm-100-disk-1.qcow2
file format: qcow2
virtual-size: 491G (527207235584 bytes)
disk size: 161G
cluster_size: 65536
Format specific information:
compat: 1.1
lazy refcounts: false

What is virtual size? This as I tried to adjust the size, I increased the size of the virtual disk more than really has.

I need this:
virtual size: 250G
disk size: 250G

Can you help me wih this problem?
Thank you in advance.
ps. Debian wheezy (updated)

 

[udo]

Hi,
if you increase an disk, the VM will only reconise that:

a. after stop and start again the VM. So that the VM-bios see the bigger disk

b. if you has enable hotplug in the vm-config and your VM-OS support hotplug, you see the bigger disk directly in the VM.

In both cases you need to expand the disk (partition mapping) inside the VM to use the whole space.

Udo

 

[Martin Cleaver]

It would be nice for newbies if there was a way to automatically expand the partition to the size of the disk, or at least a simple one command (vs pv, vg, l something or other sequence described on the wiki). Im thinking REST end point plus access via the UI. I'm sure the pros don't need such a thing but it'd help uptake.

 

[starkruzr]

I've tried editing the Wiki a little for clarity, but I agree it could stand with some more streamlining.

 

[pirateghost]

It would be nice for newbies if there was a way to automatically expand the partition to the size of the disk, or at least a simple one command (vs pv, vg, l something or other sequence described on the wiki). Im thinking REST end point plus access via the UI. I'm sure the pros don't need such a thing but it'd help uptake.

Considering the vast options available for the guest OS, this would be impossible for ProxMox to deal with.
What if my guest OS is windows? How do you expect ProxMox to resize that? What if I don't use LVM in my guest? The hypervisor should merely present the disk to the OS and the OS should handle everything after that. This is the responsibility of the admin to know how to handle these things, not for the hypervisor to guess what I want.

 

[Martin Cleaver]

Naturally the UI won't be able to handle every eventuality but it could help with a few common ones. In the event the disk type isn't handled, I think PVE's UI would simply lead to the how-to on the wiki.

 

[pirateghost]

Naturally the UI won't be able to handle every eventuality but it could help with a few common ones. In the event the disk type isn't handled, I think PVE's UI would simply lead to the how-to on the wiki.

But how do you expect proxmox to know what kind of filesystem you have in your guest?
Even with the host asking the admin, the admin should understand what kind of filesystems the VMS have. You make it sound like the admin doesn't know these things.

There isn't a hypervisor out there that handles your guest OS disks/filesystem