1. Virtualising 3D Hardware

2. Basically VM 1 VM 2 Multiplex real hardware

3. Fortunately Graphics drivers already do that! Run Quake at same time as Gears? Driver must multiplex the hardware anyway!

4. Consequently One rendering context in guest VM  one context in Domain 0 Remote graphics library

5. Annoyingly OpenGL: Huge API, pain to remote. OpenGL: Also is not Direct3D Direct3D: Gets used a lot

6. Handily Gallium: 70-function API State tracker interprets native API (such as GL, Direct3D) Sits atop much simpler driver OpenGL  Gallium state tracker: 140,000 LOC

7. Regrettably Direct3D state tracker currently unavailable Gallium: actually suited to remoting? No: Lacks display lists Yes: Display lists losing their edge? No: Can we beat display lists?