On 11/11/2015 06:06 AM, Peter Krempa wrote: > On Tue, Nov 10, 2015 at 13:17:41 +0100, Christian Loehle wrote: >> >From README: >> The jailhouse hypervisor driver for the libvirt project aims to provide >> rudimentary support for managing jailhouse with the libvirt library. The >> main advantage of this is the possibility to use virt-manager as a GUI >> to manage Jailhouse cells. Thus the driver is mainly built around the >> API calls that virt-manager uses and needs. > > Would you mind posting a link to 'Jailhouse' for the lazy ones?
There you go: https://github.com/siemens/jailhouse README: Jailhouse is a partitioning Hypervisor based on Linux. It is able to run bare-metal applications or (adapted) operating systems besides Linux. For this purpose it configures CPU and device virtualization features of the hardware platform in a way that none of these domains, called "cells" here, can interfere with each other in an unacceptable way. Jailhouse is optimized for simplicity rather than feature richness. Unlike full-featured Linux-based hypervisors like KVM or Xen, Jailhouse does not support overcommitment of resources like CPUs, RAM or devices. It performs no scheduling and only virtualizes those resources in software, that are essential for a platform and cannot be partitioned in hardware. Once Jailhouse is activated, it runs bare-metal, i.e. it takes full control over the hardware and needs no external support. However, in contrast to other bare-metal hypervisors, it is loaded and configured by a normal Linux system. Its management interface is based on Linux infrastructure. So you boot Linux first, then you enable Jailhouse and finally you split off parts of the system's resources and assign them to additional cells. -- Christian Loehle -- libvir-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/libvir-list
