This is caused because the user is running as qemu for virt-resize and if qemu does not have privileges to read from the source and write to the destination, it will fail with the below. So either change the uid of qemu or change the ownership of the source and target.
Solution:
export LIBGUESTFS_BACKEND=direct
virt-resize --expand /dev/sda2 /root/kvmtemplates/windows2019-eval-template.img /root/kvmguests/kvmkvmuser4515........
pip install PIL
ERROR: Could not find a version that satisfies the requirement PIL (from versions: none)
ERROR: No matching distribution found for PIL
The import name is PILbut the actual pip package is called "Pillow"
pip install Pillow........
The strange thing is that usually the first install or two will work on any new machine but then it suddenly won't. I had this experience on QEMU 2.13 on a different machine. There is something finicky or buggy about the CUCM installer even when choosing the same virtual hardware specs.
qemu-kvm command:
/usr/libexec/qemu-kvm -version
QEMU PC emulator version 0.12.1 (qemu-kvm-0.12.1.2-2.506.el6_10.1), Copyright (c) 2003-2008 Fabrice Bellard
........
There is no such option as "VBS" that Ican see in vSphere 6.7 Ibelieve this is actually an issue because of using old hardware in this case L5420 doesn't support Nested Virtualization I believe.
Hardware virtualization is selected and cannot be deselected due to selection of VBS
Insufficient resources to satisfy configured failover level for vSphere HA.........
This happens on any file an even just typing "vi"whereas it never happened before. I suspect an update or environment variable is causing this issue
When entering vi I get this weird stuff
line 58:
E488: Trailing characters: t_Sbet
line 63:
E171: Missing :endif
When exiting vi I get this weird stuff
t_Sb=^[[4%?%p1%{1}%=%t........