I have just verified that the reproducer for Red Hat Enterprise Linux is valid for Bionic:
1.Start a guest: $ virsh start test1
2.Do 'virsh list' in a loop: $ for i in {1..1000}; do virsh list; done
3.Open another terminal, do 'virsh domstats' in a loop: $ for i in {1..1000}; do virsh domstats; done
4.Check the libvirtd.log: $ cat /var/log/libvirt/libvirtd.log | grep -i "Hash operation not allowed during" 2018-09-04 06:57:00.761+0000: 28687: error : virHashForEach:597 : Hash operation not allowed during iteration 2018-09-04 06:57:00.773+0000: 28684: error : virHashForEach:597 : Hash operation not allowed during iteration 2018-09-04 06:57:02.040+0000: 28687: error : virHashForEach:597 : Hash operation not allowed during iteration 2018-09-04 06:57:06.567+0000: 28687: error : virHashForEach:597 : Hash operation not allowed during iteration 2018-09-04 06:57:09.761+0000: 28684: error : virHashForEach:597 : Hash operation not allowed during iteration
https://bugzilla.redhat.com/show_bug.cgi?id=1581364#c7
With the aforementioned patch, this error is not produced any more.
I have just verified that the reproducer for Red Hat Enterprise Linux is valid for Bionic:
1.Start a guest:
$ virsh start test1
2.Do 'virsh list' in a loop:
$ for i in {1..1000}; do virsh list; done
3.Open another terminal, do 'virsh domstats' in a loop:
$ for i in {1..1000}; do virsh domstats; done
4.Check the libvirtd.log: libvirt/ libvirtd. log | grep -i "Hash operation not allowed during"
$ cat /var/log/
2018-09-04 06:57:00.761+0000: 28687: error : virHashForEach:597 : Hash operation not allowed during iteration
2018-09-04 06:57:00.773+0000: 28684: error : virHashForEach:597 : Hash operation not allowed during iteration
2018-09-04 06:57:02.040+0000: 28687: error : virHashForEach:597 : Hash operation not allowed during iteration
2018-09-04 06:57:06.567+0000: 28687: error : virHashForEach:597 : Hash operation not allowed during iteration
2018-09-04 06:57:09.761+0000: 28684: error : virHashForEach:597 : Hash operation not allowed during iteration
https:/ /bugzilla. redhat. com/show_ bug.cgi? id=1581364# c7
With the aforementioned patch, this error is not produced any more.