264
« on: February 17, 2021, 06:26:21 pm »
I've seen that with Tiger updates. I think there is some glitch or inefficiency with supervisor level code (which makes sense with KVM-PR). I've had the best luck doing installs with TCG instead of KVM, which is most reliable, and then switching back.
Also note right now that as long as we advertise to the OS as a G4/7410, it will select the wrong dcbz size, which has memory impacts. I have code to monkeypatch the operating system but this is not suitable for mainline KVM. We could monkeypatch the kernel permanently in the disk image but this would have to be after all your updates are done.
The definitive solution is to advertise to the OS we're a G5, and then the right cache line size is used. However, this locks up the computer right now ...