我们对合并和分叉模型进行了修改，使多任务系统可以方便地通过操作系统管理程序进行调度。
In order to make the multitask scheduling be realized by system management scheduler of the Operating system, modified solutions for join and fork models are presented.
对这些Linux组件进行优化(例如2.6版本内核中的新o(1)调度程序)都可以让系统管理程序(主机操作系统)和Linux客户操作系统同时受益。
Optimizations to these Linux components (such as the new o (1) scheduler in the 2.6 kernel) benefit both the hypervisor (the host operating system) and the Linux guest operating systems.
在某些情况中，这个系统管理程序就是一个操作系统；此时，它就称为主机操作系统，如图1所示。
In some cases, the hypervisor is an operating system; in this case, it's called the host operating system, as shown in Figure 1.
系统管理程序之上是客户机操作系统，也称为虚拟机(VM)。
Above the hypervisor are the guest operating systems, also called virtual machines (VMs).
这是因为每个客户操作系统都了解自己正在虚拟化模式中运行，因此每个系统都与系统管理程序协作，来实现底层硬件的虚拟化。
This is because each guest operating system is aware that it's being virtualized, so each cooperates with the hypervisor to virtualize the underlying hardware.
当操作系统检测到一个线程空闲时，把对硬件的控制权交还给系统管理程序，这会使线程进入 nap模式。
The way it works is that the OS detects when a thread is idle and then gives control of the hardware back to the hypervisor, which puts the thread into nap mode.
使用内核作为一个系统管理程序，您就可以启动其他操作系统，例如另一个Linux内核或Windows系统。
With the kernel acting as a hypervisor, you can then start other operating systems, such as another Linux kernel or Windows.
这种技术本身使用基于系统管理程序的解决方案(这是IBM最终通过Xen实现的，但是只在x86平台上使用)，它位于操作系统和硬件之间。
The technology itself USES a hypervisor-based solution (which IBM has finally implemented though Xen, but only on their x86 platform), which sits between the operating system and the hardware.
这种技术本身使用基于系统管理程序的解决方案(这是IBM最终通过Xen实现的，但是只在x86平台上使用)，它位于操作系统和硬件之间。
The technology itself USES a hypervisor-based solution (which IBM has finally implemented though Xen, but only on their x86 platform), which sits between the operating system and the hardware.
应用推荐