#1 - See what guests are running
# virsh list
Id Name State
----------------------------------------------------
1 dc1 running
3 cfmc87 running
4 win7c running
#2 - Use the libvirt-guests service to suspend all of them.
# service libvirt-guests stop
Running guests on default URI: dc1, cfmc87, win7c
Suspending guests on default URI...
Suspending dc1: ...
Suspending dc1: done
Suspending cfmc87: ...
Suspending cfmc87: ...
Suspending cfmc87: done
Suspending win7c: ...
error: Failed to save domain bb0d169d-a373-544e-a0f7-99e338673177 state
error: internal error unable to execute QEMU command 'migrate': An undefined error has ocurred
#3 Dealing with troublesome guests
Oops, looks like win7c is being difficult. So let's just force it down.
# virsh shutdown win7c
Domain win7c is being shutdown
# virsh list
Id Name State
----------------------------------------------------
4 win7c running
Even with issuing the shutdown command and waiting a few minutes, the "win7c" guest is still running. So we'll have to "destroy" the instance.
# virsh destroy win7c
Domain win7c destroyed
#4 Checking that all files are released
Now I can use the "lsof" command to verify that there are no open files on the mount point.
# lsof /srv/vms
(returns nothing)
#5 Umount, fsck, resize, fsck, remount
The VM image LV is stored on /dev/md127, inside a LVM thin pool. It's currently 200GB and is about 70% full, so I want to add another 100GB.
# umount /srv/vms
# fsck -f /dev/vg10/vms
# lvextend -L+100G /dev/vg10/vms
# resize2fs /dev/vg10/vms
# fsck -f /dev/vg10/vms
# mount /srv/vms
#6 Restart the guests
# service libvirt-guests restart
# virsh list
And now my /srv/vms filesystem is no longer having space issues.
No comments:
Post a Comment