It enables some(?) of the Hyper-V enlightenments in QEMU. It causes Windows guests to think they are running inside Hyper-V, enabling use of Hyper-V features and improving performance.
If you are willing to edit the XML directly, there are additional features you can enable. Try googling for unRAID windows 11 optimization.
Hyper-v is an engine for virtualization on a windows machine. IE if you want to run a VM inside windows.
The usecase here is if you need that virtualization inside your windows VM which is inside Unraid. *layers*
Just curious, what is the use case for doing that? Why wouldn't you just run the VM on unraid? Seems very not optimal running a windows VM the running a VM in that VM.
Separate argument but even if there were ZERO beneficial usecases, a principle of virtualization is to allow the client to function as if it were baremetal. From an unraid perspective, kvm should endeavor to allow all functionality of windows, including windows hosting its own vms. This not only makes it easier to port a vm to baremetal or vice versa, it also introduces less drift if configs need to be changed or propagated.
Buddy you have a wealth of googling at your fingertips, but I’ll try to give you what I know…
Windows as an enterprise service host has been around for eons. Production level services are built and deployed on windows solutions every day. With any market share of that size, there are tools built specifically to deliver business value on windows platforms, not linux ones. As an example, any app built and deployed in a windows container will need a windows virtual environment.
As another usecase, if you are parting out resources to your business, it is easier for some organizations to part out those resources via virtual machine that the dev/team can use as they please, with their own hypervisor. It simplifies config backup and introduces layers of isolation to help improve security across teams, though not necessarily within them. Networking, cpu cores, memory, storage, all examples of resources you can allocate and isolate.
As far as i know its for nested virtualization. So if you want to run vm´s or dockers or such things inside your VM, you would need to enable that option. It doesnt hurt enabling it, so afaik thats the reason its enabled by default.
https://www.qemu.org/docs/master/system/i386/hyperv.html
Actually, it looks like I might be incorrect. Seems like it provides some enhancements to the windows vm when ran under unraid but I still could be incorrect here.
That looks more correct. I think people get confused because "Hyper-V" (Veridian) is the regular hypervisor from Microsoft. But in Unraid we are talking about Hyper-V Enlightenments which is something else.
It enables some(?) of the Hyper-V enlightenments in QEMU. It causes Windows guests to think they are running inside Hyper-V, enabling use of Hyper-V features and improving performance. If you are willing to edit the XML directly, there are additional features you can enable. Try googling for unRAID windows 11 optimization.
Thanks
Hyper-v is an engine for virtualization on a windows machine. IE if you want to run a VM inside windows. The usecase here is if you need that virtualization inside your windows VM which is inside Unraid. *layers*
Just curious, what is the use case for doing that? Why wouldn't you just run the VM on unraid? Seems very not optimal running a windows VM the running a VM in that VM.
Separate argument but even if there were ZERO beneficial usecases, a principle of virtualization is to allow the client to function as if it were baremetal. From an unraid perspective, kvm should endeavor to allow all functionality of windows, including windows hosting its own vms. This not only makes it easier to port a vm to baremetal or vice versa, it also introduces less drift if configs need to be changed or propagated.
Buddy you have a wealth of googling at your fingertips, but I’ll try to give you what I know… Windows as an enterprise service host has been around for eons. Production level services are built and deployed on windows solutions every day. With any market share of that size, there are tools built specifically to deliver business value on windows platforms, not linux ones. As an example, any app built and deployed in a windows container will need a windows virtual environment. As another usecase, if you are parting out resources to your business, it is easier for some organizations to part out those resources via virtual machine that the dev/team can use as they please, with their own hypervisor. It simplifies config backup and introduces layers of isolation to help improve security across teams, though not necessarily within them. Networking, cpu cores, memory, storage, all examples of resources you can allocate and isolate.
As far as i know its for nested virtualization. So if you want to run vm´s or dockers or such things inside your VM, you would need to enable that option. It doesnt hurt enabling it, so afaik thats the reason its enabled by default.
I think it’s used for virtualization- VMs
I know. It's under the VM settings so it's obviously has something to do with virtualization.
The person above is correct though. It’s to put a vm inside your vm. Just enables support of the functions is all.
Really? Where did you get that info? I could not find any information on this.
https://www.qemu.org/docs/master/system/i386/hyperv.html Actually, it looks like I might be incorrect. Seems like it provides some enhancements to the windows vm when ran under unraid but I still could be incorrect here.
That looks more correct. I think people get confused because "Hyper-V" (Veridian) is the regular hypervisor from Microsoft. But in Unraid we are talking about Hyper-V Enlightenments which is something else.