when 3D acceleration is enabled linux host doesn't boot
Posted: 20. Apr 2020, 17:13
Hello,
I'm having big troubles with the latest version of VirtualBox to start my Linux guest machines with "3D Acceleration" enabled.
Setup:
- host OS - Windows 10 Pro
- GPU - Nvidia RTX 2070 MAX-Q
- VirtualBox 6.1.6
I have multiple Linux guest VMs which refuse to start when "3D Acceleration" is enabled.
Example:
- linux guest - Ubuntu 18.04 LTS
- guest additions installed and up to date
- last logged message from console -
After the the above message the UI isn't loading at all, the machine just hangs.
Of course the moment I disable the "3D Acceleration" the guest OS is booting with no problem, but the UI keeps having bunch of issues while rendering components, example - I open Firefox and then start Terminal, the UI is freezing and sometimes performs user logout automatically.
I have resolved the issue by reverting to VirtualBox 6.0.14 and changing the Windows Hyper-V launch Type to "off" -.
Why I have to change the Hyper-V Launch Type ? - no idea, but without making the change and restarting my machine I cannot even open a session with VB to any guest VM.
It's getting even more interesting, because after changing the hyper-v launch type I can no longer use my Windows Docker.
I'd like to keep both my VMs and Docker running, so if anyone have encounter the problem I'd love some details and pointers ?
I'm having big troubles with the latest version of VirtualBox to start my Linux guest machines with "3D Acceleration" enabled.
Setup:
- host OS - Windows 10 Pro
- GPU - Nvidia RTX 2070 MAX-Q
- VirtualBox 6.1.6
I have multiple Linux guest VMs which refuse to start when "3D Acceleration" is enabled.
Example:
- linux guest - Ubuntu 18.04 LTS
- guest additions installed and up to date
- last logged message from console -
Code: Select all
[ Ok ] Started vboxadd-service.serviceOf course the moment I disable the "3D Acceleration" the guest OS is booting with no problem, but the UI keeps having bunch of issues while rendering components, example - I open Firefox and then start Terminal, the UI is freezing and sometimes performs user logout automatically.
I have resolved the issue by reverting to VirtualBox 6.0.14 and changing the Windows Hyper-V launch Type to "off" -
Code: Select all
bcdedit.exe /set hypervisorlaunchtype offWhy I have to change the Hyper-V Launch Type ? - no idea, but without making the change and restarting my machine I cannot even open a session with VB to any guest VM.
It's getting even more interesting, because after changing the hyper-v launch type I can no longer use my Windows Docker.
I'd like to keep both my VMs and Docker running, so if anyone have encounter the problem I'd love some details and pointers ?