[libvirt] libvirtd 1.0.6 refuses to start

Franky Van Liedekerke liedekef at telenet.be
Tue Jun 11 14:59:52 UTC 2013


I just downloaded and compiled libvirtd on the same server as I did 
1.0.4. Upon updating, libvirtd refuses to start, with this in the 
logfile (obfuscated the hostname by xxx's):

2013-06-11 13:43:49.154+0000: 3336: info : libvirt version: 1.0.6, 
package: 1.el6 (Unknown, 2013-06-06-14:57:07, xxxxxxxx)
2013-06-11 13:43:49.154+0000: 3336: error : virFileReadAll:1195 : 
Failed to open file '/sys/class/fc_host//host0/max_npiv_vports': No such 
file or directory
2013-06-11 13:43:49.159+0000: 3336: error : detect_scsi_host_caps:87 : 
Failed to read max_npiv_vports for host1
2013-06-11 13:43:49.163+0000: 3336: error : virFileReadAll:1195 : 
Failed to open file '/sys/class/fc_host//host0/max_npiv_vports': No such 
file or directory
2013-06-11 13:43:49.163+0000: 3336: error : detect_scsi_host_caps:87 : 
Failed to read max_npiv_vports for host2
2013-06-11 13:43:49.386+0000: 3336: error : virLockManagerPluginNew:175 
: Failed to load plugin /usr/lib64/libvirt/lock-driver/lockd.so: 
/usr/lib64/libvirt/lock-driver/lockd.so: undefined symbol: 
virProcessGetStartTime
2013-06-11 13:43:49.386+0000: 3336: error : virStateInitialize:831 : 
Initialization of QEMU state driver failed
2013-06-11 13:43:49.386+0000: 3336: error : daemonRunStateInit:887 : 
Driver state initialization failed

So it seems two issues are present here:

1) it searches for /sys/class/fc_host//host0/max_npiv_vports for both 
host1 and host2. Imho this path needs to be 
/sys/class/fc_host//host1/max_npiv_vports and 
/sys/class/fc_host//host2/max_npiv_vports respectively.

2) the undefined symbol problem: seems a linking issue, no? The build 
worked just fine on rhel6 with all patches applied.

For now I reverted back to 1.0.4. Hope this helps to debug :-)

Also: I created a bug report for 1.0.4/1.0.6 concerning the init 
scripts:
https://bugzilla.redhat.com/show_bug.cgi?id=971408
Part of it (the virtlock socket) seems to be in the latest code 
already, but I believe the other issues mentioned are valid as well.

With friendly regards,

Franky




More information about the libvir-list mailing list