<P> A hypervisor provides the virtualization of the underlying computer system . In full virtualization, a guest operating system runs unmodified on a hypervisor . However, improved performance and efficiency is achieved by having the guest operating system communicate with the hypervisor . By allowing the guest operating system to indicate its intent to the hypervisor, each can cooperate to obtain better performance when running in a virtual machine . This type of communication is referred to as paravirtualization . </P> <P> In 2005, VMware proposed a paravirtualization interface, the Virtual Machine Interface (VMI), as a communication mechanism between the guest operating system and the hypervisor . This interface enabled transparent paravirtualization in which a single binary version of the operating system can run either on native hardware or on a hypervisor in paravirtualized mode . As AMD and Intel CPUs added support for more efficient hardware - assisted virtualization, the standard became obsoleted and VMI support was removed from Linux kernel in 2.6. 37 and from VMware products in 2011 . </P> <P> At the USENIX conference in 2006 in Boston, Massachusetts, a number of Linux development vendors (including IBM, VMware, Xen, and Red Hat) collaborated on an alternative form of paravirtualization, initially developed by the Xen group, called "paravirt - ops". The paravirt - ops code (often shortened to pv - ops) was included in the mainline Linux kernel as of the 2.6. 23 version, and provides a hypervisor - agnostic interface between the hypervisor and guest kernels . Distribution support for pv - ops guest kernels appeared starting with Ubuntu 7.04 and RedHat 9 . Xen hypervisors based on any 2.6. 24 or later kernel support pv - ops guests, as does VMware's Workstation product beginning with version 6 . VirtualBox also supports it from version 5.0 . </P>

In para-virtualization vms run on hypervisor that interacts with the hardware
find me the text answering this question