Archlinux as Guest system on new Virtualbox 2.2.0

m-4 · 2009-04-26 09:09:18

Hi,
I've installed Archlinux on Virtualbox. Everything goes smoothly, except installing the additions.
When I try to build them I've got an error "this system does not seem to have support for OpenGL direct rendering", I have libdrm installed, but I can't find headers (like drmP.h). Is there any way to install it? Without it there is no vboxvideo driver, so there will be no opengl acceleration

--
Best regards,
Mateusz

Nate · 2009-04-29 07:04:42

I don't know the answer to your problem, but wanted to know if you are able to run X windows under different resolutions in Virtual Box?

For example, can you maximize the Virtual machine, and X automatically resizes?

Thanks,
-Nate

Wintervenom · 2009-04-29 07:55:21

Post deleted.

Last edited by Wintervenom (2009-08-03 14:07:00)

djgera · 2009-05-04 00:49:13

The Arch Linux kernel26 package don't provide this headers.

The just download the kernel source, extract and copy the include directory:

[root@gerardo ~]# tar xf linux-2.6.29.2.tar.bz2
[root@gerardo ~]# cp -a linux-2.6.29.2/include/drm /usr/src/linux-2.6.29-ARCH/include/
[root@gerardo ~]# /media/dvd/VBoxLinuxAdditions-x86.run
Verifying archive integrity... All good.
Uncompressing VirtualBox 2.2.2 Guest Additions for Linux installation..............................................................................................................................................................................................................................
VirtualBox 2.2.2 Guest Additions installation
Building the VirtualBox Guest Additions kernel module...
Building the shared folder support kernel module...
Building the drm support kernel module...
Installing the VirtualBox Guest Additions...

Successfully installed the VirtualBox Guest Additions.
You must restart your guest system in order to complete the installation.

[root@gerardo ~]# ln -s /usr/lib/VBoxOGL.so /usr/lib/xorg/modules/dri/vboxvideo_dri.so

EDIT: the last command is because the install of vbox, search for the inexistent directory /usrt/lib/dri

Last edited by djgera (2009-05-04 01:51:33)

djgera · 2009-05-04 02:31:36

btw: i forgot

[root@gerardo ~]# ln -s /usr/lib/xorg/modules/dri /usr/lib/dri
[root@gerardo ~]# gpasswd -a youruseringuest video

Last edited by djgera (2009-05-04 02:31:55)

djgera · 2009-05-15 03:55:19

btw: the kernel26 now includes these headers http://bugs.archlinux.org/task/14568

theringmaster · 2009-05-30 05:34:51

Thanks, djgera!!

it works for me, and all this time i could never figure this out.

Last edited by theringmaster (2009-06-12 17:44:58)

dvh · 2009-09-24 03:42:27

first off, thanks to djgera I have made some progress with this problem. I had an error similar to the one that started this thread. I created the symlinks as recommended, and the first error has been alleviated, but now I get a new issue. here is the relevant part of my Xorg startup log...

(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) AIGLX: Screen 0 is not DRI2 capable
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 11, (OK)
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 11, (OK)
drmOpenByBusid: drmOpenMinor returns 11
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
(EE) AIGLX error: Calling driver entry point failed(EE) AIGLX: reverting to software rendering
(II) AIGLX: Loaded and initialized /usr/lib/xorg/modules/dri/swrast_dri.so
(II) GLX: Initialized DRISWRAST GL provider for screen 0
(II) VBoxVideo(0): Setting screen physical size to 289 x 232

any idea what this "Calling driver entry point..." error is caused by? any advice would be much appreciated.

-dvh

Syntaxeus · 2009-12-26 18:06:03

Hi!

I have struggled with getting Compiz fusion to work on my Arch Linux 64-bit guest system in Virtual Box 3.1 on my Win 7 64-bit host for some time now, but without results.

I have installed the latest guests additions, without any errors and added the symlink:

 ln -s /usr/lib/VBoxOGL.so /usr/lib/xorg/modules/dri/vboxvideo_dri.so

then I get this error in my Xorg.0.log file:

(EE) AIGLX error: vboxvideo does not export required DRI extension

so I tried your tip and created the symlink:

ln -s /usr/lib/xorg/modules/dri /usr/lib/dri

I also add my user to the video group as suggested both neither of these things worked, I still the previous error:

(EE) AIGLX error: vboxvideo does not export required DRI extension

Any help in this matter will be very appreciated!

prairie_dad · 2009-12-26 18:23:20

so far, I am not aware of anyone who has succeeded in getting 3D accel to run on Arch as a guest in VBox...myself included, though I too have tried and tried...alas! The errors are more or less the same...

dave

Syntaxeus · 2010-02-02 20:56:48

I have updated Virtualbox to the latest version and reinstalled the guest additions, but the above problems remains.
Does any one got a solution to this?

Ultraman · 2010-02-02 23:23:59

prairie_dad wrote:

so far, I am not aware of anyone who has succeeded in getting 3D accel to run on Arch as a guest in VBox...myself included, though I too have tried and tried...alas! The errors are more or less the same...
dave

I have. Windows host and Arch guest. OpenGL rendering worked.
I believe my problem was solved with setting the symlink, but i'm not 100% sure.
I had that running half a year ago. Searched my ass off to fix it...

I don't know what's causing the problem in this case, unfortunately.

Last edited by Ultraman (2010-02-02 23:24:37)

Aidenn · 2010-02-11 14:07:57

apparently the message about reverting to software mode is irrelevant. verify with glxinfo/glxgears only, glxgears should not say anything about not being able to connect to host. I'm still struggling with that part, but others have confirmed that they got 3d acceleration working and the AIGLX message was still there.

-- edit --

ok, it's working if X is run as root. user probably needs permissions in xorg.conf. I'll check it out now. ;)

-- edit --

nah, setting DRI permissions to 0666 didn't help. back to troubleshooting. does anyone know what glxgears does before reaching /dev/dri/-card0? it's got to be permissions, but on something other than the -card0.

-- edit --

finally cracked the damn thing after a bit of stracing. ;)

anyway, the virtualbox-ose-additions package lacks udev rules for creating /dev/vbox* files and they are created with root:root 0660 permissions, when /dev/vboxuser should be 0666. that's all one has to do to get working 3D acceleration (in addition to being in the video group and symlinking the dri files, of course). whew, finally.

to make this permanent put the following in /lib/udev/rules.d/60-virtualbox-ose-additions.rules:

KERNEL=="vboxuser", NAME="vboxuser", OWNER="root", MODE="0666"

Last edited by Aidenn (2010-02-11 15:11:00)

Syntaxeus · 2010-02-23 21:17:23

Aidenn wrote:

apparently the message about reverting to software mode is irrelevant. verify with glxinfo/glxgears only, glxgears should not say anything about not being able to connect to host. I'm still struggling with that part, but others have confirmed that they got 3d acceleration working and the AIGLX message was still there.
-- edit --
ok, it's working if X is run as root. user probably needs permissions in xorg.conf. I'll check it out now.
-- edit --
nah, setting DRI permissions to 0666 didn't help. back to troubleshooting. does anyone know what glxgears does before reaching /dev/dri/-card0? it's got to be permissions, but on something other than the -card0.
-- edit --
finally cracked the damn thing after a bit of stracing.
anyway, the virtualbox-ose-additions package lacks udev rules for creating /dev/vbox* files and they are created with root:root 0660 permissions, when /dev/vboxuser should be 0666. that's all one has to do to get working 3D acceleration (in addition to being in the video group and symlinking the dri files, of course). whew, finally.
to make this permanent put the following in /lib/udev/rules.d/60-virtualbox-ose-additions.rules:
KERNEL=="vboxuser", NAME="vboxuser", OWNER="root", MODE="0666"

This did not work for me at all. However I am using the PUEL version. Can it make a difference?

Aidenn · 2010-02-23 22:02:43

Syntaxeus wrote:

This did not work for me at all. However I am using the PUEL version. Can it make a difference?

Yes, the PUEL licensed modules in Arch repos are for host only, not guest (though they provide the guest additions ISO for manual installation). Anyway, virtualbox-ose-additions and virtualbox-ose-additions-modules install the very same modules the official Virtualbox additions ISO does. So even if you use the PUEL Virtualbox as a host (like I do), by all means use virtualbox-ose-additions* packages.

By the way, you don't need to type in these rules by hand anymore, it's been fixed by the maintainer of the ose packages.

Syntaxeus · 2010-02-24 18:23:08

Aidenn wrote:

Syntaxeus wrote:
This did not work for me at all. However I am using the PUEL version. Can it make a difference?
Yes, the PUEL licensed modules in Arch repos are for host only, not guest (though they provide the guest additions ISO for manual installation). Anyway, virtualbox-ose-additions and virtualbox-ose-additions-modules install the very same modules the official Virtualbox additions ISO does. So even if you use the PUEL Virtualbox as a host (like I do), by all means use virtualbox-ose-additions* packages.
By the way, you don't need to type in these rules by hand anymore, it's been fixed by the maintainer of the ose packages.

Ah, thanks for the tips.
However, I'm using the 64-bit version of VirtualBox, and thus I can't install the virtualbox-ose-additions* packages.
So I am only able to mount the additions belonging to the PUEL host as a CD and install it from there (./VBoxLinuxAdditions-amd64.run)

Last edited by Syntaxeus (2010-02-24 18:26:55)

Aidenn · 2010-02-25 10:39:18

I was having trouble with manual installation from the additions ISO too. maybe you could recompile the ose additions with ABS, the PKGBUILD says arch=('i686' 'x86_64').

Syntaxeus · 2010-03-06 18:48:59

Aidenn wrote:

I was having trouble with manual installation from the additions ISO too. maybe you could recompile the ose additions with ABS, the PKGBUILD says arch=('i686' 'x86_64').

So I tried the x64 version of the ose-version from here: http://archlinux.ro/~ioni/vbox/, but the problem still remains

When I give the

fusion-icon

command, the screen becomes white, but I can rotate "the cube" with ctrl+alt+right arrow.
If i try the

compiz --replace

command the boarders from the windows disappears and I get the message

OpenGL Warning: No pincher, please call crStateSetCurrentPointers() in your SPU
OpenGL Info: Using XSHM for GLX_EXT_texture_from_pixmap

I start to wonder if it has something to do with my xorg.conf. This is what it looks like:

Section "ServerLayout"
    Identifier     "X.org Configured"
    Screen      0  "Screen0" 0 0
    InputDevice    "Mouse0" "CorePointer"
    InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
    ModulePath   "/usr/lib/xorg/modules"
    FontPath     "/usr/share/fonts/misc"
    FontPath     "/usr/share/fonts/100dpi:unscaled"
    FontPath     "/usr/share/fonts/75dpi:unscaled"
    FontPath     "/usr/share/fonts/TTF"
    FontPath     "/usr/share/fonts/Type1"
EndSection

Section "Module"
    Load  "extmod"
    Load  "dbe"
    Load  "dri"
    Load  "glx"
    Load  "dri2"
EndSection

Section "InputDevice"
    Identifier  "Keyboard0"
    Driver      "kbd"
EndSection

Section "InputDevice"
    Identifier  "Mouse0"
    Driver      "vboxmouse"
    Option      "CorePointer"
    Option        "Protocol" "auto"
    Option        "Device" "/dev/input/mice"
    Option        "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
    Identifier   "Monitor0"
    VendorName   "Monitor Vendor"
    ModelName    "Monitor Model"
EndSection

Section "Device"
        ### Available Driver options are:-
        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
        ### [arg]: arg optional
    Identifier  "Configured Video Device"
    Driver      "vboxvideo"
    VendorName  "InnoTek Systemberatung GmbH"
    BoardName   "VirtualBox Graphics Adapter"
    BusID       "PCI:0:2:0"
EndSection

Section "Screen"
    Identifier "Screen0"
    Device     "Configured Video Device"
    Monitor    "Monitor0"
    DefaultDepth    24
    SubSection "Display"
        Viewport   0 0
        Depth     1
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     4
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     8
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     15
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     16
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     24
        Modes      "1920x1080"
    EndSubSection
EndSection

#Section "ServerFlags"
#    Option "DontZap" "false"
#EndSection

Last edited by Syntaxeus (2010-03-06 18:53:43)

Aidenn · 2010-03-07 03:14:09

I don't see the message about not being able to connect to host (most easily noticed with glxgears). If it is not there, then it means 3D acceleration is working correctly and the problem lies elsewhere. Remember that even if you get 3D acceleration working (that is, glxgears doesn't throw an error and it's moving smoothly), you can't expect everything graphics-related to work like under a native system, especially since 2D acceleration is completely missing. AFAIK VirtualBox's OpenGL wrapper translates only the bare minimum.

That said, Ubuntu's compiz seems to work fine with VirtualBox. Maybe try a different compiz build?

Syntaxeus · 2010-03-30 19:27:33

Sigh...

I have now upgraded Virtual Box to 3.1.6 and reinstalled Compiz completely.
No success. I am however able to see some icon effects when using the

compiz --replace ccp & emerald --replace

command, but no window borders or rotating cube.
When I try to start compiz with the compiz-manager command I get

 Checking for Xgl: Not present

I have also commented out the

Section "Files"
    ModulePath   "/usr/lib/xorg/modules"
    FontPath     "/usr/share/fonts/misc"
    FontPath     "/usr/share/fonts/100dpi:unscaled"
    FontPath     "/usr/share/fonts/75dpi:unscaled"
    FontPath     "/usr/share/fonts/TTF"
    FontPath     "/usr/share/fonts/Type1"
EndSection

Section "Module"
    Load  "extmod"
    Load  "dbe"
    Load  "dri"
    Load  "glx"
    Load  "dri2"
EndSection

part.

The compiz-check runs with now errors however.

Any one?

Last edited by Syntaxeus (2010-03-30 19:31:48)

daedalus · 2010-04-21 03:06:18

I'm getting the same result as previous posters:

"(EE) AIGLX error: vboxvideo does not export required DRI extension"

Also, this fails regardless of whether or not 3D acceleration is enabled, although with one it simply says driver entry point failed.

I have run through all of the fixes suggested in this thread, but so far nothing has worked

Last edited by daedalus (2010-04-21 03:38:58)

Syntaxeus · 2011-09-26 10:55:47

Well... one and a half year has went by since I posted this thread, and after recently installing a similar set up as described above (Win 7 64-bit host, Arch linux 64-bit guest) the DRI support is still (!) broken.

(EE) AIGLX error: vboxvideo does not export required DRI extension

How could this be? Does anyone have any kind of workaround for this?

Last edited by Syntaxeus (2011-09-26 10:57:35)

Inxsible · 2011-09-26 13:50:36

Syntaxeus wrote:

Well... one and a half year has went by since I posted this thread

I don't see you as the OP !!

this thread has Virtualbox 2.2 reference. Do you know what the latest version of Virtualbox is?

Please don't necrobump old threads. Read this forum rule :: https://wiki.archlinux.org/index.php/Fo … Bumping.27

Closing...

Arch Linux

#1 2009-04-26 09:09:18

Archlinux as Guest system on new Virtualbox 2.2.0

#2 2009-04-29 07:04:42

Re: Archlinux as Guest system on new Virtualbox 2.2.0

#3 2009-04-29 07:55:21

Re: Archlinux as Guest system on new Virtualbox 2.2.0

#4 2009-05-04 00:49:13

Re: Archlinux as Guest system on new Virtualbox 2.2.0

#5 2009-05-04 02:31:36

Re: Archlinux as Guest system on new Virtualbox 2.2.0

#6 2009-05-15 03:55:19

Re: Archlinux as Guest system on new Virtualbox 2.2.0

#7 2009-05-30 05:34:51

Re: Archlinux as Guest system on new Virtualbox 2.2.0

#8 2009-09-24 03:42:27

Re: Archlinux as Guest system on new Virtualbox 2.2.0

#9 2009-12-26 18:06:03

Re: Archlinux as Guest system on new Virtualbox 2.2.0

#10 2009-12-26 18:23:20

Re: Archlinux as Guest system on new Virtualbox 2.2.0

#11 2010-02-02 20:56:48

Re: Archlinux as Guest system on new Virtualbox 2.2.0

#12 2010-02-02 23:23:59

Re: Archlinux as Guest system on new Virtualbox 2.2.0

#13 2010-02-11 14:07:57

Re: Archlinux as Guest system on new Virtualbox 2.2.0

#14 2010-02-23 21:17:23

Re: Archlinux as Guest system on new Virtualbox 2.2.0

#15 2010-02-23 22:02:43

Re: Archlinux as Guest system on new Virtualbox 2.2.0

#16 2010-02-24 18:23:08

Re: Archlinux as Guest system on new Virtualbox 2.2.0

#17 2010-02-25 10:39:18

Re: Archlinux as Guest system on new Virtualbox 2.2.0

#18 2010-03-06 18:48:59

Re: Archlinux as Guest system on new Virtualbox 2.2.0

#19 2010-03-07 03:14:09

Re: Archlinux as Guest system on new Virtualbox 2.2.0

#20 2010-03-30 19:27:33

Re: Archlinux as Guest system on new Virtualbox 2.2.0

#21 2010-04-21 03:06:18

Re: Archlinux as Guest system on new Virtualbox 2.2.0

#22 2011-09-26 10:55:47

Re: Archlinux as Guest system on new Virtualbox 2.2.0

#23 2011-09-26 13:50:36

Re: Archlinux as Guest system on new Virtualbox 2.2.0

Board footer