12,065
edits
Changes
Jump to navigation
Jump to search
m
→Type 1 Hypervisors
|MESA GL/3Dfx Glide Pass-Through [https://github.com/kjliew/qemu-3dfx#donation ($)]
|{{~}}
|-
|[[QEMU]]+'''KVM''' or '''WHPX'''
|align=left|{{Icon|Linux|Windows}}<ref>[https://github.com/matthias-prangl/qemu-virgl-winhost Repository to help build qemu with virgl support for windows hosts].</ref>
|[https://docs.mesa3d.org/drivers/virgl.html VirGL]
|{{✗}}
|}
[https://github.com/jamesstringerparsec/Easy-GPU-PV#prerequisites "Hyper-V + GPU-P" exclusive to Windows 10/11 host and guest systems at the moment]. So you don't have any option other than "QEMU-3dfx with WHPX" OR "Type 2 hypervisors" for current Windows hosts at the moment.
QEMU VirGL '''only for Linux guests''' [https://wiki.archlinux.org/title/QEMU#virtio "with 4.4=> kernel with mesa (>=11.2) compiled with the option gallium-drivers=virgl"] at the moment. Plans are to target GL2.1 + GLSL 1.20 as the possible lowest GL interface to support. The guest would then expose the same level of GL. Currently the renderer is GLSL 1.30 based, and requires some extensions from later GL levels. I’ve only really tested on the open source nouveau driver exposing GL3.0/GL3.1 core profile, and the binary nvidia driver exposing GL 4.3. Future plans to add a capabilities system will be required to work make things work across more systems. The capabilities system will expose different guest GL levels dependant on the host GL level, this could allow for a GLES2 specific interface etc. The current guest driver exposes GL2.1 and GLSL 1.20. For more information about VirGL3D [https://virgil3d.github.io/questions.html use this link].
;Videos;<br/>
