libvirt
None of the virtualization tools is installed by default.
To install KVM and KVM tools, proceed as follows:
Start YaST and choose
› .
Select libvirt
-based management stack is also desired. Confirm with
.
To enable normal networking for the VM Guest, using a network bridge is recommended. YaST offers to automatically configure a bridge on the VM Host Server. Agree to do so by choosing
, otherwise choose .After the setup has been finished, you can start setting up VM Guests. Rebooting the VM Host Server is not required.
To install Xen and Xen tools, proceed as follows:
Start YaST and choose
› .
Select libvirt
-based management stack is also desired. Confirm with
.
To enable normal networking for the VM Guest, using a network bridge is recommended. YaST offers to automatically configure a bridge on the VM Host Server. Agree to do so by choosing
, otherwise choose .After the setup has been finished, you need to reboot the machine with the Xen kernel.
If everything works as expected, change the default boot kernel with YaST and make the Xen-enabled kernel the default. For more information about changing the default kernel, see Book “Reference”, Chapter 12 “The Boot Loader GRUB 2”, Section 12.3 “Configuring the Boot Loader with YaST”.
To install containers, proceed as follows:
Start YaST and choose
› .Select
and confirm with .
It is possible using Zypper and patterns to install virtualization
packages. Run the command zypper in -t pattern
PATTERN. Available patterns are:
kvm_server
: sets up the
KVM VM Host Server with QEMU tools for management
kvm_tools
: installs the
libvirt
tools for managing and monitoring VM Guests
xen_server
: sets up the
Xen VM Host Server with Xen tools for management
xen_tools
: installs the
libvirt
tools for managing and monitoring VM Guests
There is no pattern for containers; install the libvirt-daemon-lxc package.
UEFI support is provided by OVMF (Open Virtual Machine Firmware). To enable UEFI boot, first install the qemu-ovmf-x86_64 or qemu-uefi-aarch64 package.
libvirt
is configured using
/usr/share/qemu/ovmf-x86_64-ms-4m-code.bin
and
/usr/share/qemu/ovmf-x86_64-ms-4m-vars.bin
as
default UEFI firmware and VARS images. For ARM the defaults are
/usr/share/qemu/aavmf-aarch64-code.bin
and
/usr/share/qemu/aavmf-aarch64-vars.bin
.
The packages contain the following files:
root #
rpm -ql qemu-ovmf-x86_64
/usr/share/qemu/ovmf-x86_64-ms-code.bin /usr/share/qemu/ovmf-x86_64-ms-vars.bin /usr/share/qemu/ovmf-x86_64-ms.bin /usr/share/qemu/ovmf-x86_64-opensuse-code.bin /usr/share/qemu/ovmf-x86_64-opensuse-vars.bin /usr/share/qemu/ovmf-x86_64-opensuse.bin /usr/share/qemu/ovmf-x86_64-suse-code.bin /usr/share/qemu/ovmf-x86_64-suse-vars.bin /usr/share/qemu/ovmf-x86_64-suse.bin /usr/share/qemu/ovmf-x86_64-code.bin /usr/share/qemu/ovmf-x86_64-vars.bin /usr/share/qemu/ovmf-x86_64.bin
The *-code.bin
files are the UEFI firmwares.
The *-vars.bin
files are corresponding variable
store images that can be used as a template for per-VM non-volatile
store. libvirt
copies the specified vars
template to a per-VM path under
/var/lib/libvirt/qemu/nvram/
when first
creating the VM. Files without code
or
vars
in the name can be used as a single UEFI
image. They are not as useful since no UEFI variables persist
across power cycles of the VM.
The *-ms*.bin
files contain Microsoft keys as
found on real hardware. Therefore, they are configured as default in
libvirt
. Likewise, the *-suse*.bin
files
contain preinstalled SUSE and openSUSE keys. There is also a set
of files with no preinstalled keys.
For details, see Using UEFI and Secure Boot and http://www.linux-kvm.org/downloads/lersek/ovmf-whitepaper-c770f8c.txt.