Installation guide

# virsh list --all
Id Name State
----------------------------------------------------
#
In vest ig at io n
There are various possible causes of this problem. Performing these tests will help to
determine the cause of this situation:
Verif y KVM kern el mo d u les
Verify that KVM kernel modules are inserted in the kernel:
# lsmod | grep kvm
kvm_intel 121346 0
kvm 328927 1 kvm_intel
If you are using an AMD machine, verify the kvm_amd kernel modules are inserted
in the kernel instead, using the similar command l smo d | g rep kvm_amd in
the root shell.
If the modules are not present, insert them using the mo d pro be <modulename>
command.
Note
Although it is uncommon, KVM virtualization support may be compiled into
the kernel. In this case, modules are not needed.
Verif y virt u aliz at io n ext en sio n s
Verify that virtualization extensions are supported and enabled on the host:
# egrep "(vmx|svm)" /proc/cpuinfo
flags : fpu vme de pse tsc ... svm ... skinit wdt npt lbrv
svm_lock nrip_save
flags : fpu vme de pse tsc ... svm ... skinit wdt npt lbrv
svm_lock nrip_save
Enable virtualization extensions in your hardware's firmware configuration within
the BIOS setup. Refer to your hardware documentation for further details on this.
Verif y clien t URI co n f ig urat io n
Verify that the URI of the client is configured as desired:
# virsh uri
vbox:///system
For example, this message shows the URI is connected to the Virt u alBo x
hypervisor, not Q EMU , and reveals a configuration error for a URI that is
otherwise set to connect to a Q EMU hypervisor. If the URI was correctly
connecting to Q EMU , the same message would appear instead as:
Red Hat Ent erp rise Linux 6 Virt ualiz at ion Host Configurat ion and G uest Inst allat ion G uide
14 8