Bug 13986 - [REQUEST] VMGL (formerly Xen-GL) implementation in Mesa
Summary: [REQUEST] VMGL (formerly Xen-GL) implementation in Mesa
Status: RESOLVED WONTFIX
Alias: None
Product: Mesa
Classification: Unclassified
Component: Other (show other bugs)
Version: unspecified
Hardware: Other All
: medium enhancement
Assignee: mesa-dev
QA Contact:
URL: http://www.cs.toronto.edu/~andreslc/x...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-09 03:34 UTC by Andreas Setterlind
Modified: 2016-01-24 10:45 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Andreas Setterlind 2008-01-09 03:34:50 UTC
VMGL (formerly Xen-GL) implementation in The Mesa 3D Graphics Library?

Feature request:
Would it be possible to implement VMGL (formerly Xen-GL) into Mesa to enable OpenGL Hardware 3D Acceleration for Virtual Machines via its code?

http://www.cs.toronto.edu/~andreslc/xen-gl/

OpenGL apps running inside a Virtual Machine (VM) can use VMGL to take advantage of graphics hardware acceleration. VMGL can be used on VMware guests, Xen HVM domains (depending on hardware virtualization extensions) and Xen paravirtual domains, using XVnc or the virtual framebuffer. Although we haven't tested it, VMGL should work for qemu, KVM, etc. VMGL is available for X11-based guest OS's: Linux, FreeBSD and OpenSolaris. Finally, VMGL is GPU-independent: we support ATI, Nvidia and Intel GPUs.

Would be great if MESA featured this function nativly.

Currently licensed under the Modified BSD licence but I sure they would consider re-licence or dual-licence if the Mesa project requires it to be(?).

PS! The creator of VMGL also have plans to enhance it to support OpenGL under Windows guests as well.
Comment 1 Timothy Arceri 2016-01-24 10:45:53 UTC
This projects seems to have had its last activity a few months after this request was posted :P 

Think its safe to say its not happening.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.