In summary, if you see "NativeAPI" as the VM Execution Engine, and your VM is flaky, something's not right! Grindlay Posts: 6 Joined: 23. I've searched "NativeAPI" on the forums here but can't see anything related to my problem.
On next VM start, the session information on the Ryzen 3 reported "VT-x/AMD-V" and the crashes/random errors went away. Toggle virtualisation support ON in the BIOS and checked the "Enable Nested VT-x/AMD-V" setting on vbox Toggled virtualisation support OFF in the BIOS and attempted to start the VM (failed) In spite of checking the "Enable Nested VT-x/AMD-V" setting on vbox, the Ryzen 3 VM refused to change from "NativeAPI". On the Ryzen 7 it was reported as "VT-x/AMD-V", on the Ryzen 3 it was "NativeAPI". The same VMs (same original *.vdi files) were running smoothly on the Ryzen 7 machine so I knew something must be wrong with my Ryzen 3 setup.Ĭomparing the settings on the two machines, the only difference was the "VM Execution Engine" as reported by the virtualbox session information tool.
Windows Device Security > Core Isolation was off. I made sure that Hyper-V was off (it was). Initially it was random problems with crashing, Gnome restarting, updates not working properly (failing with authentication errors). Soon after starting the VMs on a new SSD, a variety of problems started. The restored VMs had been running on another machine with a Ryzen 7 CPU without issue.
Then the SSD failed and I had to restore the *vdi files from backup. I created a couple of Linux guest VMs on this windows host and they worked acceptably well for a few weeks. Virtualisation on this MB is off by default and enabled by a setting in the BIOS. I'm posting this in the hope that it will save someone time and effort.ĪMD Ryzen 3 2300X Quad Core CPU on Asus A320M-K MB
0 kommentar(er)
