Opened 11 years ago
Closed 9 years ago
#12061 closed defect (obsolete)
No GL acceleration running ArchLinux guest under MacOSX host using VirtualBox
Reported by: | k-s | Owned by: | |
---|---|---|---|
Component: | guest additions/x11/graphics | Version: | VirtualBox 4.2.16 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Mac OS X |
Description
This is a cross bug to https://bugs.archlinux.org/task/36746?project=1&opened=14878
Description
Running ArchLinux as a guest OS from inside a !MacOS X running VirtualBox fails to load DRI, AIGLX and has no !OpenGL acceleration.
From the logs it seems that VirtualBox is not DRI2 capable, but I'm unsure if that's the case or if my system is not configured properly.
Additional info
- Host:
- Guest:
- OS: ArchLinux latest as 2013-08-30
- virtualbox-guest-modules: 4.2.16-8
- virtualbox-guest-utils: 4.2.16-1
Relevant X logs
[ 3.771] (II) LoadModule: "vboxvideo" [ 3.773] (II) Loading /usr/lib/xorg/modules/drivers/vboxvideo.so [ 3.775] (II) Module vboxvideo: vendor="Oracle Corporation" [ 3.775] compiled for 10.6.99, module version = 1.0.1 [ 3.775] Module class: X.Org Video Driver [ 3.775] ABI class: X.Org Video Driver, version 14.1 [ 3.775] (**) Load address of symbol "VBOXVIDEO" is 0xb71fbf40 ... [ 3.781] (II) VBoxVideo: guest driver for VirtualBox: vbox ... [ 3.806] (II) VBoxVideo(0): VirtualBox guest additions video driver version 4.2.16_OSE ... [ 3.850] (II) Loading sub module "dri" [ 3.850] (II) LoadModule: "dri" [ 3.850] (II) Module "dri" already built-in ... [ 3.870] (II) VBoxVideo(0): [drm] Using the DRM lock SAREA also for drawables. [ 3.870] (II) VBoxVideo(0): [drm] framebuffer handle = 0xe0000000 [ 3.870] (II) VBoxVideo(0): [drm] added 1 reserved context for kernel ... [ 3.892] (II) AIGLX: Screen 0 is not DRI2 capable [ 3.892] drmOpenDevice: node name is /dev/dri/card0 [ 3.892] drmOpenDevice: open result is 13, (OK) [ 3.892] drmOpenByBusid: Searching for BusID pci:0000:00:02.0 [ 3.892] drmOpenDevice: node name is /dev/dri/card0 [ 3.892] drmOpenDevice: open result is 13, (OK) [ 3.892] drmOpenByBusid: drmOpenMinor returns 13 [ 3.892] drmOpenByBusid: Interface 1.4 failed, trying 1.1 [ 3.892] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0 [ 3.909] (II) Next line is added to allow vboxvideo_drv.so to appear as whitelisted driver [ 3.909] (II) The file referenced, is *NOT* loaded [ 3.909] (II) Loading /usr/lib/xorg/modules/drivers//ati_drv.so [ 3.909] (EE) AIGLX error: vboxvideo does not export required DRI extension [ 3.909] (EE) AIGLX: reverting to software rendering [ 3.997] (II) AIGLX: Loaded and initialized swrast [ 3.997] (II) GLX: Initialized DRISWRAST GL provider for screen 0
Attachments (1)
Change History (4)
by , 11 years ago
Attachment: | Xorg.0.log added |
---|
comment:1 by , 11 years ago
The log output you gave is expected on systems where 3D is working as we do not interface properly to the system 3D interfaces. Could you please say what other symptoms you see of 3D failing? For instance does glxinfo in the guest system show that you are using software rendering?
comment:2 by , 10 years ago
I cannot say for him, but I seem to have the same problem here
HOST : Ubuntu 14.04.2 x86_64 with kernel 3.13.0-54 running Virtualbox 4.3.28 r100309
GUEST : Arch linux x86_64 (every thing up to date, no testing repo) with vbox addition 4.3.28-1
output of glxinfo :
direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 ... client glx vendor string: Mesa Project and SGI client glx version string: 1.4 ... OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.6, 128 bits) OpenGL version string: 3.0 Mesa 10.5.7 OpenGL shading language version string: 1.30
comment:3 by , 9 years ago
Component: | 3D support → guest additions/x11/graphics |
---|---|
Resolution: | → obsolete |
Status: | new → closed |
Xorg.0.log