Installation guide

No guest virtual machines are
present when lib virt d is
started
The lib virt daemon is
successfully started, but no
guest virtual machines appear
to be present when running
vi rsh l i st --al l .
Section B.15, “ No guest virtual
machines are present when
lib virt d is started
Unabl e to co nnect to
server at ' ho st: 16 50 9 ' :
C o nnecti o n refused . . .
erro r: fai l ed to
co nnect to the
hypervi so r
While lib virt d should listen on
TCP ports for connections, the
connection to the hypervisor
fails.
Section B.16, “ Unable to
connect to server at
'host:16509': Connection
refused ... error: failed to
connect to the hypervisor
Common XML errors lib virt uses XML documents to
store structured data. Several
common errors occur with XML
documents when they are
passed to lib virt through the
API. This entry provides
instructions for editing guest
XML definitions, and details
common errors in XML syntax
and configuration.
Section B.17, “Common XML
errors
Erro r Descrip t io n of p ro b lem So lu t io n
B.1. libvirt d failed t o st art
Symp t o m
The lib virt daemon does not start automatically. Starting the lib virt daemon manually
fails as well:
# /etc/init.d/libvirtd start
* Caching service dependencies ...
[ ok ]
* Starting libvirtd ...
/usr/sbin/libvirtd: error: Unable to initialize network sockets.
Check /var/log/messages or run without --daemon for more info.
* start-stop-daemon: failed to start `/usr/sbin/libvirtd'
[ !! ]
* ERROR: libvirtd failed to start
Moreover, there is not ' mo re i nfo ' about this error in /var/l og /messag es.
In vest ig at io n
Change lib virt ' s logging in /etc/l i bvi rt/l i bvi rtd .co nf by uncommenting the line
below. To uncomment the line, open the /etc/l ibvi rt/l i bvi rtd . co nf file in a text
editor, remove the hash (or #) symbol from the beginning of the following line, and save the
change:
log_outputs="3:syslog:libvirtd"
Common libvirt errors and t roublesh oot ing
129