Академический Документы
Профессиональный Документы
Культура Документы
Pre-installation checklist
Check that your CPU supports hardware virtualization
To run KVM, you need a processor that supports hardware virtualization. Intel and AMD both
have developed extensions for their processors, deemed respectively Intel VT-x (code name
Vanderpool) and AMD-V (code name Pacifica). To see if your processor supports one of these,
you can review the output from this command:
egrep -c '(vmx|svm)' /proc/cpuinfo
If you see :
INFO: Your CPU does not support KVM extensions
KVM acceleration can NOT be used
You can still run virtual machines, but it'll be much slower without the KVM extensions.
NOTE: You may see a message like "KVM acceleration can/can NOT be used". This is
misleading and only means if KVM is *currently* available (i.e. "turned on"), *not* if it is
supported.
Running a 64 bit kernel on the host operating system is recommended but not required.
1. To serve more than 2GB of RAM for your VMs, you must use a 64-bit kernel (see
32bit_and_64bit). On a 32-bit kernel install, you'll be limited to 2GB RAM at maximum
for a given VM.
2. Also, a 64-bit system can host both 32-bit and 64-bit guests. A 32-bit system can only
host 32-bit guests.
To see if your processor is 64-bit, you can run this command:
egrep -c ' lm ' /proc/cpuinfo
x86_64 indicates a running 64-bit kernel. If you use see i386, i486, i586 or i686, you're running a
32-bit kernel.
Note: x86_64 is synonymous with amd64.
Installation of KVM
Install Necessary Packages
For the following setup, we will assume that you are deploying KVM on a server, and therefore
do not have any X server on the machine.
You need to install a few packages first:
Lucid (10.04) or later
$ sudo apt-get install qemu-kvm libvirt-bin ubuntu-vm-builder bridge-utils
libvirt
qemu-kvm (kvm in Karmic and earlier) is the backend
using
After this, you need to relogin so that your user becomes an effective member of the libvirtd
group. The members of this group can run virtual machines. (You can also 'newgrp kvm' in a
terminal, but this will affect only that terminal.)
Releases prior to Karmic (9.10)
You need to ensure that your username is added to the groups: kvm and libvirtd.
To check:
$ groups
adm dialout cdrom floppy audio dip video plugdev fuse lpadmin admin sambashare
kvm libvirtd
After the installation, you need to relogin so that your user becomes an effective member of
kvm and libvirtd user groups. The members of this group can run virtual machines.
Verify Installation
You can test if your install has been successful with the following command:
$ virsh -c qemu:///system list
Id Name
State
---------------------------------$
Something is wrong (e.g. you did not relogin) and you probably want to fix this before you move
on. The critical point here is whether or not you have write access to /var/run/libvirt/libvirt-sock.
The sock file should have permissions similar to:
$ sudo ls -la /var/run/libvirt/libvirt-sock
srwxrwx--- 1 root libvirtd 0 2010-08-24 14:54 /var/run/libvirt/libvirt-sock
8 22:04 /dev/kvm
You might experience problems when creating a virtual machine. Change the device's group to
kvm/libvirtd instead:
sudo chown root:libvirtd /dev/kvm
Virtual Machine Manager will appear in Applications -> System Tools menu. First create a new
connection to local QEMU instance from File -> Add Connection menu. Localhost (QEMU) or
QEMU/KVM should appear in the virtual machine list. Note: there already exist Localhost
(QEMU Usermode) connection but this does not work at least on Ubuntu 10.04.
Create a new virtual machine by pressing the top left Create a new virtual machine toolbar
button.