![]() ![]() (Note that there may be other messages relating to the sudoers file that do not represent a problem.) If you find any lines in that log file saying something about "no valid sudoers" being found, you have a problem with your system that is interfering with the installation. Next, search for "sudoers" (without the quotes). Double-click that install.log file to open it in the Console application. In the folder that opens, an install.log file should be selected. In the Finder, choose Go to Folder from the Go menu, then enter the following path into the window that opens: VBoxVGA is an 'historic' hangover intended for mainly for older operating systems and it doesn't provide 3D support, so running that option in a Windows 11 VM should produce similar behaviour to running VBoxSVGA with 3D disabled, but, out of curiosity, I'll do some more personal testing, on both macOS and Windows Hosts before reporting my outcomes to the VirtualBox Developers via the Public Bugtracker.Endpoint Detection & Response for Servers However, somewhat confusingly, on one HP Laptop I've used, the same VMs all run perfectly! 'Linux' VM installations tested seem to work normally. Windows 11 VMs always freeze during startup, unless the Guest Additions installations are downgraded to Version 6.1.XX Windows 10 VMs only work with 3D disabled and ![]() Windows 7 VMs seem to work normally with 3D enabled but The reason I asked, is that, as you know, VBoxSVGA is the default (intended) setting for Windows VMs on which 3D is supported but, for me, if the Version 7.0.xx Guest Additions are installed, then on some Windows PCs, and also on Intel macOS hardware I've been able to test with VirtualBox 7 releases up tp 7.0.6: For reporting back and glad you've hit on a 'work-around' for your current setup. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |