mpack wrote:birdie wrote:It's great your CPU still works.
(1) I've never had a problem with any CPU I've used on any PC since 2008. It's just a matter of setting up the guest correctly.
(2) You didn't say above you had a problem with Ryzen, you said all of those guests had a problem with HW virtualization on modern CPUs. Perhaps you should make up your mind.
Before opening such tickets, please do some due diligence first. Google for "windows 98 ryzen crash" and you will see that this is not a problem with VirtualBox, it's a problem with Ryzen CPUs and Windows 9x, or more likely a bug in Windows 9x. See e.g. here https://communities.vmware.com/thread/579537
I believe this blog post explains what the problem is. The method Windows 9x uses to manage page tables does not work (reliably) on AMD Bulldozer and Ryzen CPUs, and it probably only works by accident on other CPUs.
Disabling the I/O APIC of course does nothing, Windows 9x does not use it. But disabling nested paging does a lot, because it hides the TLB management problem referenced above.
Please note that Windows 9x is known to have serious problems on fast CPUs.
Also note that the first generation Ryzens had a bug related to VME (Virtual-8086 Mode Extensions) but VirtualBox works around that and AMD fixed that a long ago.
You can complain to AMD but they will very likely tell you that this is a bug in Win9x that they have no desire working around. Intel has done such things too, various old operating systems no longer work on current Intel CPUs because they did things that they shouldn't have done, and they're no longer commercially important.
The bottom line is that this is not a regression and it's not something VirtualBox can fix. Disabling nested paging may help but Windows 9x still remains an unsupported guest OS in VirtualBox.
Users browsing this forum: premax and 17 guests