On Fri, Mar 07, 2014 at 01:06:10PM +0800, Wangpan wrote: > bug address: https://bugzilla.redhat.com/show_bug.cgi?id=1066801 > I can reproduce it at master/v1.2.1-maint/v1.1.4-maint/v1.1.3.4 release branches everytime, > but cann't reproduce it at v1.2.1，so I believe this bug is imported by the maintain patches after v1.2.1 release. > > Steps to Reproduce: > 1.create many VMs(40 in my env) on the host > 2.kill -9 `pid of libvirtd` > 3.start libvirtd by using service libvirt-bin start > > Actual results: > virsh version/list command is hung there without any responses > > Expected results: > virsh version/list return the correct things > > Additional info: > if there are few VMs(1 vm in my env), the virsh version command is OK I've reproduced the problem - the key thing I was missing is that it only occurs if every VM is using a different named nwfilter. It they all use 'clean-traffic' it is fine, but if they use 'clean-traffic-xxx' where 'xxx' is the name of the VM it deadlocks. This is why I never spotted it before :-( Please try out this patch https://www.redhat.com/archives/libvir-list/2014-March/msg00501.html Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list