Installation guide

Common libvirt errors and troubleshooting
This appendix documents common lib virt -related problems and errors along with instructions for
dealing with them.
Locate the error on the table below and follow the corresponding link under So l uti o n for detailed
troubleshooting information.
T ab le B.1. Co mmo n lib virt erro rs
Erro r Descrip t io n of p ro b lem So lu t io n
l i bvi rtd fai l ed to
start
The lib virt daemon failed to
start. However, there is no
information about this error in
/var/l o g /messag es.
Section B.1, “ lib virt d failed to
start”
C anno t read C A
certi fi cate
This is one of several errors
that occur when the URI fails to
connect to the hypervisor.
Section B.2, “ The URI failed to
connect to the hypervisor”
Fai l ed to co nnect
so cket . . . :
P ermi ssi o n d eni ed
This is one of several errors
that occur when the URI fails to
connect to the hypervisor.
Section B.2, “ The URI failed to
connect to the hypervisor”
Other connectivity errors These are other errors that
occur when the URI fails to
connect to the hypervisor.
Section B.2, “ The URI failed to
connect to the hypervisor”
Internal erro r g uest
C P U i s no t co mpati bl e
wi th ho st C P U
The guest virtual machine
cannot be started because the
host and guest processors are
different.
Section B.3, “ The guest virtual
machine cannot be started:
i nternal erro r g uest
C P U i s no t co mpati bl e
wi th ho st C P U”
Fai l ed to create d o mai n
fro m vm. xml erro r:
mo ni to r so cket d i d no t
sho w up. : C o nnecti o n
refused
The guest virtual machine (or
domain) starting fails and
returns this error or similar.
Section B.4, “ Guest starting
fails with error: mo ni to r
so cket d i d no t sho w up”
Internal erro r canno t
fi nd character d evi ce
(nul l )
This error can occur when
attempting to connect a guest's
console. It reports that there is
no serial console configured
for the guest virtual machine.
Section B.5, “ Internal erro r
canno t fi nd character
d evi ce (nul l )”
No bo o t d evi ce After building a guest virtual
machine from an existing disk
image, the guest booting stalls.
However, the guest can start
successfully using the Q EMU
command directly.
Section B.6, “ Guest virtual
machine booting stalls with
error: No bo o t d evi ce”
T he vi rtual netwo rk
"default" has no t been
started
If the default network (or other
locally-created network) is
unable to start, any virtual
machine configured to use that
network for its connectivity will
also fail to start.
Section B.7, “ Virtual network
default has not been started”
Common libvirt errors and t roublesh oot ing
127