Difference between revisions of "KVM"

From Alpine Linux
Jump to: navigation, search
(Installing KVM)
Line 3: Line 3:
  
 
= Installing KVM =
 
= Installing KVM =
It is possible to install just qemu and libvirt for local management, but most users will probably want libvirt-deamon and/or virt-manager for a GUI.  
+
It is possible to install just qemu and libvirt for local management  
{{Cmd|sudo apk add qemu-system-x86_64 libvirt
+
{{Cmd|sudo apk add qemu-system-x86_64 libvirt}}
 
+
but most users will probably want libvirt-deamon and/or virt-manager for a GUI.
sudo apk add libvirt-daemon dbus polkit}}
+
{{Cmd|sudo apk add libvirt-daemon dbus polkit}}
 +
If you want to use other disk image formats than raw, you need qemu-img
 +
{{Cmd|sudo apk add qemu-img}}
  
 
Enable the KVM kernel module
 
Enable the KVM kernel module
Line 12: Line 14:
 
or
 
or
 
{{Cmd|sudo modprobe kvm-amd}}
 
{{Cmd|sudo modprobe kvm-amd}}
 
+
by defaults kvm use bridge to nat vm, if you want network with the default configuration, you need to load the tun module
 +
{{Cmd|sudo modprobe tun}}
  
 
Add your user to the follwing groups so you can mange the vms
 
Add your user to the follwing groups so you can mange the vms

Revision as of 19:48, 30 October 2017

KVM is an open source virtualization solution in a kernel module. KVM can virtualize x86, PowerPC, and S390 guests.


Installing KVM

It is possible to install just qemu and libvirt for local management

sudo apk add qemu-system-x86_64 libvirt

but most users will probably want libvirt-deamon and/or virt-manager for a GUI.

sudo apk add libvirt-daemon dbus polkit

If you want to use other disk image formats than raw, you need qemu-img

sudo apk add qemu-img

Enable the KVM kernel module

sudo modprobe kvm-intel

or

sudo modprobe kvm-amd

by defaults kvm use bridge to nat vm, if you want network with the default configuration, you need to load the tun module

sudo modprobe tun

Add your user to the follwing groups so you can mange the vms

sudo addgroup user kvm sudo addgroup user qemu sudo addgroup user libvirt

Set libvirtd and dbus to start on startup

sudo rc-update add libvirtd sudo rc-update add dbus

Configure PolicyKit

In order to use libvirtd to remotely control KVM over ssh PolicyKit needs a .pkla informing it that this is allowed. Write the following file to /etc/polkit-1/localauthority/50-local.d/50-libvirt-ssh-remote-access-policy.pkla

[Remote libvirt SSH access] Identity=unix-group:libvirt Action=org.libvirt.unix.manage ResultAny=yes ResultInactive=yes ResultActive=yes