Académique Documents
Professionnel Documents
Culture Documents
KVM only works if your CPU has hardware virtualization support either Intel VT-x or
AMD-V. To determine whether your CPU includes these features, run the following
command:
A 0 indicates that your CPU doesnt support hardware virtualization, while a 1 or more
indicates that it does. You may still have to enable hardware virtualization support in
your computers BIOS, even if this command returns a 1 or more.
Use the following command to install KVM and supporting packages. Virt-Manager is a
graphical application for managing your virtual machines you can use the kvm
command directly, but libvirt and Virt-Manager simplify the process.
Only the root user and users in the libvirtd group have permission to use KVM virtual
machines. Run the following command to add your user account to the libvirtd group:
After running this command, log out and log back in. Run this command after logging
back in and you should see an empty list of virtual machines. This indicates that
everything is working correctly.
Once youve got KVM installed, the easiest way to use it is with the Virtual Machine
Manager application. Youll find it in your Dash.
Click the Create New Virtual Machine button on the toolbar and the Virtual Machine
Manager will walk you through selecting an installation method, configuring your virtual
machines virtual hardware, and installing your guest operating system of choice.
The process will by familiar if youve ever used VirtualBox, VMware, or another virtual
machine application. You can install from a disc, ISO image, or even a network
location.
To assign more than 2GB of memory to a virtual machine, youll need a 64-bit Linux
kernel. Systems running 32-bit kernels can assign a maximum of 2 GB of RAM to a
virtual machine.
By default, KVM gives you NAT-like bridged networking your virtual machine wont
appear on the network as its own device, but it will have network access through the
host operating system. If youre running server software in your virtual machine and
want it accessible from other devices on the network, youll have to tweak the
networking settings.
After selecting your installation method, Virt-Manager will boot the guest operating
system in a window. Install the guest operating system as you would on a physical
machine.
Managing Virtual Machines
The Virtual Machine Manager window displays a list of your installed virtual machines.
Right-click virtual machines in the window to perform actions, including starting,
shutting down, cloning, or migrating them.
You can view information about the virtual machine and configure its virtual hardware
by clicking the i-shaped toolbar icon in the virtual machines window.
Qu es KVM?
KVM (Kernel Virtual Machine) es un mdulo del kernel Linux que permite
que los programas en espacio usuario utilicen las caractersticas de
virtualizacin por hardware ofrecidas por diferentes procesadores. En la
actualidad, soporta procesadores AMD e Intel (x86 y x86_64), PPC 440,
PPC 970, S/390, y ARM (Cortex A15).
Qu es QEMU?
Qu es libvirt?
KVM/QEMU
Xen (en Linux y Solaris)
LXC
OpenVZ
VirtualBox
Microsoft Hyper-V
IBM PowerVM
El hipervisor Parallels
KVM
Para poder utilizar KVM se debe contar con un procesador que soporte
virtualizacin por hardware.
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl
xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor
ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic
popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat
epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid
fsgsbase smep erms
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl
xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor
ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic
popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat
epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid
fsgsbase smep erms
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl
xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor
ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic
popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat
epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid
fsgsbase smep erms
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl
xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor
ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic
popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat
epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid
fsgsbase smep erms
El mdulo del kernel que implementa KVM (kvm) est incluido por
defecto en todos los kernels Linux (mainline Linux) a partir de la versin
2.6.20. Por lo tanto, para utilizar KVM slo hace falta comprobar que el
mdulo est cargado, para ello ejecutar lsmod | grep kvm:
kvm_intel 126236 0
kvm 363491 1 kvm_intel
modprobe kvm_amd
modprobe kvm_intel
Instalar QEMU
device-tree-compile
usbredir
spice
http://wiki.qemu-project.org/download/qemu-1.7.0.tar.bz2
Extraer el tarball:
Configurar qemu:
$ cd qemu-1.7.0/
$ ./configure --help
Por defecto compila con soporte para todas las arquitecturas de CPU
disponibles, por lo tanto (salvo que se desee quitar alguna) no hace falta
especificar la "target list".
--target-list=i386-softmmu,x86_64-softmmu,arm-softmmu
Compilar qemu:
$ make
# make install
Instalar libvirt
http://libvirt.org/sources/libvirt-1.2.1.tar.gz
Extraer el tarball:
Configurar libvirt:
$cd libvirt-1.2.1/
$ ./configure --help
Al igual que QEMU, por defecto instala los binarios en el
directorio /usr/local/bin. Existen muchas caractersticas que se pueden
habilitar, como el soporte para todo tipo de hipervisores, storage, etc. Es
importante habilitar el uso de threads POSIX para mejorar el
rendimiento. Revisar cuidadosamente la ayuda de configure y habilitar
todas las caractersticas necesarias (algunas requieren la instalacin de
paquetes adicionales):
Errores de configuracin:
$ cd ..
$ mv ~/Downloads/lloyd-yajl-2.0.1-0-gf4b2b1a.tar.gz ./
$ cd lloyd-yajl-f4b2b1a/
$ ./configure
$ make
$ make install
$ cd ../libvirt-1.2.1/
$ ./configure
$ make
# make install
Instalar virt-manager
http://virt-manager.org/download/sources/virt-manager/virt-manager-
0.10.0.tar.gz
Extraer el tarball:
Instalar virt-manager:
$ cd virt-manager-0.10.0/
$ export PKG_CONFIG_PATH="/usr/local/lib/pkgconfig"
#!/usr/bin/bash
# http://wiki.libvirt.org/page/Libvirtd_and_dnsmasq
# Note also that the tun, vhost_net and kvm related modules are
# on your setup
MODULES="tun vhost_net"
PIDFILE="/usr/local/var/run/libvirt/libvirtd.pid"
TIMEOUT=${TIMEOUT:-40}
check_running_machines() {
i=0
/usr/local/bin/virsh shutdown $j
done
break
fi
echo -n "."
i=`expr $i + 1`
sleep 1
done
echo ""
/usr/local/bin/virsh destroy $j
done
echo ""
sleep 2
fi
}
check_processor() {
fi
check=$?
fi
fi
start() {
if [ -f $PIDFILE ];then
exit 1
fi
/sbin/modprobe -a $MODULES
export PATH="$PATH:/usr/local/sbin:/usr/local/bin"
/usr/local/sbin/libvirtd -d -l $OPTS
stop() {
if [ ! -f $PIDFILE ];then
exit 2
fi
check_running_machines
check_processor
for i in "$NETNAME"; do
done
sleep 3
case $1 in
start)
start
;;
stop)
stop
;;
restart)
stop
sleep 1
start
;;
*)
;;
esac
# chmod +x /etc/rc.d/rc.libvirt
if [ -x /etc/rc.d/rc.libvirt ]; then
/etc/rc.d/rc.libvirt start
fi
/etc/rc.d/rc.libvirt stop
fi
Starting libvirtd...
Se observa que falla al inicializar sockets, esto se debe a que por defecto
utiliza TLS para aceptar conexiones entrantes. Hay dos soluciones:
instalar un certificado CA; o deshabilitar TLS.
# nano /usr/local/etc/libvirt/libvirtd.conf
listen_tls = 0
Una vez que se corrigen todos los errores, el demonio libvirtd inicia
correctamente:
Starting libvirtd...
'quit' to quit
virsh # nodeinfo
CPU(s): 4
CPU socket(s): 1
virsh # iface-list
---------------------------------------------------
virsh # net-list
----------------------------------------------------------
virsh # pool-list
-------------------------------------------
virsh # version
virsh # exit
<capabilities>
<host>
<uuid>400ad740-9e16-e211-8d57-30f9edc2dbe8</uuid>
<cpu>
<arch>x86_64</arch>
<model>SandyBridge</model>
<vendor>Intel</vendor>
<feature name='erms'/>
<feature name='smep'/>
<feature name='fsgsbase'/>
<feature name='rdrand'/>
<feature name='f16c'/>
<feature name='osxsave'/>
<feature name='pcid'/>
<feature name='pdcm'/>
<feature name='xtpr'/>
<feature name='tm2'/>
<feature name='est'/>
<feature name='vmx'/>
<feature name='ds_cpl'/>
<feature name='monitor'/>
<feature name='dtes64'/>
<feature name='pbe'/>
<feature name='tm'/>
<feature name='ht'/>
<feature name='ss'/>
<feature name='acpi'/>
<feature name='ds'/>
<feature name='vme'/>
</cpu>
<power_management>
<suspend_mem/>
<suspend_disk/>
<suspend_hybrid/>
</power_management>
<migration_features>
<live/>
<uri_transports>
<uri_transport>tcp</uri_transport>
</uri_transports>
</migration_features>
<topology>
<cells num='1'>
<cell id='0'>
<memory unit='KiB'>3987248</memory>
<cpus num='4'>
</cpus>
</cell>
</cells>
</topology>
<secmodel>
<model>none</model>
<doi>0</doi>
</secmodel>
<secmodel>
<model>dac</model>
<doi>0</doi>
<baselabel type='kvm'>+0:+0</baselabel>
<baselabel type='qemu'>+0:+0</baselabel>
</secmodel>
</host>
<guest>
<os_type>hvm</os_type>
<arch name='alpha'>
<wordsize>64</wordsize>
<emulator>/usr/local/bin/qemu-system-alpha</emulator>
<machine maxCpus='4'>clipper</machine>
<domain type='qemu'>
</domain>
</arch>
<features>
<deviceboot/>
</features>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='armv7l'>
<wordsize>32</wordsize>
<emulator>/usr/local/bin/qemu-system-arm</emulator>
<machine maxCpus='1'>integratorcp</machine>
<machine maxCpus='1'>collie</machine>
<machine maxCpus='2'>smdkc210</machine>
<machine maxCpus='2'>nuri</machine>
<machine maxCpus='1'>verdex</machine>
<machine maxCpus='1'>connex</machine>
<machine maxCpus='4'>midway</machine>
<machine maxCpus='4'>highbank</machine>
<machine maxCpus='1'>kzm</machine>
<machine maxCpus='1'>mainstone</machine>
<machine maxCpus='1'>musicpal</machine>
<machine maxCpus='1'>n810</machine>
<machine maxCpus='1'>n800</machine>
<machine maxCpus='1'>sx1-v1</machine>
<machine maxCpus='1'>sx1</machine>
<machine maxCpus='1'>cheetah</machine>
<machine maxCpus='4'>realview-pbx-a9</machine>
<machine maxCpus='1'>realview-pb-a8</machine>
<machine maxCpus='4'>realview-eb-mpcore</machine>
<machine maxCpus='1'>realview-eb</machine>
<machine maxCpus='1'>terrier</machine>
<machine maxCpus='1'>borzoi</machine>
<machine maxCpus='1'>spitz</machine>
<machine maxCpus='1'>akita</machine>
<machine maxCpus='1'>lm3s6965evb</machine>
<machine maxCpus='1'>lm3s811evb</machine>
<machine maxCpus='1'>tosa</machine>
<machine maxCpus='1'>versatileab</machine>
<machine maxCpus='1'>versatilepb</machine>
<machine maxCpus='4'>vexpress-a15</machine>
<machine maxCpus='4'>vexpress-a9</machine>
<machine maxCpus='1'>xilinx-zynq-a9</machine>
<machine maxCpus='1'>z2</machine>
<domain type='qemu'>
</domain>
</arch>
<features>
<cpuselection/>
<deviceboot/>
</features>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='cris'>
<wordsize>32</wordsize>
<emulator>/usr/local/bin/qemu-system-cris</emulator>
<machine maxCpus='1'>axis-dev88</machine>
<domain type='qemu'>
</domain>
</arch>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='i686'>
<wordsize>32</wordsize>
<emulator>/usr/local/bin/qemu-system-i386</emulator>
<machine maxCpus='1'>isapc</machine>
<machine maxCpus='255'>pc-0.10</machine>
<machine maxCpus='255'>pc-0.11</machine>
<machine maxCpus='255'>pc-0.12</machine>
<machine maxCpus='255'>pc-0.13</machine>
<machine maxCpus='255'>pc-0.14</machine>
<machine maxCpus='255'>pc-0.15</machine>
<machine maxCpus='255'>pc-1.0</machine>
<machine maxCpus='255'>pc-1.1</machine>
<machine maxCpus='255'>pc-1.2</machine>
<machine maxCpus='255'>pc-1.3</machine>
<machine maxCpus='255'>pc-i440fx-1.4</machine>
<machine maxCpus='255'>pc-i440fx-1.5</machine>
<machine maxCpus='255'>pc-i440fx-1.6</machine>
<machine maxCpus='255'>pc-q35-1.4</machine>
<machine maxCpus='255'>pc-q35-1.5</machine>
<machine maxCpus='255'>pc-q35-1.6</machine>
<domain type='qemu'>
</domain>
<domain type='kvm'>
<emulator>/usr/local/bin/qemu-system-i386</emulator>
</domain>
</arch>
<features>
<cpuselection/>
<deviceboot/>
<pae/>
<nonpae/>
</features>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='lm32'>
<wordsize>32</wordsize>
<emulator>/usr/local/bin/qemu-system-lm32</emulator>
<machine maxCpus='1'>lm32-evr</machine>
<machine maxCpus='1'>lm32-uclinux</machine>
<machine maxCpus='1'>milkymist</machine>
<domain type='qemu'>
</domain>
</arch>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='m68k'>
<wordsize>32</wordsize>
<emulator>/usr/local/bin/qemu-system-m68k</emulator>
<machine maxCpus='1'>mcf5208evb</machine>
<machine maxCpus='1'>an5206</machine>
<machine maxCpus='1'>dummy</machine>
<domain type='qemu'>
</domain>
</arch>
<features>
<deviceboot/>
</features>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='microblaze'>
<wordsize>32</wordsize>
<emulator>/usr/local/bin/qemu-system-microblaze</emulator>
<machine maxCpus='1'>petalogix-s3adsp1800</machine>
<machine maxCpus='1'>petalogix-ml605</machine>
<domain type='qemu'>
</domain>
</arch>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='microblazeel'>
<wordsize>32</wordsize>
<emulator>/usr/local/bin/qemu-system-microblazeel</emulator>
<machine maxCpus='1'>petalogix-s3adsp1800</machine>
<machine maxCpus='1'>petalogix-ml605</machine>
<domain type='qemu'>
</domain>
</arch>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='mips'>
<wordsize>32</wordsize>
<emulator>/usr/local/bin/qemu-system-mips</emulator>
<machine maxCpus='16'>malta</machine>
<machine maxCpus='1'>pica61</machine>
<machine maxCpus='1'>magnum</machine>
<machine maxCpus='1'>mipssim</machine>
<machine maxCpus='1'>mips</machine>
<domain type='qemu'>
</domain>
</arch>
<features>
<deviceboot/>
</features>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='mipsel'>
<wordsize>32</wordsize>
<emulator>/usr/local/bin/qemu-system-mipsel</emulator>
<machine maxCpus='16'>malta</machine>
<machine maxCpus='1'>pica61</machine>
<machine maxCpus='1'>magnum</machine>
<machine maxCpus='1'>mipssim</machine>
<machine maxCpus='1'>mips</machine>
<domain type='qemu'>
</domain>
</arch>
<features>
<deviceboot/>
</features>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='mips64'>
<wordsize>64</wordsize>
<emulator>/usr/local/bin/qemu-system-mips64</emulator>
<machine maxCpus='16'>malta</machine>
<machine maxCpus='1'>pica61</machine>
<machine maxCpus='1'>magnum</machine>
<machine maxCpus='1'>mipssim</machine>
<machine maxCpus='1'>mips</machine>
<domain type='qemu'>
</domain>
</arch>
<features>
<deviceboot/>
</features>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='mips64el'>
<wordsize>64</wordsize>
<emulator>/usr/local/bin/qemu-system-mips64el</emulator>
<machine maxCpus='16'>malta</machine>
<machine maxCpus='1'>fulong2e</machine>
<machine maxCpus='1'>pica61</machine>
<machine maxCpus='1'>magnum</machine>
<machine maxCpus='1'>mipssim</machine>
<machine maxCpus='1'>mips</machine>
<domain type='qemu'>
</domain>
</arch>
<features>
<deviceboot/>
</features>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='ppc'>
<wordsize>32</wordsize>
<emulator>/usr/local/bin/qemu-system-ppc</emulator>
<machine maxCpus='1'>g3beige</machine>
<machine maxCpus='32'>ppce500</machine>
<machine maxCpus='1'>mac99</machine>
<machine maxCpus='15'>mpc8544ds</machine>
<machine maxCpus='1'>taihu</machine>
<machine maxCpus='1'>ref405ep</machine>
<machine maxCpus='1'>bamboo</machine>
<machine maxCpus='1'>prep</machine>
<machine maxCpus='1'>virtex-ml507</machine>
<domain type='qemu'>
</domain>
</arch>
<features>
<cpuselection/>
<deviceboot/>
</features>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='ppc64'>
<wordsize>64</wordsize>
<emulator>/usr/local/bin/qemu-system-ppc64</emulator>
<machine maxCpus='256'>pseries</machine>
<machine maxCpus='32'>ppce500</machine>
<machine maxCpus='1'>mac99</machine>
<machine maxCpus='1'>g3beige</machine>
<machine maxCpus='15'>mpc8544ds</machine>
<machine maxCpus='1'>taihu</machine>
<machine maxCpus='1'>ref405ep</machine>
<machine maxCpus='1'>bamboo</machine>
<machine maxCpus='1'>prep</machine>
<machine maxCpus='1'>virtex-ml507</machine>
<domain type='qemu'>
</domain>
</arch>
<features>
<cpuselection/>
<deviceboot/>
</features>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='ppcemb'>
<wordsize>32</wordsize>
<emulator>/usr/local/bin/qemu-system-ppcemb</emulator>
<machine maxCpus='1'>g3beige</machine>
<machine maxCpus='32'>ppce500</machine>
<machine maxCpus='1'>mac99</machine>
<machine maxCpus='15'>mpc8544ds</machine>
<machine maxCpus='1'>taihu</machine>
<machine maxCpus='1'>ref405ep</machine>
<machine maxCpus='1'>bamboo</machine>
<machine maxCpus='1'>prep</machine>
<machine maxCpus='1'>virtex-ml507</machine>
<domain type='qemu'>
</domain>
</arch>
<features>
<cpuselection/>
<deviceboot/>
</features>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='s390x'>
<wordsize>64</wordsize>
<emulator>/usr/local/bin/qemu-system-s390x</emulator>
<domain type='qemu'>
</domain>
</arch>
<features>
<cpuselection/>
<deviceboot/>
</features>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='sh4'>
<wordsize>32</wordsize>
<emulator>/usr/local/bin/qemu-system-sh4</emulator>
<machine maxCpus='1'>shix</machine>
<machine maxCpus='1'>r2d</machine>
<domain type='qemu'>
</domain>
</arch>
<features>
<deviceboot/>
</features>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='sh4eb'>
<wordsize>64</wordsize>
<emulator>/usr/local/bin/qemu-system-sh4eb</emulator>
<machine maxCpus='1'>shix</machine>
<machine maxCpus='1'>r2d</machine>
<domain type='qemu'>
</domain>
</arch>
<features>
<deviceboot/>
</features>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='sparc'>
<wordsize>32</wordsize>
<emulator>/usr/local/bin/qemu-system-sparc</emulator>
<machine maxCpus='1'>SS-5</machine>
<machine maxCpus='1'>leon3_generic</machine>
<machine maxCpus='1'>SPARCbook</machine>
<machine maxCpus='1'>SPARCClassic</machine>
<machine maxCpus='1'>SS-4</machine>
<machine maxCpus='1'>LX</machine>
<machine maxCpus='1'>Voyager</machine>
<machine maxCpus='4'>SS-20</machine>
<machine maxCpus='4'>SS-600MP</machine>
<machine maxCpus='4'>SS-10</machine>
<domain type='qemu'>
</domain>
</arch>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='sparc64'>
<wordsize>64</wordsize>
<emulator>/usr/local/bin/qemu-system-sparc64</emulator>
<machine maxCpus='1'>sun4u</machine>
<machine maxCpus='1'>Niagara</machine>
<machine maxCpus='1'>sun4v</machine>
<domain type='qemu'>
</domain>
</arch>
<features>
<deviceboot/>
</features>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='unicore32'>
<wordsize>32</wordsize>
<emulator>/usr/local/bin/qemu-system-unicore32</emulator>
<machine maxCpus='1'>puv3</machine>
<domain type='qemu'>
</domain>
</arch>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='x86_64'>
<wordsize>64</wordsize>
<emulator>/usr/local/bin/qemu-system-x86_64</emulator>
<machine maxCpus='255'>pc-0.10</machine>
<machine maxCpus='255'>pc-0.11</machine>
<machine maxCpus='255'>pc-0.12</machine>
<machine maxCpus='255'>pc-0.13</machine>
<machine maxCpus='255'>pc-0.14</machine>
<machine maxCpus='255'>pc-0.15</machine>
<machine maxCpus='255'>pc-1.0</machine>
<machine maxCpus='255'>pc-1.1</machine>
<machine maxCpus='255'>pc-1.2</machine>
<machine maxCpus='255'>pc-1.3</machine>
<machine maxCpus='255'>pc-i440fx-1.4</machine>
<machine maxCpus='255'>pc-i440fx-1.5</machine>
<machine maxCpus='255'>pc-i440fx-1.6</machine>
<machine maxCpus='255'>pc-q35-1.4</machine>
<machine maxCpus='255'>pc-q35-1.5</machine>
<machine maxCpus='255'>pc-q35-1.6</machine>
<domain type='qemu'>
</domain>
<domain type='kvm'>
<emulator>/usr/local/bin/qemu-system-x86_64</emulator>
</domain>
</arch>
<features>
<cpuselection/>
<deviceboot/>
</features>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='xtensa'>
<wordsize>32</wordsize>
<emulator>/usr/local/bin/qemu-system-xtensa</emulator>
<machine maxCpus='4'>sim</machine>
<machine maxCpus='4'>lx200</machine>
<machine maxCpus='4'>lx60</machine>
<domain type='qemu'>
</domain>
</arch>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='xtensaeb'>
<wordsize>32</wordsize>
<emulator>/usr/local/bin/qemu-system-xtensaeb</emulator>
<machine maxCpus='4'>sim</machine>
<machine maxCpus='4'>lx200</machine>
<machine maxCpus='4'>lx60</machine>
<domain type='qemu'>
</domain>
</arch>
</guest>
</capabilities>
# ln -s /usr/local/lib/libvirt.so.0 /lib64/libvirt.so.0
# ln -s /usr/local/lib/libyajl.so.2 /lib64/libyajl.so.2
# nano /usr/share/polkit-1/actions/org.libvirt.unix.policy
"http://www.freedesktop.org/standards/PolicyKit/1.0/policyconfig.dtd">
<policyconfig>
<action id="org.libvirt.unix.monitor">
<defaults>
<allow_any>yes</allow_any>
<allow_inactive>yes</allow_inactive>
<allow_active>yes</allow_active>
</defaults>
</action>
<action id="org.libvirt.unix.manage">
<defaults>
<!-- Only a program in the active host session can use libvirt
in
<allow_any>auth_admin</allow_any>
<allow_inactive>auth_admin</allow_inactive>
<allow_active>auth_admin_keep</allow_active>
</defaults>
</action>
</policyconfig>
$ virt-manager
# nano /var/lib/polkit-1/localauthority/50-local.d/50-vaio.libvirt-
access.pkla
Identity=unix-group:wheel
Action=org.libvirt.unix.manage
ResultAny=yes
ResultInactive=yes
ResultActive=yes
Identity=unix-user:emi
Action=org.libvirt.unix.manage
ResultAny=yes
ResultInactive=yes
ResultActive=yes
NAME
SYNOPSIS
DESCRIPTION
Create a pool.
OPTIONS
[--name] name of the pool
Finalizar:
Crear una mquina virtual