#Qemu img resize free

That's it! Now you can either create new partitions or resize existing ones. I/O size (minimum/optimal): 512 bytes / 512 bytesĭevice Boot Start End Sectors Size Id Type Warning: Never use qemu-img to modify images in use by a running virtual machine or any other process this may destroy the image. It can handle all image formats supported by QEMU. Sector size (logical/physical): 512 bytes / 512 bytes Description qemu-img allows you to create, convert and modify images offline. Login to the machine and check that actual size was changed: fdisk -lĭisk /dev/vda: 100 GiB, 107374182400 bytes, 209715200 sectors The 100G is the resulting size of the drive we want to have img extension and drive- was added to disk alias. Now we actually resize the drive using qemu monitor: virsh qemu-monitor-command test block_resize drive-virtio-disk0 100G -hmp To this name, you need to prepend drive- to get qemu drive name. For me file name is test.img and alias name is virtio-disk0. You should look for source and alias blocks.

I've found a working way here:įind out a file name and KVM device name of the hard drive you want to resize: virsh dumpxml test | xpath -e /domain/devices/disk I know that's an old question but I've found it while googling for the solution and hope it may help someone else.Īs for today it is possible to resize the hard drive on the machine. XEN I believe has the same limitations currently. Note: There is a difference in the notation between increasing and shrinking disk. If you boot your virtual machine, you will see that the disk has been reduced accordingly.

#Qemu img resize free

But this thin provisioning could be a problem though if you do this to 1000 machines and everyone takes you up on the free space that they see. qemu-img resize -5GB Click to enlarge.

This would at least keep the number of virtual drives/images that you're having to manage. So you could give each machine a small drive for the OS and a large sparse image for data under LVM. But the Qemu forum would be a good place to ask this question if you don't get any solid answers here.Īnother option which may not be ideal is to use really large qcow2 or other sparse image format for the drives. Here's a good how-to resize the various formats that Qemu/KVM support. Then boot another Linux to resize this filesystem offline.

KVM is based on QEMU so all it's image format support comes from that project. rootOpenWrt:/mnt resize2fs /dev/sda2 resize2fs 1.44.5 (1) Filesystem at /dev/sda2 is mounted on / on-line resizing required olddescblocks 1, newdescblocks 7 resize2fs: Invalid argument While checking for on-line resizing support. Why not just give the virtual machines LUNs right off the SAN and manage the space there? This works better if you want to use features like live migration anyhow. I think you're stuck doing what you've mentioned if you want to do it without taking the machine down.