I give it topology; 2*2; 100GB space & 16 GB ram.
I have tried ‘Legacy Bios’, ‘UEFI x64’, ‘UEFI SECUREBOOT x64’. The windows manual stated it’s a fix within the system… Within Windows, that you do a secure boot for in order to find what’s wrong.
I have now tried it with bootleged windows ISO’s, and the original from Microsofts own page, both Win10 & Win11. Same results. So I was thinking, maybe it’s QEMU that’s at fault here.
I installed ArcoLinuxXL without a problem, and a bunch of other Linux distro’s. It’s a Windows only problem.
EDIT;
That did not work for me. I’m met with the message that there’s only two options “host-passthrough” or “maximum”… Setting it to Maximum still gave me the same error code.
I did a “sudo chmod 1775 /var/lib/libvirt/images/win10.qcow2” and now it has access to the file… Strange that it wouldn’t have access to it’s own file…
… Woah, I have had 32 GB of ram in the computer for ages, and there hasn’t been any problems at all, this began with a newer kernel or later versions of Linux, I actually use at least 16 GB per session, I rather not go down that road.
Still the same result. It’s a CPU thing, and it started with newer versions of the Kernel. I get it my 1700X is getting old, but did it really have to get into this situation? It started noticing it this year. I haven’t had any problems with it before. Last year I had multiple Windows VM’s.