Support OpenGL for package validation.

[denelon]

Description of the new feature/enhancement

Add support for packages with a dependency on OpenGL.
Some packages require OpenGL. The validation environment does not currently support this as a dependency.

Proposed technical implementation details (optional)

Once support for package dependencies is enabled, the validation environment should be able to test packages with the OpenGL dependencies.

Examples:
#705
#1067

[latere-a-latere]

Thanks for the effort of making this issue, @denelon, but I just went to check out RemoteFX and apparently when I used it a year ago for #1067 it was already unsupported and being deprecated - And it has been fully removed in the April security update of this year.

Because of security concerns, RemoteFX vGPU is disabled by default on all versions of Windows starting with the July 14, 2020 Security Update and removed starting with the April 13, 2021 Security Update.

I'm gonna look into getting the alternative, Discrete Device Assignment (DDA) working under Windows 10, though I'm not quite sure if it's possible at all sinds the docs only talk about Windows Server 2016 and up.

If that's not going to work, well, then I don't know how we can possibly validate manifests for programs that require OpenGL inside the validation environment - the standard display driver simply doesn't cut it.

[denelon]

I guess I need to update the Issue. Thank you so much for digging into this!

[denelon]

We also have an interesting challenge with some device drivers requiring specific hardware to be present.

[latere-a-latere]

@denelon I've done a bunch of digging and from what I understand DDA is not available on desktop versions of Windows 10 - You can only use it on server 2016 and up.

The only solutions currently available to consumers are qemu and VirtualBox, as far as I am aware. Naturally this is far from ideal: it's hard if not impossible to migrate the win10 dev environment to these platforms (and probably against the license agreement) and I doubt you guys would want to built this into the pipeline.

Do you think you could ask the Hyper-V team if there is currently any way of getting opengl in Hyper-v to work on consumer editions of Windows?

[denelon]

I'll see if the team knows anyone who works on Hyper-v.

[jedieaston]

It's worth noting that Windows Sandbox supports graphics acceleration (see here for more info), so if you need a local environment to test packages that need OpenGL, that would work. There's a lot of limitations (one of these days I'm going to buy a ticket to Build so I can go ask the engineers responsible why I can't have more than one Sandbox open at a time, or even better, just create Hyper-V containers myself that have graphics), but it works. Tools\SandboxTest.ps1 is a good way to validate a package.

[latere-a-latere]

@jedieaston Unfortunately, even using a configuration file that has vGPU set to Enable I'm not getting any usable OpenGL:

The minimum version required is 2.0, anything lower than that doesn't really work for the majority of applications.

[denelon]

@jenatali and I just had a talk, this might be one option for getting openGL support in a VM:
https://devblogs.microsoft.com/directx/announcing-the-opencl-and-opengl-compatibility-pack-for-windows-10-on-arm/

[jenatali]

Yeah, right now you'd need the insider version of that package installed, but then it will enable OpenGL support on top of WARP (Windows Advanced Rasterization Platform), which is our D3D software renderer used in VMs with no hardware acceleration.