Hyper-v On Windows 10 Type 1 Or 2
Karl Meinhardt
With Microsoft Hyper-V, you can virtualize server operating systems in the data center or Windows phone environments on your desktop and most everything in between. It is also a great tool for developers that want a safe sandbox to test software.
When Microsoft Hyper-V debuted in 2008, virtualization was just beginning to become mainstream. Not many people knew what it was, and even fewer understood what they could do with it. It all seemed conceptually complicated, risky, and challenging to implement and maintain.
Each vendor offers additional products above and beyond the base product, notably System Center from Microsoft and vSphere from VMware. These two product suites differ quite radically in most metrics and are difficult to compare directly. Here are a few noteworthy items where Hyper-V is the clear winner:
For purposes of this article, we will focus on the general benefits of virtualization and highlight the particular features that are found in Windows Server with the Hyper-V role or with the free Hyper-V Server.
Hyper-V also provides a great deal of portability to your server-based applications. They can be easily moved to new hardware with little or no downtime. Workloads can be rebalanced if hardware becomes overloaded, or they can be quickly recovered on another system if hardware fails. The VHDX file format that Hyper-V uses to hold virtual machine data can be mounted by any current Windows operating system so you can recover data quickly and easily. Microsoft also allows customers to upload their own Azure-compliant VHDs and create Azure images for deployment.
With a physical infrastructure already in place, new operating system environments can be deployed from templates in a few minutes, drastically reducing the time necessary to provision and deploy a new Windows Server or Linux installation. DevOps tools such as PowerShell, Terraform, Ansible, and other tools can be used to interact with virtualized environments to further automate virtualized environments.
With the rapid provisioning and isolation features that are natural to Hyper-V, you can quickly design and deploy test and sandbox environments quickly. Disposing of them once testing has completed is even quicker. It makes testing patches, new applications, driver updates, and other tasks possible before rolling these into production.
All virtual machines running on a host or cluster can be viewed from a single pane using existing tools. For larger installations, management tools are available to monitor virtual machines across the entire datacenter. PowerShell and other tools enable mass simultaneous management of these systems.
Of all currently available virtualization platforms, Hyper-V Server is one of the few that has no price tag, regardless of the feature set. All features of Hyper-V are available in even the free edition, including failover clustering, multi-path I/O, Hyper-V Replication, and no artificial limits on CPU or memory utilization. While Hyper-V Server features are free, customers are responsible for the guest OS licenses running in the environment. Overall, it still provides a cost-effective solution for running specific workloads.
With the needs of a mobile workforce often exceeding the power of modern small devices, Hyper-V can provide a virtual desktop infrastructure (VDI) to supply high-powered desktop processing capabilities to low-powered laptops and handheld devices.
Client Hyper-V has one very important distinction among desktop hypervisors: it is a type 1 hypervisor whereas almost all others are type 2. A type 2 hypervisor is just an application that runs inside an operating system and is subjected to the same treatment as other applications, like Microsoft Outlook or a video game.
For your purposes, Client Hyper-V provides a much smoother performance profile than most competing desktop hypervisors. It also comes as a free, built-in component that requires no downloads, purchases, or separate update processes.
Microsoft has embraced the use of Client Hyper-V for other purposes, such as security, in the latest versions of Windows 10 & 11. In Windows 10 & 11, Microsoft leverages client-side virtualization technologies made possible by Hyper-V to instantiate Hypervisor-protected code integrity (HVCI). HVCI provides many security benefits, including:
As with any major technology group, virtualization has a long list of technical terms. Many of them are easy to understand when encountered in context, but some can be rather confusing, especially when not everyone uses them the same way. This list provides some of the most common terms and uses each of them in the same fashion as Microsoft documentation. In the interest of brevity, not all terms will be thoroughly explained here. Later material will explore all of these concepts in depth.
Hyper-V was first introduced with the 2008 series of Windows Server products. Since then, it has expanded its capabilities and added a significant number of features. In the current edition (Windows Server 2022), it is truly ready to power everything from a small business to a major enterprise.
As Microsoft continues to shift its focus to a Microsoft Azure cloud-driven ecosystem of products and solutions, it has detailed that Microsoft Hyper-V Server 2019 will be the last version of the free Hyper-V Server product in its current form. See the instructions on how to install Hyper-V on Windows Server 2019.
While Windows Server 2022 still includes the Hyper-V Role, there is no SKU for Hyper-V Server 2022. Instead, Microsoft is shifting to a new solution called Azure Stack HCI which is a cloud-licensed and delivered HCI solution that looks to be the roadmap for the Microsoft hypervisor technology we know as Hyper-V today.
Second-level address translation is a required feature for Client Hyper-V. It is not required for any server version of Hyper-V, but it is highly desirable. Memory operations, especially video, are greatly enhanced by this technology. This technology also has different names on different platforms. Intel refers to it as Rapid Virtualization Indexing (RVI) or Extended Page Tables (EPT). AMD calls theirs Nested Page Tables (NPT). As with DEP and hardware-assisted virtualization, SLAT has become very common.
These resources will allow you to explore the potential of Hyper-V. For a more comprehensive discussion of hardware usage in Hyper-V, refer to the following article: -v/hyper-vs-actual-hardware-requirements/.
Virtualizing and consolidating workloads leads to many advantages, including reduced energy demands, increased portability, rapid deployment, ability to easily provision lab environments, reduced management efforts, licensing savings, VDI capabilities, and many others.
Hyper-V capabilities are also built into Windows client operating systems, including Windows 10 and Windows 11. It allows running guest virtual machines on a Windows client machine. It is a great feature that is useful for development, browsing VMs, and many other use cases.
The Hyper-V platform continues to evolve and grow over time as Microsoft is further integrating Hyper-V capabilities into the SaaS Azure offerings, such as Azure Stack HCI and others. By making use of Hyper-V, organizations can modernize their enterprise data centers and successfully deploy hybrid cloud solutions.
1.) System Support Utility(SSU) log of your system. This will allow us to check your Adapter details and configuration. This would also help us identify if you are using an OEM or retail version of Intel Ethernet Adapter. Kindly refer to the steps below.
Please note that I was initially forcibly updated to 2.1.3.15 via Windows Update, so even if the OEM version worked it would still not be a good long-term solution if I need to manually rollback drivers after every update.
Thank you for your patience. It appears that the default or original inbox driver version (1.0.2.8, 1.0.2.14) worked till there is a windows/new update. Inbox driver usually came specifically from Original Equipment Manufacturer (OEM) / Asus' customization to ensure it works accordingly at minimum state (which is expected).
Please be aware, we should only use the software application that came with the Asus system to perform the update, but in hyper V environment, we many need to investigate the minidump or the changes happened after post update with the later drivers.
I do not believe we are being given a choice in this update, as it has been pushed down by Windows Update automatically. As far as I can tell, this appears to be pushed down by WU under the branding of Intel, with no involvement from Asus. Notably, it is actually a different version from the one provided by Asus (which also does not work for this purpose).
Just to be clear: to me it looks like Intel is providing the drivers to Microsoft, who are then pushing them down via Windows Update and in this process breaking previously working vSwitch setups, all automatically. I did not initiate this update process. I would have been fine staying on the older working version, if I had a choice in the matter.
Please note that although my primary environment is running under a Hyper-V hypervisor, the fresh test setup I was using was not. It was only using Hyper-V services to provide the vSwitch and vNICs, but the OS itself was running bare-metal (i.e. no hypervisor was involved). This issue has nothing to do with virtualisation itself, but is solely an interaction between the new drivers and the vSwitch/vNIC.
Since I can already see this becoming an endless back-and-forth (where you insist this is an OEM issue, and Asus will likely insist it is not), could you please tell me if there is any way I can convince you otherwise? If I purchase a non-Asus PCIe card with an I-225V on it and manage to reproduce the issue there, will you again tell me that it is an OEM issue?
I can also confirm this issue with a I226-V PCI-e card. VLAN on Hyper-V Switch/Adapter doesn't work with any 2.x version driver; but works fine on the latest 1.x driver which is currently version 1.1.4.42 from the 28.2.1 driver package. Also Wake-on-LAN is not working with both versions.
d3342ee215