Rachel’s information is absolutely accurate.
RemoteFX virtual graphics adapter uses an API interception mechanism that translates API calls from the Microsoft driver in the guest VM and passes those calls to the hardware driver in the Hyper-V host.
What you see with the K2 is the Microsoft driver intercepting and translating those API calls and passing them to the Nvidia driver in the Hyper-V host.
It’s also worth noting a couple of things
The Remote FX virtual graphics adapter is only enabled in fully featured RemoteFX sessions, any other connection method disables it.
It’s also limited to DirectX, OpenGL is not supported in the 2012R2 release ( Server 2016 does though). So I’m surprised you’re seeing Solidworks use the GPU (it may be running on CPU at a very low feature level).
Anyhow, you asked about M60 support for Hyper-V.
In the case of the M60 there is currently no official support for bare metal deployments, which this type of installation is becasue it’s installed into Server 2012R2 (no support for core services, you must have the GUI).
There are several reasons for this which may change in the future.
However, if you’re happy testing out an unsupported feature, the Tesla M60 can technically be used with Hyper-V 2012R2 to deliver the virtual graphic functionality. You will need an additional graphics adapter in the host to install your OS and you will still require a license for each running VM at the level of vPC Edition. Once you have these licenses and hence access to the license portal you will be able to download the GRID for Windows drivers. Evaluation licenses are available btw.
With the upcoming release of Server 2016 Nvidia plans to support Tesla M60, M6 and the newly announced M10 boards for DDA. This feature has been available for trial since Server 2016 TP4, so with the same drivers as above you can test the functionality.
If you have an M60 card and require evaluation licenses, you can request them here: