The really irritating thing is that I have now had the same problem in Manjaro and ArcoLinux.
While Linux installs are done without any hassle; creating Windows VM’s is.
This is gonna be weird, but I smell zen 1 RAM shenanigans. It’s gonna sound weird, but remove half your RAM and try again.
Is it 2x16GB sticks or 4x8GB sticks? Zen 1 sucks at dual rank and quad sticks…
1 Like
Disable memory ballooning to start with ?
<memory unit="KiB">16777216</memory>
<currentMemory unit="KiB">1048576</currentMemory>
It looks like you are trying to install windows with 1GB of ram … it’s not gonna like it …
1 Like
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.
I changed it to 16 GB.
Will do that.
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.
When does it fail? Does the installer even get to the initial welcome/partition choose?
Nobody said you had to leave it out, you’re just doing experiments. It has been fine forever with the address ranges that QEMU doesn’t use lol
I had the world of trouble with my 1600X with bluescreens everywhere when it had two sticks of RAM, had to half them to get them to work.
1 Like
(post deleted by author)
So all I have to do is take one out and then insert them again after a reboot?
It wasn’t undisclosed. AMD stated that with the Ryzen 2xx0 series they fixed the communication bug that slowed down the communication between chips in the 1xx0 series. I remember that.
Nah. I bought the first batch that came to europe. I’m probably affected by a bunch of stuff, but I have never really noticed any of it ever. Since I bought it when they came to the market, I have had maybe 50 Windows Virtual Machines running on my computer. I don’t think it’s the bios updates that I recently did, since it displayed this error a month before I even updated the bios version to the latest. Which gave me the capability to now use every AM4 CPU that has been created, even the newest 5800X3D. I’m so glad I bought this motherboard and not some cheap crap. I have been thinking of either putting in a 5800X3D or a 5950X. The thing is that I do compile stuff from time to time, I also stream and make videos, so having more cores wouldn’t be too bad, and I do set up virtual machines and I would love to max out my computer with 64GB and the biggest CPU possible, in order to also pass through my GPU.
I have been thinking of upgrading my computer and if I can, I will.
Directly. You see the Windows logo, then it bluescreens.
Found this, I have had other problems too, like applications just become black boxes and after a while they load up the information, but it’s like my computer goes snailpace. It started after I installed Arco Linux. While I actually love how this distro works, I have no Idea where the bugs are coming from. Manjaro had the same problem, could it just be Arch not liking my system? I don’t want to reinstall my computer, but to go back to POP!_os is probably not a bad Idea. "/
How do I check the memory? Memtest should be present in grub bootloader right? I should test that maybe.
I took a photo of every page in the Binary I/O System. I’m thinking that the optimised settings seems interesting to use. Could change to that, reboot then get into the bios again and change the svm & iommu stuff.
…and it started with newer versions of the Kernel.
Have you tried using the LTS kernel? Or perhaps an older one from when you were still able to install Windows VMs successfully?
Have you seen this?
1 Like
Take one out, try an install of windows.
I’d also suggest running a memtest for a while to see if there are any holes on your ram. Just speaking from terrible experience with zen 1 and ram. I had a board just like yours
1 Like
Nope. I’m not that good at using linux, that I know how to download an older kernel and then use that instead. With manjaro it would had been easier, since they have a kernel switching application, but I use another fork of Arch now, and it’s a bit limiting. I was using the latest LTS kernel on Manjaro, which means I have to go back even further in order to find out ‘who’ the culprit is.
No. I will check that out. Thanks.
I will try that out tomorrow or something. I’m a bit too tired to fix with this right now.