Note
This line is commented out by default to prevent libvirt from producing excessive
log messages. After diagnosing the problem, it is recommended to comment this line
again in the /etc/l i bvi rt/l i bvi rtd . co nf file.
Restart lib virt to determine if this has solved the problem.
If l i bvi rtd still does not start successfully, an error similar to the following will be shown
in the /var/l o g /messag es file:
Feb 6 17:22:09 bart libvirtd: 17576: info : libvirt version:
0.9.9
Feb 6 17:22:09 bart libvirtd: 17576: error :
virNetTLSContextCheckCertFile:92: Cannot read CA certificate
'/etc/pki/CA/cacert.pem': No such file or directory
Feb 6 17:22:09 bart /etc/init.d/libvirtd[17573]: start-stop-
daemon: failed to start `/usr/sbin/libvirtd'
Feb 6 17:22:09 bart /etc/init.d/libvirtd[17565]: ERROR: libvirtd
failed to start
The lib virt d man page shows that the missing cacert. pem file is used as TLS authority
when libvirt is run in Li sten fo r T C P /IP co nnecti ons mode. This means the --
listen parameter is being passed.
So lu t io n
Configure the libvirt daemon's settings with one of the following methods:
Install a CA certificate.
Note
For more information on CA certificates and configuring system authentication,
refer to the Configuring Authentication chapter in the Red Hat Enterprise Linux 6
Deployment Guide.
Do not use TLS; use bare TCP instead. In /etc/l i bvi rt/l i bvi rtd . co nf set
l i sten_tl s = 0 and l i sten_tcp = 1. The default values are l i sten_tl s = 1
and l i sten_tcp = 0 .
Do not pass the --listen parameter. In /etc/sysco nfi g /l i bvi rtd . co nf change
the LIBVIRTD_ARGS variable.
B.2. T he URI failed t o connect t o t he hypervisor
Several different errors can occur when connecting to the server (for example, when running vi rsh).
B.2.1. Cannot read CA cert ificat e
Symp t o m
Comentários a estes Manuais