This document explains how to instantiate a KVM (for Kernel-based Virtual Machine). It is a full virtualization solution for Linux on x86 hardware containing virtualization extensions (Intel VT or AMD-V). It consists of a loadable kernel module, kvm.ko, that provides the core virtualization infrastructure and a processor specific module, kvm-intel.ko or kvm-amd.ko. KVM also requires a modified QEMU although work is underway to get the required changes upstream.
The process of installing (supplying) a software and providing it as a service (instantiation) are the same for all software. However during instantiation each instance can be configured differently.
This section will cover the specific configuration parameters used for a KVM.
After selecting Services, Adding a new service, selecting KVM and the latest release, you should reach the KVM configuration menu.
There are three software types available (see also the software.cfg).
Default will install a single KVM on an available node partition,
Resilient will instantiate the single KVM in at least
three different physical locations and backup/restore the KVM in regular daily intervals.
Cluster KVM behaves similar to an ERP5 cluster. It does not
offer resilience, but to deploy many VMs within the same service to create a
network to link them together. Proceed to continue and request instantiation.
You will be forwarded back to the list of deployed services. Note that you might have to refresh the page for your new instance to appear. Once you can see it, click on entry to open the connection parameters.
You can follow the compilation by looking at the
# tail opt/slapos/log/slapos-node-software.log -f
Note, it might take a few minutes for the instance to become available. Refresh the page from time to time until the connection parameter table displays parameteres. Once the URL entry shows a URL, the Webrunner is up and working. Note down url and access the KVM.
If you go to the URL which includes the username and password, you should be able to access the KVM.