Windows 10 Hyper-V Impact on Gaming
-
@emad-r said in Windows 10 Hyper-V Impact on Gaming:
instead of virtual drivers talking to the GPU, why you dont want to consider GPU pass-through ? and dedicate it to specific VM. going this route you can choose any modern hypervisor
It's an existing Windows box that only needs to run Steam 99% of the time. Was only looking to get a little additional visualization use out of it on rare occasion for testing use. Installing any other hypervisor or moving the Windows workload to a VM would be very cumbersome. It's 2TB in size.
-
Realize this post is old, but just want to clear up some possible confusion you may have about Hyper-V. Adding the Hyper-V role on a Windows 10 system will not make the host OS a child role. The Win10 system will now act as the parent role which is a VM that has direct access to hardware in contrast to child roles that accesses virtualised hardware - the two are not the same or interchangeable. Therefore, no gaming performance hit should even be noticable on that level. The shared performance on CPU/RAM/Disk is an issue you'd have to evaluate and prioritize though.
Point is, the parent OS has direct hardware access, not virtualized. It's not a child VM like the ones you create afterwards. Microsoft documents this well.
-
@osva said in Windows 10 Hyper-V Impact on Gaming:
Point is, the parent OS has direct hardware access, not virtualized. It's not a child VM like the ones you create afterwards. Microsoft documents this well.
It may have direct access, but it is absolutely virtualized. Direct access is not the same as not being virtualized. There is no question that it is virtual. It has to be or Hyper-V can't be there.
-
@osva said in Windows 10 Hyper-V Impact on Gaming:
Realize this post is old, but just want to clear up some possible confusion you may have about Hyper-V. Adding the Hyper-V role on a Windows 10 system will not make the host OS a child role. The Win10 system will now act as the parent role which is a VM that has direct access to hardware in contrast to child roles that accesses virtualised hardware - the two are not the same or interchangeable. Therefore, no gaming performance hit should even be noticable on that level. The shared performance on CPU/RAM/Disk is an issue you'd have to evaluate and prioritize though.
Point is, the parent OS has direct hardware access, not virtualized. It's not a child VM like the ones you create afterwards. Microsoft documents this well.
First you have the hardware...
then you have the hypervisor that sits directly on top of that and has direct access to the hardware. This is ring -1. (minus one)
Then you have Ring 0 where the VSP / VM BUS / Drivers sit.
Now, here's where you have Ring 3, which is where the management OS AND the child partitions sit..
-
But definitely, that it is the parent VM (Dom0 as old timers call it) and not a child VM (DomU) is important for performance. It has priority.
-
The child partitions communicate directly with the hypervisor in modern operating systems. In Windows XP or VMs without Hyper-V Tools for example, they go through the "management OS".
-
@obsolesce It's called paravirtualization. And Xen has done it since the 1990s
Only Xen could do it for the entire VM, not just the drivers.
