IN http://logs.openstack.org/66/401366/4/gate/gate-tempest-dsvm-neutron-full-ubuntu-xenial/3deacc5/logs/libvirt/qemu/instance-0000001a.txt.gz#_2016-12-01_18_16_08_032 I see:
2016-12-01T18:16:04.707300Z qemu-system-x86_64: terminating on signal 15 from pid 17078
Which matches closely (200ms gap) with http://logs.openstack.org/66/401366/4/gate/gate-tempest-dsvm-neutron-full-ubuntu-xenial/3deacc5/logs/libvirt/libvirtd.txt.gz#_2016-12-01_18_16_04_907
2016-12-01 18:16:04.907+0000: 17078: error : qemuMonitorIORead:580 : Unable to read from monitor: Connection reset by peer
So I think the qemuMonitorIORead errors are possibly related just to VMs being normally shutdown.
IN http:// logs.openstack. org/66/ 401366/ 4/gate/ gate-tempest- dsvm-neutron- full-ubuntu- xenial/ 3deacc5/ logs/libvirt/ qemu/instance- 0000001a. txt.gz# _2016-12- 01_18_16_ 08_032 I see:
2016-12- 01T18:16: 04.707300Z qemu-system-x86_64: terminating on signal 15 from pid 17078
Which matches closely (200ms gap) with http:// logs.openstack. org/66/ 401366/ 4/gate/ gate-tempest- dsvm-neutron- full-ubuntu- xenial/ 3deacc5/ logs/libvirt/ libvirtd. txt.gz# _2016-12- 01_18_16_ 04_907
2016-12-01 18:16:04.907+0000: 17078: error : qemuMonitorIORe ad:580 : Unable to read from monitor: Connection reset by peer
So I think the qemuMonitorIORead errors are possibly related just to VMs being normally shutdown.