Hi experts,
The libvirtd can’t start on my server after the server interruption
of power supply, the status is below:
[root@openstack3 libvirt]# service libvirtd status
Redirecting to /bin/systemctl status libvirtd.service
libvirtd.service - Virtualization daemon
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled)
Active: failed (Result: signal) since Tue 2015-03-24 16:10:31 CST; 7min
ago
Process: 27372 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS (code=killed,
signal=SEGV)
Main PID: 27372 (code=killed, signal=SEGV)
Mar 24 16:10:31 openstack3 libvirtd[27372]: 2015-03-24 08:10:31.412+0000:
27383: debug : virFileClose:90 : Closed fd 22
Mar 24 16:10:31 openstack3 libvirtd[27372]: 2015-03-24 08:10:31.412+0000:
27383: debug : virFileClose:90 : Closed fd 22
Mar 24 16:10:31 openstack3 libvirtd[27372]: 2015-03-24 08:10:31.412+0000:
27383: debug : virFileClose:90 : Closed fd 22
Mar 24 16:10:31 openstack3 libvirtd[27372]: 2015-03-24 08:10:31.412+0000:
27383: debug : virFileClose:90 : Closed fd 22
Mar 24 16:10:31 openstack3 libvirtd[27372]: 2015-03-24 08:10:31.413+0000:
27383: debug : virFileClose:90 : Closed fd 22
Mar 24 16:10:31 openstack3 libvirtd[27372]: 2015-03-24 08:10:31.413+0000:
27383: debug : virStateInitialize:847 : Running global init for netcf state
driver
Mar 24 16:10:31 openstack3 libvirtd[27372]: 2015-03-24 08:10:31.413+0000:
27383: debug : virObjectNew:199 : OBJECT_NEW: obj=0x7f73f0080d00
classname=virNetcfDriverState
Mar 24 16:10:31 openstack3 libvirtd[27372]: ====== end of log =====
Mar 24 16:10:31 openstack3 systemd[1]: libvirtd.service: main process
exited, code=killed, status=11/SEGV
Mar 24 16:10:31 openstack3 systemd[1]: Unit libvirtd.service entered failed
state.
And the attachment is the log after restart the libvirtd.
After long time search on google, I didn’t get any useful information, so
anyone can give me some hint on this issue?
-BR,
Andy