A recent update to Arch Linux replaced the qemu-kvm
package with
an updated version of qemu
. A side effect of this change is that
the qemu-kvm
binary is no longer available, and any libvirt
guests
on your system utilizing that binary will no longer operate. As is
typical with Arch, there is no announcement about this incompatible
change, and queries to #archlinux
will be met with the knowledge,
grace and decorum you would expect of that channel:
Posts for: #Kvm
Growing a filesystem on a virtual disk
Occasionally we will deploy a virtual instance into our KVM infrastructure and realize after the fact that we need more local disk space available. This is the process we use to expand the disk image. This process assumes the following:
- You’re using legacy disk partitions. The process for LVM is similar
and I will describe that in another post (it’s generally identical
except for an additional
pvresize
thrown in andlvextend
in place ofresize2fs
). - The partition you need to resize is the last partition on the disk.
This process will work with either a qcow2
or raw
disk image. For
raw
images you can also run fdisk
on the host, potentially saving
yourself a reboot, but that’s less convenient for qcow2
format
images.