On Sun, May 13, 2012 at 11:51:48PM +0800, Shu Ming wrote:
Hi, Recently, I found that my host in engine was always in a "unassigned state" after the host node was installed. After looking into the vdsm.log, it seemed that vdsm failed to call libvirt as an error, "libvirtError: Cannot write data: Broken pipe". When I started virsh in the host node at that time, a warning was given "WARNING: no socket to connect to" and core dumped with "virsh net-list". It looks like that no right socket was created for virsh to connect to libvirtd. Any comments about this problem? The followings are my steps in the node:
[root@ovirt-node1 ~]# rpm -qa |grep vdsm vdsm-cli-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-python-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-hook-vhostmd-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-4.9.6-0.183.git107644d.fc16.shuming1336622293.x86_64 vdsm-reg-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-debug-plugin-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-hook-faqemu-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-bootstrap-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch [root@ovirt-node1 ~]# [root@ovirt-node1 ~]# ps -ef |grep libvirt
libvirt-daemon-0.9.11-1.fc17.x86_64 libvirt-daemon-config-nwfilter-0.9.11-1.fc17.x86_64 libvirt-client-0.9.11-1.fc17.x86_64 libvirt-daemon-config-network-0.9.11-1.fc17.x86_64 libvirt-python-0.9.11-1.fc17.x86_64
[root@ovirt-node1 ~]# virsh net-list WARNING: no socket to connect to Segmentation fault
I think that merits a libvirt bug. please attach strace output to bugzilla.
[root@ovirt-node1 ~]#
[root@ovirt-node1 ~]# ps -ef |grep vdsm root 1299 1 0 23:10 ? 00:00:00 /usr/sbin/libvirtd --listen # by vdsm
The command line of libvirt process is very odd - the comment that vdsm puts into /etc/sysconfig/libvirtd is somehow taken verbatim. That's bad, and may be related to Fedora 17's systemd services. Try to remove the comment and restart libvirtd to see if this is the case.
/usr/share/vdsm/respawn --minlifetime 10 --daemon --masterpid /var/run/vdsm/respawn.pid /usr/share vdsm/vdsm vdsm 1919 1917 0 23:10 ? 00:00:06 /usr/bin/python /usr/share/vdsm vdsm root 1940 1919 0 23:10 ? 00:00:00 /usr/bin/sudo -n /usr/bin/python /usr/share/vdsm/supervdsmServer.py 709dfdde-a668-4227-a206-3d8686b4cfa1 1919 root 1941 1940 0 23:10 ? 00:00:00 /usr/bin/python /usr/share/vdsm/supervdsmServer.py 709dfdde-a668-4227-a206-3d8686b4cfa1 1919 root 3711 3055 0 23:22 pts/0 00:00:00 vim /var/log/vdsm/vdsm.log root 4358 4103 0 23:30 pts/1 00:00:00 grep --color=auto vdsm [
[root@ovirt-node1 ~]# ps -ef |grep libvirtd root 4421 1 2 23:31 ? 00:00:00 /usr/sbin/libvirtd --listen # by vdsm root 4750 4103 0 23:31 pts/1 00:00:00 grep --color=auto libvirtd
Thanks for testing on F17!
Dan.