virtualbox.org

Hello,

I have been trying to get the HD3000 graphics to use in VBox 4.2.10 (+ newest Guest Addition) with ticked 3d acceleration in virtualbox.
Unfortunately it seems system is not grabbing built-in HD3000 card; instead some Innotek drivers are being used:

vm@vm-VirtualBox:~$ sudo lshw -c video
*-display UNCLAIMED
description: VGA compatible controller
product: VirtualBox Graphics Adapter
vendor: InnoTek Systemberatung GmbH
physical id: 2
bus info: pci@0000:00:02.0
version: 00
width: 32 bits
clock: 33MHz
capabilities: vga_controller bus_master
configuration: latency=0
resources: memory:e0000000-e7ffffff

The problem is with OpenGL and acceleration - when cairo / compiz works very slow, and gives a lot of artifacts (black background). Obviously thought of drivers, hence installed new mesa and xorg:

sudo add-apt-repository ppa:xorg-edgers/ppa
sudo apt-get upgrade

still proper advatage of 3d has not been taken. Driver being shown by Ubuntu is <unknown>, also there are no proprietary drivers for intels hd3000 (via jockey) - it shows only Oracle VM Virtualbox GuestAdditions for Linux Module .

Did anyone managed to get opengl working on HD3000?

Some additional things:

vm@vm-VirtualBox:~$ echo ${DESKTOP_SESSION}
ubuntu
vm@vm-VirtualBox:~$ /usr/lib/nux/unity_support_test -p
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
OpenGL vendor string: Humper
OpenGL renderer string: Chromium
OpenGL version string: 2.1 Chromium 1.9

Not software rendered: yes
Not blacklisted: yes
GLX fbconfig: yes
GLX texture from pixmap: yes
GL npot or rect textures: yes
GL vertex program: yes
GL fragment program: yes
GL vertex buffer object: yes
GL framebuffer object: yes
GL version is 1.4+: yes

Unity 3D supported: yes

glxwork on mesa works properly - meaning opengl is utilised.

Thanks in advance.

Please ponder the meaning of the word "virtual", as in "Virtual Machine" or VM.

Hi Mpack,

This is not that easy. The other PCs I used had for instance nvidia cards - the priopretary drivers were found and all opengl acceleration was available.
Name also changed to nvidia with recognised chipset.

As this is Intels 3000 card I would assume there would be some drivers to take advantage of opengl. I had gone through many posts and similar problems were found - but with no solution to this, hence I wrote this post here.

What mpack tries to hint at, and you didn't get, is that you are running a VIRTUAL machine, so the hardware seen from within the machine is VIRTUAL and is NOT the physical hardware.
The OS inside the VM has no knowledge of your hardware graphical card, it does not see it. All the Guest OS see is the virtual graphic card.

So any of your attempts to install a driver for a physical graphic card will not work since it is NOT that card that is presented to the guest OS.

Perhaps you should take a step back and tell us what the basic problem is, rather than giving your own diagnosis. Oh, and you should provide a log file too. See Minimum information needed for assistance.

Thanks for the tips, will write later all the data needed.

mpack - The problem is with OpenGL and acceleration - when cairo / compiz works very slow, and gives a lot of artifacts (black background), same happens for every application which uses opengl.
As noted - VM is looking for virtual card, but jockey drivers for nvidia for instance allow Guest system to get advantage of GPU 3d functions. I was trying to build and compile intel drivers (the same way I did with nvidia on other machine) but they do not work exactly as they should - hence artifacts, very slow performance on 3d opengl apps.

In other words I am trying to force Guest system to see proper video card. When system has been installed separately (not in VirtualBox) all was fine - performance was ok, and no artifacts detected.

Well, I admit I'm not really a Linux person, but I can't find any documentation that says that installing nVidia drivers inside a VirtualBox Linux guest is correct, or that it improves the performance of the guest in any way, regardless of what the host graphics chipset is. Naturally, the same will be true of Intel graphics drivers.

If you want to improve graphics performance inside a VM you enable 3D accleration and install the Guest Additions.

thanks, but as stated at the beginning 3d mode is enabled + Guest Additions are installed (and working for instance seamless mode or clipboard host-guest)

Yes, you stated that, but OTOH you have not provided the log file I asked for hence your statements are not supported by evidence. See the "minimum information" link I provided above.

And even if true, what I said is still correct: i.e. those are the only steps which will increase graphics performance inside a VM. Installing drivers for hardware which doesn't exist, e.g. nVidia or Intel Graphics chipsets, will not help in any way that I know of, though I admit its possible that doing so in a Linux guest may involve the installation of generic (not hardware specific) libs which do help. As I mentioned above I am not a Linux user and don't know these things for sure.

In other words I am trying to force Guest system to see proper video card

Not going to happen unless your PC supports VT-d and you go through some hoops to make it work in VirtualBox.

Attaching logs

MRD

Seen some errors here:

Xorg.0.log:[ 18.321] (==) AIGLX enabled
Xorg.0.log:[ 18.321] Loading extension GLX
Xorg.0.log:[ 18.535] (II) AIGLX: Screen 0 is not DRI2 capable
Xorg.0.log:[ 18.592] (EE) AIGLX error: vboxvideo does not export required DRI extension
Xorg.0.log:[ 18.592] (EE) AIGLX: reverting to software rendering

It looks something is missine - either functionality or libs ?

Apologies for the delay on posting logs.

Neither of those is the VM log asked for in the "Minimum Information" link. In any case as far as I'm concerned the conversation was already concluded: you don't install drivers for host hardware in a VM. Period.

Even when VM detects Sandy Bridge - it does not take advantage of opengl in full. GuideAdditions bug then?

Anyway - regardless if we or we dont install those drivers - can you see any ways which could actually fix the issue?

main log below

LG, I think you are not understanding a key component here : The guest IS NOT PRESENTED with the physical card!
It doesn't matter what you install or how, a virtual card is presented to the guest, which is NOT YOUR PHYSICAL CARD.

Hi,

With todays release of Vbox and new Vbox Guest additions this is no longer the case.

As for GPU - sure it will be virtual card, bt it is possible to force system to see host card.

Acceleration is shaky for a moment, but at least there is no artifacts and Cairo works well.

Thanks