Hi,
Host - Windows 7 RC, Intel graphics
VirtualBox 3.0 release
Guest - OpenSolaris 111b (a.k.a 200906).
After upgrading VirtualBox (uninstalling first the guest additions of 3.0B1, installing 3.0 and then reinstalling the new guest additions) I get:
ld.so.1: gnome-appearance-properties: fatal: relocation error: file /usr/X11/lib/libGL.so.1: symbol glXFreeMemoryMESA: referenced symbol not found
ld.so.1: gnome-appearance-properties: fatal: relocation error: file /usr/bin/gnome-appearance-properties: symbol glXQueryServerString: referenced symbol not found
and running /usr/X/demo/glxgears:
$ /usr/X/demo/glxgears
ld.so.1: glxgears: fatal: relocation error: file /usr/lib/libGL.so.1: symbol glXFreeMemoryMESA: referenced symbol not found
ld.so.1: glxgears: fatal: relocation error: file /usr/X11/demo/glxgears: symbol glXChooseVisual: referenced symbol not found
[1] 840 killed /usr/X/demo/glxgears
This used to work on the beta.
Otherwise seems OK. I'll try the same tomorrow on a Nevada host.
Chavdar Ivanov
GLX lost on VBox3.0 release
-
- Posts: 23
- Joined: 16. Jun 2009, 12:55
- Primary OS: OpenSolaris 11
- VBox Version: PUEL
- Guest OSses: Windows Server 2008 R2, Windows 7, OpenSolaris
Re: GLX lost on VBox3.0 release
Just to confirm the same on a clean installation of OpenSolaris 1002 (117).
Chavdar Ivanov
Chavdar Ivanov
-
- Posts: 23
- Joined: 16. Jun 2009, 12:55
- Primary OS: OpenSolaris 11
- VBox Version: PUEL
- Guest OSses: Windows Server 2008 R2, Windows 7, OpenSolaris
Re: GLX lost on VBox3.0 release
This is getting annoying - answering my own posts...
GLX on VBox 3.0 release works fine with the Guest Additions from the second Beta (49051).
C I
GLX on VBox 3.0 release works fine with the Guest Additions from the second Beta (49051).
C I
Re: GLX lost on VBox3.0 release
Wait for the next update, it's fixed there.
-
- Posts: 23
- Joined: 16. Jun 2009, 12:55
- Primary OS: OpenSolaris 11
- VBox Version: PUEL
- Guest OSses: Windows Server 2008 R2, Windows 7, OpenSolaris
Re: GLX lost on VBox3.0 release
Thanks, good to know it's under control . . . VirtualBox pace of development this year has been truly amazing.Leonid wrote:Wait for the next update, it's fixed there.
Chavdar