[vbox-dev] 3D acceleration in Windows Guest
hedonghust at gmail.com
Fri Apr 25 13:10:24 UTC 2014
Let me throw a sprat to catch a mackerel. I might answer a little bit of
You are right to realize that host OpenGL driver is leveraged to boost the
performance of graphic computing on the guest OS. The Stanford distributed
OpenGL library Chromium is used to achieve this. vboxgl.dll is a Window
OpenGL ICD driver that works with guest OS run-time OpenGL32.dll then pack
up OpenGL states into Chromium packets, through tunnels between guest and
host the packets are sent to host to perform the actual 3D rendering.
For Windows host D3D states are translated into OpengGL states with the
help of WINE D3D, a sub project of WINE.
>Date: Fri, 25 Apr 2014 02:16:49 +0000 (GMT)
>From: Jaeyong Yoo <jaeyong.yoo at samsung.com>
>Subject: [vbox-dev] 3D acceleration in Windows Guest
>To: "vbox-dev at virtualbox.org" <vbox-dev at virtualbox.org>
>Message-ID: <28704458.56701398392208980.JavaMail.weblogic at epml03>
>Content-Type: text/plain; charset=euc-kr
>I'm amused by the support 3D acceleration in Windows guest.
>I can run quake 3 without feeling no lag and suddently I've got several
>1) When running quake 3, I observe which opengl DLLs this quake3 is using
>and it turns out it uses both opengl32.dll (which is native DLL from
windows) and vboxgl.dll (which looks like built by using Chromium).
>What I'm wondering is the relationship between opengl32.dll and
vboxgl.dll. Since vboxgl.dll has full GL APIs (such as glBegin, ...),
>quake 3 has to replace the opengl32.dll to vboxgl.dll. But it looks like
quake 3 uses both of them.
>How does this happen?
>2) I saw that windows display driver uses Wine APIs to manipulate the
graphics functions. Since WineD3D is transforming the direct3d call to
>opengl, does it use vboxgl.dll function? Or is there some other magic?
>I'm really impressed by your work :-)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the vbox-dev