3 ms·
Can you explain this? Afaict hyper-v is the same as VMware or virtual box where you have a host OS and multiple guest OSes (which makes sense because you still
by vlovich123 5y ago
Can you explain this? Afaict hyper-v is the same as VMware or virtual box where you have a host OS and multiple guest OSes (which makes sense because you still need something to run the OS drivers). It sounds like what you’re implying is it behaves differently but I’m not sure how. Can you elaborate?
- pjmlp 5y agoWindows runs as guest OS on top of Hyper-V as well, it is a type 1 hypervisor. Basically when you activate Hyper-V, you will be getting one VM running where the host is only a guest with special privileges known as root partition.
- bpye 5y agoHyper-V is similar to Xen. The hypervisor runs on bare metal, the Windows root is akin to your dom0 on Xen, and your guests are your domU.
- vlovich123 5y agoOk, but then I still don’t understand this piece: > If they are running on Hyper-V on Azure, there is no underlying kernel doing anything. In a Xen model as I understand it, the dom0 kernel is still actually responsible for talking to all the hardware directly and presenting a virtualized implementation that Xen can mux other guests on, no? So there’s still a kernel there and it’s doing quite a bit of work, no?
- bpye 5y agoThe dom0 kernel is responsible for talking to devices such as a disk or a NIC, yes, be that Linux, NT, *BSD, etc. The hypervisor is typically responsible for enforcing isolation of compute, memory, etc. The line does blur - for example Hyper-V may be configured with something called the “root scheduler” with which NT is responsible for scheduling virtual CPUs [0] - though the hypervisor is still enforcing the isolation. [0] - https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/manage-hyper-v-scheduler-types#hypervisor-scheduler-types https://docs.microsoft.com/en-us/windows-server/virtualizati...