KubeVirt is a virtualization add-on to Kubernetes and this guide assumes that a Kubernetes cluster is already installed.
A few requirements need to be met before you can begin:
Kubernetes cluster (OpenShift, Tectonic)
kubectl client utility
git
Kubernetes 1.10 or later is required to run KubeVirt.
In addition it can be that feature gates need to be opened.
There are several distributions of Kubernetes, you need to decide on one and deploy it.
Hardware with virtualization support is recommended. You can use virt-host-validate to ensure that your hosts are capable of running virtualization workloads:
$ virt-host-validate qemu
QEMU: Checking for hardware virtualization : PASS
QEMU: Checking if device /dev/kvm exists : PASS
QEMU: Checking if device /dev/kvm is accessible : PASS
QEMU: Checking if device /dev/vhost-net exists : PASS
QEMU: Checking if device /dev/net/tun exists : PASS
...If hardware virtualization is not available, then a software emulation fallback can be enabled using:
$ kubectl create configmap -n kubevirt kubevirt-config \
--from-literal debug.useEmulation=true
This ConfigMap needs to be created before deployment or the virt-controller deployment has to be restarted.
For hugepages support you need at least Kubernetes version 1.9.
To enable hugepages on Kubernetes, check the official documentation.
To enable hugepages on OpenShift, check the official documentation.
To pre-allocate hugepages on boot time, you will need to specify
hugepages under kernel boot parameters hugepagesz=2M hugepages=64 and
restart your machine.
You can find more about hugepages under official documentation.
Once Kubernetes is deployed, you will need to deploy the KubeVirt
add-on. The add-on is deployed to a cluster using the kubectl tool and
manifest file:
$ RELEASE=v0.10.0
$ kubectl apply -f https://github.com/kubevirt/kubevirt/releases/download/${RELEASE}/kubevirt.yamlThis command will deploy the most recent stable version of KubeVirt to
your cluster. The new components will be deployed in the kubevirt
namespace:
kubectl get pods -n kubevirt
NAME READY STATUS RESTARTS AGE
libvirt-9zmtl 2/2 Running 0 28m
virt-controller-5d9fc8cf8b-n5trt 0/1 Running 0 27m
virt-handler-vwdjx 1/1 Running 0 28mvirtctl deploymentBasic VirtualMachineInstance operations can be performed with the stock
kubectl utility. However, the virtctl binary utility is required to
use advanced features such as:
Serial and graphical console access
It also provides convenience commands for:
Starting and stopping VirtualMachineInstances
Live migrating VirtualMachineInstances
The most recent version of the tool can be retrieved from the official release page.
There are three ways to deploy KubeVirt on OpenShift.
The following
SCCs
need to be added prior kubevirt.yaml deployment:
$ oc adm policy add-scc-to-user privileged -n kubevirt -z kubevirt-privileged
$ oc adm policy add-scc-to-user privileged -n kubevirt -z kubevirt-controller
$ oc adm policy add-scc-to-user privileged -n kubevirt -z kubevirt-apiserverOnce privileges are granted, the kubevirt.yaml can be deployed:
$ RELEASE=v0.10.0
$ kubectl apply -f https://github.com/kubevirt/kubevirt/releases/download/${RELEASE}/kubevirt.yamlYou can find KubeVirt in the OpenShift Service Catalog and install it from there. In order to do that please follow the documentation in the KubeVirt APB repository.
The kubevirt-ansible project provides a collection of playbooks that installs KubeVirt and it’s related components on top of OpenShift or Kubernetes clusters.
See the Developer Getting Started Guide to understand how to build and deploy KubeVirt from source.
KubeVirt alone does not bring any additional network plugins, it just allows user to utilize them. If you want to attach your VMs to multiple networks (Multus CNI) or have full control over L2 (OVS CNI), you need to deploy respective network plugins. For more information, refer to OVS CNI installation guide.
Note: KubeVirt Ansible network playbook installs these plugins by default.