11:06 p.m.
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
Thanks in advance!
2014-03-07
Wangpan
3:48 a.m.
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
Can you provide a full stack trace (thread apply all bt) to the bug
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 :|
10:17 a.m.
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 :|
9:59 p.m.
Please try out this patch
https://www.redhat.com/archives/libvir-list/2014-March/msg00501.html
I have tested this patch on master branch, and it works OK now, thanks Daniel !
2014-03-10
Wangpan
5:20 a.m.
On Mon, Mar 10, 2014 at 10:59:08AM +0800, Wangpan wrote:
>Please try out this patch
>
>https://www.redhat.com/archives/libvir-list/2014-March/msg00501.html
I have tested this patch on master branch, and it works OK now, thanks Daniel !
Thanks for testing. I'll get this back onto the stable branches too.
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 :|
3910
days inactive
3913
days old
4 comments
2 participants
participants (2)
-
Daniel P. Berrange -
Wangpan