Because we’ve had several recent posts about deploying openSUSE as a Guest on MSWindows Hyper-V,
I collected the necessary resources to do so properly and added the following to my Wiki
https://en.opensuse.org/User:Tsu2/openSUSE_Guest_on_Hyper-V
One major change from the references compared to what has been posted in these Forums is that there should not be a need to find special drivers for deploying on Hyper-V. Apparently LIS drivers from Microsoft are automatically distributed and installed for all Linux similar to how Guest enhancements are provided for all(or most?) virtualization technologies.
Also,
While doing this I looked up updated articles on Hyper-V and I now would categorize it more as a Type 1 virtualization architecture (similar to Xen) than as a Type 2 (like Virtualbox, KVM, and VMware). Although MS has modified the architecture somewhat compared to Xen, what MS calls its virtualization “partition” (not to be confused with the disk partition) is largely comparable to the Xen Dom, and there is a MS “root partition” which is comparable to Xen’s Dom0.
I suspect that this Hyper-V architecture might be a result of the famous technology exchange between Xen and Microsoft (2006?) when Xen gave Microsoft access and rights to substantial parts of its virtualization in exchange for similar access and rights to the vast Windows drivers library… I just was never entirely clear on how much technology MS utilized, and it appears more than I realized.
As long as I was looking at this “Type 1 vs Type 2” which seems to come up time and again, I also reviewed the VMware ESXi claim to be a Type 1,
And, I continue to believe that’s a mis-characterization (even despite VMware’s claims). There is no dispute about VMware’s ESX(Now called VSphere), it is unquestionably a Type 2, only whether ESXi which is described as a “bare metal hypervisor” as though whatever that is supposed to mean is supposed to be the differentiating factor.
A close inspection of ESXi’s architecture reveals nothing comparable to Xen’s Dom0 or MSWindows’ Hyper-V root partition. But, because VMware deploys its OS stub more like firmware as largely read-only modules, the OS is not likely subject to attacks against typical OS… In some ways, the Read Only aspects are comparable to our openSUSE Transactional Server (Should openSUSE try marketing Transactional Server as firmware? IMO not!). So, with its small attack surface and lack of typical OS vulnerabilities, VMware might be able to claim “bare metal” type security, but IMO that doesn’t make it a Type 1.
Anyway…
Enjoy, and now anyone deploying on Hyper-V should now be able to do so with reliable reference documents.
TSU