Created attachment 492703 [details]
gdb generated log of issue

Description of problem:
libvirt crash when you run loads of "virsh domstat vm_name" 

Version-Release number of selected component (if applicable):
0.9.0 (and all older versions)

How reproducible:
It's easily reproducible with fedora core 14 and libvirt-0.9.0 

Steps to Reproduce:
1.Install a fedora core 14 and configure libvirt-0.9.0  with netcf
2.Run some vms, and let some other vms be off
3.Put vms' nics on different bridge and isolated network
4.save this script to a file and name it putload:
#!/bin/bash
vms=( vm1 vm2 vm3 vm4 vm5 )
for i in `seq 10000`;
do
        sleep 1
        for vm in "${vms[@]}";
        do
                virsh domstate $vm
        done
done
5. run putload script more than 5 times at the same time like this
./putload & sleep 1 && ./putload & sleep 1 && ./putload & sleep 1 && ./putload & sleep 1 && ./putload & sleep 1 && ./putload 

6. some times after some minutes, and sometime after some hours libvirtd crash
NOTICE: be patient some times it takes more than 12 hours to crash.

  
Actual results:
libvirtd crash

Expected results:
libvirtd should be stable and not crash at all

Additional info:
I think it's related to netcf and fedora, because I haven't had such problem with debian and ubuntu as they don't use netcf. I attached gdb.txt to this bug report.
It's really urgent because you can't run any monitoring and HA solution with virsh and libvirtd with such a bug, as you need to also watch libvirtd daemon.