Opened 5 years ago
Last modified 4 years ago
#18882 new defect
OpenGL Warning: Failed to connect to host. Make sure 3D acceleration is enabled for this VM.
| Reported by: | mi | Owned by: | |
|---|---|---|---|
| Component: | 3D support | Version: | VirtualBox 6.0.10 |
| Keywords: | Cc: | ||
| Guest type: | BSD | Host type: | Windows |
Description
(This looks like a repeat of the Bug #9889, but is probably unrelated.)
I'm using VirtualBox on a Windows 10 host to run a FreeBSD and some Linux VMs (guests). The FreeBSD VM is my main desktop -- and the only guest with GUI (X11) configured.
My access to the Windows host itself is through Remote Desktop -- from a "dumb" terminal capable of running only the Remote Desktop client.
Things were working fine until the recent upgrade of the hardware -- the same disk was moved into a new machine, with faster CPUs and bigger RAM. There were no software configuration-changes.
VMs also came up Ok, but, upon starting X11 session in the FreeBSD guest, I started getting the error in subject from various X11-clients.
Since then I tried the following changes, to no avail:
- Upgrade the host software (including the extras pack) from 5.x to 6.0.10
- Change the "Graphics Controller" to "VBoxSVGA" in the VM's definition.
- Upgrade the virtualbox-ose-additions inside the VM from 5.x to 6.0.10
Nothing helped -- the machine comes up fine, simpler X11-clients (like xterm) work, but many (including Qt5-using programs) fail with the same message about 3D-acceleration...
I'm attaching the X-server's log from inside the VM, and VM's log from the host.
At the very least, the error should be more detailed. At best, it should not happen :)
Attachments (2)
Change History (3)
by , 5 years ago
| Attachment: | Xorg.0.log added |
|---|
by , 5 years ago
comment:1 by , 4 years ago
The good news is, this problem is finally gone for me -- with the following combination of settings:
- VirtualBox-6.1.2 host
- VirtualBox-6.1.2 Guest Additions inside the VM
Driver "vboxvideo"in thexorg.confVBoxSVGAas the graphics adapter in the VM-definition- 3D enabled in the VM-definition
The bad news is, VirtualBox claims the last two items to be mutually exclusive and, if I use its fancy GUI to configure the VM, forces the graphics adapter to VMSVGA, which does not work (one has to change the Driver settings in xorg.conf to vmware, which, in turn, breaks the integrated desktop feature -- the Host-L).
Fortunately, it is possible to overwrite this unhelpful forcing from command line. After making your other changes, exit the GUI and then enter:
VBoxManage modifyvm kachka --graphicscontroller vboxsvga
X-server's log from inside the guest