VBox 4.3.26 - no 3D acceleration

bfg9800gt · 2015-05-14 12:07:56

Hello guys,

I've installed Arch with all the guides provided on Wiki. Now I encountered a problem that couldnt resolve for three days: No hardware rendering. Only Gallium.

Host: Win8.1
VBox 4.3.26 with guest additions from pacman repos

[dan@arch ~]$ glxinfo |grep render
direct rendering: Yes
    GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
    GLX_MESA_query_renderer, GLX_OML_swap_method, GLX_SGIS_multisample, 
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.6, 128 bits)
    GL_ARB_conditional_render_inverted, GL_ARB_conservative_depth, 
    GL_NV_blend_square, GL_NV_conditional_render, GL_NV_depth_clamp,

[root@arch dan]# dmesg |grep vbox
[    5.684685] vboxguest: misc device minor 58, IRQ 20, I/O port d020, MMIO at 00000000f0400000 (size 0x400000)
[    5.684690] vboxguest: Successfully loaded version 4.3.26_OSE (interface 0x00010004)
[    5.913222] vboxsf: Successfully loaded version 4.3.26_OSE (interface 0x00010004)
[    6.202601] [drm] Initialized vboxvideo 1.0.0 20090303 for 0000:00:02.0 on minor 0

[    70.018] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[    70.018] (II) LoadModule: "glx"
[    70.018] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    70.020] (II) Module glx: vendor="X.Org Foundation"
[    70.020]    compiled for 1.17.1, module version = 1.0.0
[    70.020]    ABI class: X.Org Server Extension, version 9.0
[    70.020] (==) AIGLX enabled
[    70.020] (==) Matched vboxvideo as autoconfigured driver 0
[    70.020] (==) Matched vboxvideo as autoconfigured driver 1
[    70.020] (==) Matched modesetting as autoconfigured driver 2
[    70.020] (==) Matched fbdev as autoconfigured driver 3
[    70.021] (==) Matched vesa as autoconfigured driver 4
[    70.021] (==) Assigned the driver to the xf86ConfigLayout
[    70.021] (II) LoadModule: "vboxvideo"
[    70.021] (II) Loading /usr/lib/xorg/modules/drivers/vboxvideo.so
[    70.021] (II) Module vboxvideo: vendor="Oracle Corporation"
[    70.021]    compiled for 1.6.99, module version = 1.0.1
[    70.021]    Module class: X.Org Video Driver
[    70.021]    ABI class: X.Org Video Driver, version 19.0
[    70.021] (**) Load address of symbol "VBOXVIDEO" is 0x7f9922d94840
[    70.021] (II) LoadModule: "modesetting"
[    70.021] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    70.021] (II) Module modesetting: vendor="X.Org Foundation"
[    70.021]    compiled for 1.17.1, module version = 1.17.1
[    70.021]    Module class: X.Org Video Driver
[    70.021]    ABI class: X.Org Video Driver, version 19.0
[    70.021] (II) LoadModule: "fbdev"
[    70.021] (WW) Warning, couldn't open module fbdev
[    70.022] (II) UnloadModule: "fbdev"
[    70.022] (II) Unloading fbdev
[    70.022] (EE) Failed to load module "fbdev" (module does not exist, 0)
[    70.022] (II) LoadModule: "vesa"
[    70.022] (WW) Warning, couldn't open module vesa
[    70.022] (II) UnloadModule: "vesa"
[    70.022] (II) Unloading vesa
[    70.022] (EE) Failed to load module "vesa" (module does not exist, 0)
[    70.022] (II) VBoxVideo: guest driver for VirtualBox: vbox
[    70.022] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    70.022] (++) using VT number 2
[    70.022] (WW) Falling back to old probe method for modesetting
[    70.022] (II) VBoxVideo(0): VirtualBox guest additions video driver version 4.3.26_OSE

What would be your thoughts?
Thanks

bfg9800gt · 2015-05-14 13:34:14

Also in Xorg log:

[    70.107] (II) VBoxVideo(0): Output VGA-0 connected
[    70.107] (II) VBoxVideo(0): Using exact sizes for initial modes
[    70.107] (II) VBoxVideo(0): Output VGA-0 using initial mode 1086x800
[    70.108] (II) VBoxVideo(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[    70.108] (II) VBoxVideo(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[    70.108] (==) VBoxVideo(0): DPMS enabled
[    70.108] (--) RandR disabled
[    70.116] (II) AIGLX: Screen 0 is not DRI2 capable
[    70.116] (EE) AIGLX: reverting to software rendering
[    70.139] (II) AIGLX: Loaded and initialized swrast
[    70.139] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[    70.139] (II) VBoxVideo(0): Setting screen physical size to 287 x 211
[    70.188] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[    70.189] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[    70.189] (II) LoadModule: "evdev"
[    70.189] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[    70.189] (II) Module evdev: vendor="X.Org Foundation"
[    70.189]    compiled for 1.17.1, module version = 2.9.2

AIGLX: Screen 0 is not DRI2 capable
AIGLX: reverting to software rendering

mwillems · 2015-05-14 15:34:52

What desktop manager/desktop environment are you using? There's an issue with the current version of gdm where it breaks acceleration in VBox.

bfg9800gt · 2015-05-14 15:36:06

Yes, it's Gnome 3. Where can I read about this issue?
Still can't imagine how is it possible.

Last edited by bfg9800gt (2015-05-14 15:41:41)

mwillems · 2015-05-14 16:45:00

Gnome-session is fine it's gdm specifically that's the issue. I've tested several different configurations, results summarized in this thread : https://bbs.archlinux.org/viewtopic.php?id=196776

There's no reason to take my word for it, it's easy to test: try disabling gdm and enabling lightdm. Alternatively, try rolling gdm back to 3.14. Both of those steps restore hardware acceleration in virtualbox for me on several different VMs.

Last edited by mwillems (2015-05-14 16:45:46)

bfg9800gt · 2015-05-14 17:11:15

Wow, you're right. I noticed that gdm use two ttys, but thought it just another fancy stuff from gnome devs. Well, it is.
Now I got the hardware rendering, big thanks to you.

Time for me to solve another trashload:

[dan@arch ~]$ glxinfo | grep render
pci id for fd 4: 80ee:beef, driver (null)
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
direct rendering: Yes
OpenGL renderer string: Chromium

Last edited by bfg9800gt (2015-05-14 17:12:37)

mwillems · 2015-05-14 17:24:23

No problem. I would appreciate it if you could add your experience to my bug over at the gnome bugzilla, to help get this fixed: https://bugzilla.gnome.org/show_bug.cgi?id=749390

Last edited by mwillems (2015-05-14 17:25:16)

bfg9800gt · 2015-05-14 17:37:13

I've confirmed it and will watch closely this thread. Thank you

rzulu · 2015-05-28 05:09:01

pop up

Trilby · 2015-05-28 18:15:05

rzulu, please do not make empty posts.

OK38 · 2015-05-28 21:17:25

Hi,

Did you try this : "After enabling OpenGL acceleration as described above, reboot the guest into safe mode (press F8 before the Windows screen appears but after the Virtualbox screen disappears), and install Virtualbox guest additions, during install enable checkbox "Direct3D support". Reboot back to normal mode and you should have accelerated Direct3D."

VirtualBox D3D acceleration in Windows guests

mwillems · 2015-05-28 21:54:06

That advice is inapplicable because no one here has a windows guest. This thread is about broken 3d acceleration in Linux guests. OP has a windows host, but I do not (linux host/linux guest), so the issue has nothing to do with directx.

It's a gdm 3.16 issue, switching to another desktop manager or rolling back to a prior version of gdm fixes it.

Last edited by mwillems (2015-05-28 21:55:36)

Arch Linux

#1 2015-05-14 12:07:56

VBox 4.3.26 - no 3D acceleration

#2 2015-05-14 13:34:14

Re: VBox 4.3.26 - no 3D acceleration

#3 2015-05-14 15:34:52

Re: VBox 4.3.26 - no 3D acceleration

#4 2015-05-14 15:36:06

Re: VBox 4.3.26 - no 3D acceleration

#5 2015-05-14 16:45:00

Re: VBox 4.3.26 - no 3D acceleration

#6 2015-05-14 17:11:15

Re: VBox 4.3.26 - no 3D acceleration

#7 2015-05-14 17:24:23

Re: VBox 4.3.26 - no 3D acceleration

#8 2015-05-14 17:37:13

Re: VBox 4.3.26 - no 3D acceleration

#9 2015-05-28 05:09:01

Re: VBox 4.3.26 - no 3D acceleration

#10 2015-05-28 18:15:05

Re: VBox 4.3.26 - no 3D acceleration

#11 2015-05-28 21:17:25

Re: VBox 4.3.26 - no 3D acceleration

#12 2015-05-28 21:54:06

Re: VBox 4.3.26 - no 3D acceleration

Board footer