Dear Qemu & KVM Developers,
1) the praise: thanks for kvm-qemu,
first off the praise:
* kvm-qemu is a high performance nicely scriptable virtualization system
o checkout this hd bench
https://dwaves.de/wp-content/uploads/2021/09/windows-7-32Bit-virtio-drivers-kvm-qemu-crystal-disk-mark-benchmark-Screenshot-at-2021-09.jpg
<https://dwaves.de/wp-content/uploads/2021/09/windows-7-32Bit-virtio-drivers-kvm-qemu-crystal-disk-mark-benchmark-Screenshot-at-2021-09.jpg>
* if it works, it can do pretty things 🙂
* especially like the x11 forwarded virt-manager gui over ssh (yes it
is a bit slow… but simplicity at it’s best)
o https://dwaves.de/wp-content/uploads/2021/09/virt-manager_2021.jpg
<https://dwaves.de/wp-content/uploads/2021/09/virt-manager_2021.jpg>
2) the problem/the critique:
* why is thin provisioning
<https://dwaves.de/2021/08/01/how-to-gnu-linux-thin-provisioning-kvm-virtual-machines-with-virt-manager-bigger-than-physical-virtual-harddisks/>
not the disk-saving default option?
o or at least should be possible for the user to select this
option in virt-manager
* do not drop windows 7 support just yet… many virtualization systems
such as VirtualBox are actually intended to run “outdated” OS on
newer hardware for the sake of getting programs to run, that are
incompatible with recent OS.
something is very wrong with the default settings for windows 7 64bit
ultimate: it is stuck at 0% during setup (as if the harddisk died)
https://dwaves.de/wp-content/uploads/2021/09/kvm-qemu-windows-7-ultimate-64bit-something-wrong-with-disk-access-sata-Screenshot-at-2021-09_2.jpg
<https://dwaves.de/wp-content/uploads/2021/09/kvm-qemu-windows-7-ultimate-64bit-something-wrong-with-disk-access-sata-Screenshot-at-2021-09_2.jpg>
(this was tested and found valid on two different systems using GNU
Linux Debian 10 and 11)
the only workaround that worked so far: go with 32Bit and use virtio as
disk driver system :)
help! :)
& best regards
