[New Feature]: Upgrade manual validation hardware

[superusercode]

Description of the new feature/enhancement

The absence of support for newer versions of opengl and lack of an audio driver on the manual validation VM causes launch errors that are specific to the pipeline and would not happen in the real world or even on a self set-up clean VM i.e. virtualbox (making this hard for new contributors to preemptively test for). This blocks PRs like #107110 #107333 #107211 #106964 #107075 and would have blocked developer tools like #107422 if not for the latter clearly stating it requires opengl 3.3+ - supported on GPUs in the last five years and near ubiquitous on windows 11. Open source programs and games lean on the newer side of opengl support since mesa is the default graphics package for most of their Linux users, so this may become a more common issue for some of the packages already in winget.

Proposed technical implementation details (optional)

A better gpu driver and an audio device would resolve these issues.

[stephengillie]

Some research notes:

• Add-VMRemoteFx3dVideoAdapter -VMName
• https://social.technet.microsoft.com/wiki/contents/articles/31771.server-2016-experience-guide-enabling-opengl-support-for-vgpu.aspx
• https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/deploy-graphics-devices-using-remotefx-vgpu

[stephengillie]

The host may require some modification:

WARNING: We no longer support the RemoteFX 3D video adapter. If you are still using this adapter, you may become vulnerable to security risks. Learn more (https://go.microsoft.com/fwlink/?linkid=2131976)
Add-VMRemoteFx3dVideoAdapter: Hyper-V cannot add a RemoteFX 3D video adapter to this virtual machine. To add this adapter, the host must have at least one graphics processing unit (GPU) that supports RemoteFX and that meets the minimum requirements for DirectX.

• One eventual outcome of the above link: https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/deploying-graphics-devices-using-dda

[stephengillie]

Related: Request to revert Manual Validation pipeline to Windows 10, except for situations where MinimumOSVersion demands Windows 11.

[stephengillie]

Related: Request to revert Manual Validation pipeline to Windows 10, except for situations where MinimumOSVersion demands Windows 11.

Windows 10 pipeline VMs operational, completing this section.

[superusercode]

What's the exact MinimumOSVersion of windows 11 to force the validation pipeline to use it?

[stephengillie]

For the Manual Validation pipeline, I'm currently using 10.0.22000.0. I believe the Automatic Validation pipeline uses the same value.

(The Manual Validation pipeline is a ~1300 LOC PowerShell module that orchestrates minimally-modified VMs. It's currently hosted in a private repo, but I'd be happy to work to release it through a public Microsoft repository. I'm unsure of the best home for it.)

[superusercode]

I think it would make sense for it to live in the Tools directory with the other powershell scripts, but if it becomes more common for issues to be filed against the validation environment then I think it would be better for it to have its own repository.

[stephengillie]

This sounds like a good location.

• One complication I'll have to work around is that the PR Watcher is in one branch, while this will be in another branch. But the PR Watcher depends on the Manual Validation pipeline for full functionality, to run multiple new package examinations while validating moderator-approving packages. The PR Watcher code might be moved into the Manual Validation pipeline, and its branch abandoned. Unless there's a way of which I'm unaware, to reference one branch as a dependency of another branch.

[stephengillie]

In-PR:

• Adding Manual Validation Pipeline. #110987

[stephengillie]

Need 32-bit OSes:

• New version: Datronicsoft.SpacedeskDriver.Client version 0.9.4200.0 #117891

[stephengillie]

For reference: Winget List installed packages: