I’ve been running a few VMs on Proxmox, including a Pfsense VM, for over a year without a single issue. This evening, however, I noticed that I wasn’t able to access any local DNS records due to the VM hosting DNS server was not responding. On checking the Proxmox console, I could see that that VM with ID 102 was definitely not responding. So, I tried to reboot, stop and even reset....
I’m quite sure I’d resized qcow2 images before. However, when I needed to resize an image today for my VM at home, I totally forgot about it. Well, this means it’s a good excuse for me to just write down a few commands to help me in the future. If you try to follow a long, two things you wanna keep in in mind: do it at your own risk, and always backup your data before you make change to it....
Again, just a quick note to remind myself how to attach a disk to a VM guest from the command line. The following steps is based on these assumptions: A spare disk: an LVM volume name db2_data on data volume group The name/domain of the VM is db2 List the name of the VM guest and available logical volume. [root@mathvm5 ~]# virsh list | grep db2 20 db2 running [root@mathvm5 ~]# lvs | grep db2 db2 vm -wi-ao---- 80....
Today, one of my VMs needs to have its disk increased. I’m using qcow2 as the VM’s storage. Here is one way to expand the storage that it’s been proven to work very well for me. I already increased this VM’s disk to 30GiB once already, but it wasn’t enough. So here, let’s explode it to 50GiB. The name of the qcow2 file is hosta.qcow2. A friendly reminder that you should alway shave a backup before you perform any critical change such as this one....
Again this is a quick note to explain myself how to set a kvm (domain/vm) autostart when the server boots up. To list autostart domains: virsh list --autostart To set a domian, e.g. dhcp1, to autostart: virsh autostart dhcp1 To disable autostart for a domain (e.g. named dhcp1): virsh autostart dhcp1 --disable Ref: KVM: Start a Virtual Machine / Guest At Boot Time
vdi file is a type of disk image used by VirtualBox. qcow2, on the other hand, is the format of disk image used by KVM. Recently, I want to move some existing virtual machines running on VirtualBox to KVM. To do that I need to convert the disk image from vdi to qcow2. Here’s one way to achieve that: Ref: How to convert VirtualBox vid to KVM qcow2