Hyper-V 虚拟设备简介

最新推荐文章于 2024-08-20 12:27:31 发布

yayong

最新推荐文章于 2024-08-20 12:27:31 发布

阅读量4.2k

点赞数

分类专栏： Linux 文章标签： hyper-v 虚拟化 Linux 内核

本文链接：https://blog.csdn.net/yayong/article/details/51311820

版权

本文介绍了Hyper-V虚拟机中的虚拟硬件，包括全虚拟化和para虚拟化的概念，以及三种设备类型：模拟设备、合成设备和直接通过设备。重点讨论了Linux内核在Hyper-V上的驱动支持，包括物理驱动和PV驱动的使用。此外，还提到了Hyper-V虚拟机在启动磁盘和PXE启动方面的限制。

摘要由CSDN通过智能技术生成

This article was firstly published from http://oliveryang.net. The content reuse need include the original link.

Similar with other virtualization technologies，Hyper-V creates a virtual platform for its virtual machine. This article tries to give an overview about the virtual platform provided by Hyper-V, and how Linux OS works in a guest VM. The contents here are limited to Hyper-V, but some basic virtualization concepts might be similar or same with other hypervisors.

1. Virtual Hardware in Hyper-V VMs

Every hypervisor actually defines a clear specification for a virtual hardware inventory provisioned for a guest VM. For Hyper-V, Emulated and synthetic hardware specification for Windows Server 2012 Hyper-V is a such kind of specification. In order to have better understandings of the specification, there are some key concepts need to be clarified.

1.1 Virtualization Types

Today, most of hypervisors provide two virtualization types,

Full Virtualization

If a VM is working under this mode, OS without any virtualization knowledge can run over VM very well, just like running over the bare-metal hardware. With this virtualization type, application running over legacy OS like old Linux, Windows, and DOS could be easily migrated to a VM.
Para Virtualization

When a VM is working under this mode, the OS must have the virtualization knowledge, which means the OS is modified for cooperating with underlying hypervisors. The mechanism that allows guest OS to cooperate with hypervisor is called by a special terminology: hypercall.

At early phases, Para Virtualization usually provides the better performance than Full Virtualization on x86 platform. However, after Intel/AMD introduced the Hardware-assisted Virtualization extensions, such as Intel VT-X and AMD-V, the Full Virtualization VM could perform better than Para Virtualization VM while running the CPU or memory bound workload. Today, the major performance overheads in Full Virtualization VMs are caused by IO bound workloads.

For this reason, most of guest OS uses a Hybrid way to get better performance,

For major kernel part, it leverages Hardware-assisted Virtualization which is still called Full Virtualization.
In order to get better IO performance, it supports a set of PV(Para Virtualization) Drivers to optimize the data path.