Hypervisor: Difference between revisions

From Omnia
Jump to navigation Jump to search
(Created page with "= Type 1 Hypervisor = Type 1 is Bare Metal == Type 1 Linux Hypervisor == === oVirt === POWERFUL OPEN SOURCE VIRTUALIZATION oVirt is a free open-source virtualization solution for your entire enterprise https://www.ovirt.org/ -- <blockquote> oVirt – virtualization solution for your entire enterprise by September 9, 2023 Steve Emms Documents oVirt is a virtualization platform with an easy-to-use web interface. oVirt is built on libvirt which could allow it to...")
 
No edit summary
Line 4: Line 4:


== Type 1 Linux Hypervisor ==
== Type 1 Linux Hypervisor ==
=== KVM ===


=== oVirt ===
=== oVirt ===
Line 56: Line 58:
  oVirt is written in Java.
  oVirt is written in Java.


<ref>https://www.linuxlinks.com/ovirt/</ref>
ref: https://www.linuxlinks.com/ovirt/ <ref>https://www.linuxlinks.com/ovirt/</ref>
 
=== Proxmox ===
 
=== Xen ===
 
---
 
<blockquote>
Xen – open industry standard for virtualization
 
by October 15, 2023 Steve Emms Internet
 
Xen is an open source Virtual Machine Monitor (VMM) originally developed by the Systems Research Group of the University of Cambridge Computer Laboratory, as part of the UK-EPSRC funded XenoServers project.
 
Xen can securely execute multiple virtual machines, each running its own operating system, on a single physical system with close-to-native performance.
 
The Xen Cloud Platform addresses the needs of cloud providers, hosting services and data centers by combining the isolation and multitenancy capabilities of the Xen hypervisor with enhanced security, storage, and network virtualization technologies.
 
Features include:
 
* Small footprint and interface. Xen uses a microkernel design, with a small memory footprint and limited interface to the guest.
* Operating system agnostic.
* Driver Isolation: Xen has the capability to allow the main device driver for a system to run inside of a virtual machine. If the driver crashes, or is compromised, the VM containing the driver can be rebooted and the driver restarted without affecting the rest of the system.
* Paravirtualization: Fully paravirtualized guests have been optimized to run as a virtual machine. This allows the guests to run much faster than with hardware extensions (HVM). Additionally, Xen can run on hardware that does not support virtualization extensions.
* Advanced Memory Management:
** Memory Ballooning.
** Memory Sharing.
** Memory Paging.
** TMEM.
* Resource Management:
** Cpupool.
** Credit 2 Scheduler (experimental).
** NUMA scheduler affinity.
* Scalability:
** 1GB/2MB super page support.
** Deliver events to PVHVM guests using Xen event channels.
* Interoperability / Hardware support:
** Nested Virtualisation (experimental).
** HVM PXE Stack.
** Physical CPU Hotplug.
** Physical Memory Hotplug.
** Support for PV kernels in bzImage format.
** PCI Passthrough.
** X86 Advanced Vector eXtension (AVX).
* High Availability and Fault Tolerance:
** Live Migration, Save & Restore.
** Remus Fault Tolerance.
** vMCE.
* Network and Storage:
** Blktap2.
** Online resize of virtual disks.
* Security:
** Driver Domains.
** Device Model Stub Domains.
** Memaccess API.
** XSM & FLASK.
** XSM & FLASK support for IS_PRIV.
** vTPM Support.
* Tooling
** gdbsx.
** vPMU.
** Serial console.
** xentrace.
* Device Models and Virtual Firmware for HVM guests:
** Traditional Device Model.
** Qemu Upstream Device Model.
** ROMBIOS.
** SeaBIOS.
** OVMF/Tianocore (experimental).
* PV Bootloader support:
** PyGrub support for GRUB 2.
** PyGrub support for /boot on ext4.
** pvnetboot support.
* NUMA scheduling affinity.
* Openvswitch integration.
</blockquote>
 
Website: www.xenproject.org
Support: https://wiki.xenproject.org/wiki/Category:FAQ
Developer: Linux Foundation Collaborative Project
License: GNU GPL v2
 
Xen is written in C.
 
ref: https://www.linuxlinks.com/Xen/ <ref>https://www.linuxlinks.com/Xen/</ref>


= keywords =
= keywords =

Revision as of 10:41, 6 January 2024

Type 1 Hypervisor

Type 1 is Bare Metal

Type 1 Linux Hypervisor

KVM

oVirt

POWERFUL OPEN SOURCE VIRTUALIZATION
oVirt is a free open-source virtualization solution for your entire enterprise
https://www.ovirt.org/

--

oVirt – virtualization solution for your entire enterprise

by September 9, 2023 Steve Emms Documents

oVirt is a virtualization platform with an easy-to-use web interface. oVirt is built on libvirt which could allow it to manage virtual machines hosted on any supported backend, including KVM, Xen and VirtualBox. oVirt manages virtual machines, storage and virtualized networks.

oVirt Engine is the control center of the oVirt environment. It allows you to define hosts, configure data centers, add storage, define networks, create virtual machines, manage user permissions and use templates from one central location.

The project consists of the engine core (backend server), VDSM agents and a client side user interface (GWT based) and/or RESTful API to control the engine core.

oVirt has three web-based front-ends – for administrators, users and power users (for self provisioning). It also has a REST based API, a Python SDK and a CLI interface, which allows automation of most of its features.

oVirt is an open source software with backing from Red Hat and it is the base for Red Hat Enterprise Virtualization. oVirt is written in Java, over JBoss application server and GWT web framework for its user interface. VDSMd is written in Python.

Features include:

  • High availability.
  • Manage multiple virtual machines.
  • Sophisticated web-based management interface for all aspects of your datacenter.
  • Choice of means of allocation of VMs to hosts: manual, “optimised”, pinned.
  • Live migration of VMs from one hypervisor to another.
  • Add new hypervisor nodes easily and centrally.
  • Monitor resource usage on VMs.
  • Load balancing.
  • Manage quotas for use of resources (storage, compute, network).
  • Self-service console for simple and advanced use cases.
  • Built on KVM hypervisor.
  • Enhanced security: SELinux and Mandatory Access Control for VMs and hypervisor.
  • Scalability: up to 64 vCPU and 2TB vRAM per guest.
  • iSCSI, FC, NFS, and local storage.
  • Memory overcommit support (Kernel Samepage Merging).
  • Developer SDK for ovirt-engine, written in Python.
Website: www.ovirt.org
Support: https://www.ovirt.org/documentation/
Developer: Red Hat
License: Apache License 2.0
oVirt is written in Java.

ref: https://www.linuxlinks.com/ovirt/ [1]

Proxmox

Xen

---

Xen – open industry standard for virtualization

by October 15, 2023 Steve Emms Internet

Xen is an open source Virtual Machine Monitor (VMM) originally developed by the Systems Research Group of the University of Cambridge Computer Laboratory, as part of the UK-EPSRC funded XenoServers project.

Xen can securely execute multiple virtual machines, each running its own operating system, on a single physical system with close-to-native performance.

The Xen Cloud Platform addresses the needs of cloud providers, hosting services and data centers by combining the isolation and multitenancy capabilities of the Xen hypervisor with enhanced security, storage, and network virtualization technologies.

Features include:

  • Small footprint and interface. Xen uses a microkernel design, with a small memory footprint and limited interface to the guest.
  • Operating system agnostic.
  • Driver Isolation: Xen has the capability to allow the main device driver for a system to run inside of a virtual machine. If the driver crashes, or is compromised, the VM containing the driver can be rebooted and the driver restarted without affecting the rest of the system.
  • Paravirtualization: Fully paravirtualized guests have been optimized to run as a virtual machine. This allows the guests to run much faster than with hardware extensions (HVM). Additionally, Xen can run on hardware that does not support virtualization extensions.
  • Advanced Memory Management:
    • Memory Ballooning.
    • Memory Sharing.
    • Memory Paging.
    • TMEM.
  • Resource Management:
    • Cpupool.
    • Credit 2 Scheduler (experimental).
    • NUMA scheduler affinity.
  • Scalability:
    • 1GB/2MB super page support.
    • Deliver events to PVHVM guests using Xen event channels.
  • Interoperability / Hardware support:
    • Nested Virtualisation (experimental).
    • HVM PXE Stack.
    • Physical CPU Hotplug.
    • Physical Memory Hotplug.
    • Support for PV kernels in bzImage format.
    • PCI Passthrough.
    • X86 Advanced Vector eXtension (AVX).
  • High Availability and Fault Tolerance:
    • Live Migration, Save & Restore.
    • Remus Fault Tolerance.
    • vMCE.
  • Network and Storage:
    • Blktap2.
    • Online resize of virtual disks.
  • Security:
    • Driver Domains.
    • Device Model Stub Domains.
    • Memaccess API.
    • XSM & FLASK.
    • XSM & FLASK support for IS_PRIV.
    • vTPM Support.
  • Tooling
    • gdbsx.
    • vPMU.
    • Serial console.
    • xentrace.
  • Device Models and Virtual Firmware for HVM guests:
    • Traditional Device Model.
    • Qemu Upstream Device Model.
    • ROMBIOS.
    • SeaBIOS.
    • OVMF/Tianocore (experimental).
  • PV Bootloader support:
    • PyGrub support for GRUB 2.
    • PyGrub support for /boot on ext4.
    • pvnetboot support.
  • NUMA scheduling affinity.
  • Openvswitch integration.
Website: www.xenproject.org
Support: https://wiki.xenproject.org/wiki/Category:FAQ
Developer: Linux Foundation Collaborative Project
License: GNU GPL v2
Xen is written in C.

ref: https://www.linuxlinks.com/Xen/ [2]

keywords