4 ms·

Is the process of unlocking these features on Nvidia GPUs similar to something like the vgpu_unlock tool is doing?[1] No affiliation, just came across it trying

Is the process of unlocking these features on Nvidia GPUs similar to something like the vgpu_unlock tool is doing?[1] No affiliation, just came across it trying to find a replacement to the deprecated RemoteFX vGPU and am out of my depth. [1]https://github.com/DualCoder/vgpu_unlock https://github.com/DualCoder/vgpu_unlock

my123 5y ago
For replacing RemoteFX vGPU, what you might want is https://forum.level1techs.com/t/2-gamers-1-gpu-with-hyper-v-gpu-p-gpu-partitioning-finally-made-possible-with-hyperv/172234 https://forum.level1techs.com/t/2-gamers-1-gpu-with-hyper-v-... (which is the direct successor) The advantage is that it ships inbox in Windows and doesn't need license hacks or anything. It works cross-vendor too. However, it needs the host OS to be Windows (with Hyper-V being used).
- kipchak 5y ago
  Interesting! News to me, the Microsoft documentation I was looking at didn't make any mention of GPU-P but that seems like a perfect fit. Was looking at a old Grid K2 to avoid Nvidia licensing and direct pass through for high use VMs but as we're full Microsoft (for better or worse) their solution probably makes more sense. edit - apparently while this works on Server 2019 direct pass through is the only officially "supported" option. I wonder if this is a stepping on partners' toes sort of situation?
  - my123 5y ago
    GPU-P is also the GPU acceleration infrastructure used for GPU acceleration in WSL2 and for Windows Sandbox too.
  - ArcVRArthur 5y ago
    I'm not entirely sure on how wide the vendor support is but I wouldn't be entirely surprised if they were upsetting some folks with it. Happily we're just a little team right now making stuff that's useful for ourselves so we don't have all the same pressures big companies have. I hope if we ever grow we'll act in the same spirit (I'll try my best to see that we do anyway).
- ArcVRArthur 5y ago
  I think Hyper-V is GPU-P is great! I think Microsoft's hypervisor team is one of the most talented in the world, and honestly I think I could learn a lot from them. One of the benefits to using our approach instead of Microsoft's is that our tools are free open source software and (my biased opinion) I think we have an easier user setup. :) Some day I would love to read Hyper-V's GPU-P code as I think they did a rather good job overall.
ArcVRArthur 5y ago
vGPU_Unlock's Merged driver is an optional package you can include but if you don't want to use it there's no explicit dependance. We actually enable these features using a vendor neutral API called VFIO-Mdev: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/tree/Documentation/driver-api/vfio-mediated-device.rst?h=driver-core-next&id=7de3697e9cbd4bd3d62bafa249d57990e1b8f294 https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/drive... Here's a few examples of YAML for use with different GPU vendors: Intel: https://github.com/Arc-Compute/libvf.io/blob/master/example/intel-mdev.yaml https://github.com/Arc-Compute/libvf.io/blob/master/example/... Nvidia: https://github.com/Arc-Compute/libvf.io/blob/master/example/nvidia-mdev.yaml https://github.com/Arc-Compute/libvf.io/blob/master/example/... AMD: https://github.com/Arc-Compute/libvf.io/blob/master/example/amd-mdev.yaml https://github.com/Arc-Compute/libvf.io/blob/master/example/... The odd one out is AMD that uses a different API due to the fact that the vendor has largely ignored standard open source interfaces in the kernel. We're still supporting that API but unfortunately there are very few AMD cards that work due to the fact that they refuse to release open source code to support their newer cards and they have locked out these features at the firmware level on consumer cards. Fortunately Nvidia and Intel GPUs are very well suited to this functionality and we've got support for most recent consumer cards from both!
- InvaderFizz 5y ago
  It would be helpful to note that Intel GVT-g is a dead end with 10th gen Comet Lake being the end of the road[0]. They do not support it with XE and have instead decided to go with SR-IOV. I'm curious to see if this could be used in virtualizing macOS with GVT-g for 3D accelerated guests. I know that this was looked at a few year ago and no one had made it work then. 0: https://github.com/torvalds/linux/blob/2f111a6fd5b5297b4e92f53798ca086f7c7d33a4/drivers/gpu/drm/i915/intel_gvt.c#L44-L60 https://github.com/torvalds/linux/blob/2f111a6fd5b5297b4e92f...
  - ArcVRArthur 5y ago
    Based on my reading of the link you provided I don't believe support for GVT-g has been removed. You can see the GVT-Linux repository is also still receiving commits: https://github.com/intel/gvt-linux https://github.com/intel/gvt-linux

my123 5y ago

For replacing RemoteFX vGPU, what you might want is https://forum.level1techs.com/t/2-gamers-1-gpu-with-hyper-v-gpu-p-gpu-partitioning-finally-made-possible-with-hyperv/172234 https://forum.level1techs.com/t/2-gamers-1-gpu-with-hyper-v-... (which is the direct successor) The advantage is that it ships inbox in Windows and doesn't need license hacks or anything. It works cross-vendor too. However, it needs the host OS to be Windows (with Hyper-V being used).

kipchak 5y ago
Interesting! News to me, the Microsoft documentation I was looking at didn't make any mention of GPU-P but that seems like a perfect fit. Was looking at a old Grid K2 to avoid Nvidia licensing and direct pass through for high use VMs but as we're full Microsoft (for better or worse) their solution probably makes more sense. edit - apparently while this works on Server 2019 direct pass through is the only officially "supported" option. I wonder if this is a stepping on partners' toes sort of situation?
- my123 5y ago
  GPU-P is also the GPU acceleration infrastructure used for GPU acceleration in WSL2 and for Windows Sandbox too.
- ArcVRArthur 5y ago
  I'm not entirely sure on how wide the vendor support is but I wouldn't be entirely surprised if they were upsetting some folks with it. Happily we're just a little team right now making stuff that's useful for ourselves so we don't have all the same pressures big companies have. I hope if we ever grow we'll act in the same spirit (I'll try my best to see that we do anyway).
ArcVRArthur 5y ago
I think Hyper-V is GPU-P is great! I think Microsoft's hypervisor team is one of the most talented in the world, and honestly I think I could learn a lot from them. One of the benefits to using our approach instead of Microsoft's is that our tools are free open source software and (my biased opinion) I think we have an easier user setup. :) Some day I would love to read Hyper-V's GPU-P code as I think they did a rather good job overall.

ArcVRArthur 5y ago

vGPU_Unlock's Merged driver is an optional package you can include but if you don't want to use it there's no explicit dependance. We actually enable these features using a vendor neutral API called VFIO-Mdev: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/tree/Documentation/driver-api/vfio-mediated-device.rst?h=driver-core-next&id=7de3697e9cbd4bd3d62bafa249d57990e1b8f294 https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/drive... Here's a few examples of YAML for use with different GPU vendors: Intel: https://github.com/Arc-Compute/libvf.io/blob/master/example/intel-mdev.yaml https://github.com/Arc-Compute/libvf.io/blob/master/example/... Nvidia: https://github.com/Arc-Compute/libvf.io/blob/master/example/nvidia-mdev.yaml https://github.com/Arc-Compute/libvf.io/blob/master/example/... AMD: https://github.com/Arc-Compute/libvf.io/blob/master/example/amd-mdev.yaml https://github.com/Arc-Compute/libvf.io/blob/master/example/... The odd one out is AMD that uses a different API due to the fact that the vendor has largely ignored standard open source interfaces in the kernel. We're still supporting that API but unfortunately there are very few AMD cards that work due to the fact that they refuse to release open source code to support their newer cards and they have locked out these features at the firmware level on consumer cards. Fortunately Nvidia and Intel GPUs are very well suited to this functionality and we've got support for most recent consumer cards from both!

InvaderFizz 5y ago
It would be helpful to note that Intel GVT-g is a dead end with 10th gen Comet Lake being the end of the road[0]. They do not support it with XE and have instead decided to go with SR-IOV. I'm curious to see if this could be used in virtualizing macOS with GVT-g for 3D accelerated guests. I know that this was looked at a few year ago and no one had made it work then. 0: https://github.com/torvalds/linux/blob/2f111a6fd5b5297b4e92f53798ca086f7c7d33a4/drivers/gpu/drm/i915/intel_gvt.c#L44-L60 https://github.com/torvalds/linux/blob/2f111a6fd5b5297b4e92f...
- ArcVRArthur 5y ago
  Based on my reading of the link you provided I don't believe support for GVT-g has been removed. You can see the GVT-Linux repository is also still receiving commits: https://github.com/intel/gvt-linux https://github.com/intel/gvt-linux