After reading this article and this article about current controversy between VMware and Xen on how to implement virtualization in the Linux kernel, I believe it’s meaningful to quote the original VMware proposal:
Unlike the full-virtualization techniques used in the traditional VMware products, paravirtualization is a technique where the operating system is modified to enlighten the hypervisor with timely knowledge about the operating system’s activities. Since the hypervisor now depends on the kernel to tell it about common idioms etc, it does not need to write protect OS objects such as page and descriptor tables as a solution based on full-virtualization needs.
This has two important effects (a) it shortens the critical path, since faulting is expensive on modern processors (b) by eliminating complex heuristics the hypervisor is simplified. While the former delivers performance, the latter is quite important too.
Not surprisingly, paravirtualization’s strength, ie that it encourages tighter communication between the kernel and the hypervisor, is also its
weakness. Unless the changes to the operating system are moderated, you can very quickly find yourself with a kernel that (a) looks and feels like a brand new kernel or (b) cannot run on native machines or on newer versions of the hypervisor without a full recompile. The former can impede innovation in the Linux kernel, and the latter can be a problem for software vendors.
VMware proposes VMI as a paravirtualization interface for Linux that
solves these problems.
- A VMI’fied Linux kernel runs unmodified on native hardware, and on many hypervisors, while simultaneously delivering on the performance promise of paravirtualization.
- VMI has a rich and low level interface, which allows the kernel to cope with future hardware evolution by querying for hardware capability. It is our expectation that a single kernel will run unmodified on both today’s processors with limited hardware virtualization support and also keep up with any evolution on the processor front.
- VMI Linux is a fairly clean interface, with distinct name spaces for objects from the kernel and the hypervisor. Nowhere do we mingle names from the hypervisor with that of the kernel. This separation allows innovation in the kernel to proceed at the same speed as always. For most kernel developers, a VMI kernel looks and feels like a regular Linux kernel.
- VMI Linux still supports “native” hypervisor device drivers, for example a hypervisor vendor’s own private network or block device drivers which are free to use any interface desired to communicate with the hypervisor.
Be sure to read the whole ongoing thread for having a complete picture of VMware and Xen positions.
If you are interested you can find the draft VMI documentation inside the thread here.
blog comments powered by Disqus
virtualization.info Newest articles
February 9th, 2017
“We see greater potential strategic opportunity in NSX over the next decade than our franchise product vSphere has had for the past decade.”
said VMware’s CEO Pat Gelsinger talking about…
November 22nd, 2016
Encryption of virtual machines is something that has been requested for years by the security community. VMware continued to postpone its implementation due to the negative operational impact that many…
November 1st, 2016
In September 2012 Dell announced to have completed the acquisition of Quest Software, a Californian company with an history in systems management, security, business intelligence and, falling back in our…
October 21st, 2016
Citrix announced its financial results for third quarter 2016.
The revenues for the second quarter were $841 million for an increase of 3% compared to Q3 2015.
Net income was $132…
October 19th, 2016
2016 edition of VMworld US has been quite turbulent, on the other hand during VMworld Europe, happening these days in Barcelona, the company announced a few more products for the…
October 18th, 2016
Log Insight is a log aggregation, management and analisys tool, that VMware first introduced in 2013 and now is usually compared with Splunk.
Yesterday VMware announced Log Insight’s new major…
October 13th, 2016
Yesterday Microsoft announced the general availability of Windows Server 2016 which the company defines as a cloud-ready OS.
Beside fancy definitions, one of the most relevant perks of this release…
September 22nd, 2016
During Oracle OpenWorld 2016 the company released version 3.4.2 of its enterprise virtualization solution.
Oracle VM is available for both x86 and SPARC based processor architectures and uses the Xen hypervisor…
September 1st, 2016
Today was the last day of VMware’s flagship conference VMworld in Las Vegas, an highly controversial edition which left a good chunk of the audience disoriented if not properly disappointed….
August 11th, 2016
Last week Gartner updated its Magic Quadrant for Cloud Infrastructure as a Service (IaaS) for the year 2016. The Magic Quadrant for the year 2015 was released in May last year…
August 2nd, 2016
Ansible is one of the four main players in the automation market, younger then the well known Chef and Puppet, has been launched in 2013 in Durham, N.C. and acquired…
July 19th, 2016
Yesterday IBM announced its results for Q2 2016.
If we compare with the same quarter in 2015 earnings per share, from continuing operations, decreased 22%. Net income, from continuing operations,…
June 24th, 2016
Red Hat announced its financial results for the first quarter of fiscal year 2017.
Total revenue for the first quarter was $568 million, with an increase of 18% from the…
June 24th, 2016
Today Red Hat released in beta version 4.0 of its KVM-based virtualization platform Red Hat Enterprise Virtualization (RHEV).
As a major release RHEV 4.0 ships a wide series of enhancements including: