Next Steps, Oracle has resolved this issue in VirtualBox 6.1.28 and later versions. ![]() Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the upgrade to Windows 11 is offered. Only if you remove all the Hyper-V stuff from Windows does Virtualbox use its own virtualization engine, see the icon below in the image. If you no longer use VirtualBox, uninstalling it should also mitigate the safeguard. If this is visible, Virtualbox uses components from Hyper-V, with which, for example, the Windows Sandbox also runs. If you take a closer look at the virtual machine window, you might see a turtle icon in the lower right corner. Oracle did not place this notice for fun (c) PCtipp.chĪlthough my accusation of “no indication” needs to be put into perspective a little. ![]() Less nice, however, that Virtualbox never displayed a corresponding message while I was struggling with the virtual machines. The briefest text in the manual is accompanied by a note that (translated) reads roughly: When using this feature, some hosts experience significant virtual machine performance degradation. And this “experimental” is to be taken literally. Half a weekend went by before I came across an inconspicuous hint in the Virtualbox forum and in the online manual: Virtualbox also supports the Hyper-V virtualization engine included in Windows 11 (and probably Windows 10 as well) «experimentally». If it ran through once after hours, other symptoms became noticeable in addition to the underground performance: sudden reboots of the VM for no apparent reason and increasing time delays in the system clock. That should easily be enough! And yet: Whether I tried it with Windows 10 or 11 in the VM, the installation was excruciatingly slow. Thanks to a graphics card suitable for gaming, I was also able to activate 3D acceleration and allocate 256 MB of graphics memory. 2.2 Expand the Contents -> Resources -> Find VirtualBox VM -> Right clicks and select Get Info. ![]() 2.1 Open macOS’s Finder -> Applications -> VirtualBox -> Right clicks and select Show Package Contents. I assigned 8 GB of RAM and 4 CPU cores to the virtual machines. To fix it, we can start the VirtualBox in low resolution mode.
0 Comments
Leave a Reply. |