dev/vda5 501760 20969471 10233856 8e Linux LVMĭisk /dev/mapper/web-vg-root: 8300 MB, 8300527616 bytesĢ55 heads, 63 sectors/track, 1009 cylinders, total 16211968 sectorsĭisk /dev/mapper/web-vg-root doesn't contain a valid partition tableĭisk /dev/mapper/web-vg-swap_1: 2143 MB, 2143289344 bytesĢ55 heads, 63 sectors/track, 260 cylinders, total 4186112 sectorsĭisk /dev/mapper/web-vg-swap_1 doesn't contain a valid partition tableįrom this output you can see that the virtual drive this machine (called web) is currently installed on is 10GB with about 8GB given to the OS and 2GB to a swap partition. I/O size (minimum/optimal): 512 bytes / 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes On the guest machine you first want to run fdisk to determine the current partition sizes and the over all disk size: $ sudo fdisk -lĭisk /dev/vda: 10.7 GB, 10737418240 bytesġ6 heads, 63 sectors/track, 20805 cylinders, total 20971520 sectors On recent Windows OS’es I believe you can use Disk Management to change partition sizes. This basic resizing procedure should also work for Windows and other guests as well but the last step, where the guest grabs the additional space, will vary from one OS to another. In other words you virtual machines are Linux based and installed on qcow2 disk images.
Qemu img create qcow2 install#
I’m going to assume that you have an install similar to the one I’ve detailed in the Installing and Running KVM on Ubuntu 14.04 series of articles on this site.
Qemu img create qcow2 how to#
This guide shows you step by step how to expand a qcow2 disk image and then how to give the guest the extra space. Combined with the fact that if you are running LVM it’s easy to expand the disk there’s really no excuse for over specifying on the disk at install time. I like to keep my disk images as small as reasonably possible when running virtual machines as I find it just generally makes life easier.
0 kommentar(er)
