just before the above "Broken pipe", qom-list failed and errno is 32 which means "Broken pipe".
2017-02-09 18:16:35.362+0000: 16737: info : qemuMonitorIOWrite:528 : QEMU_MONITOR_IO_WRITE: mon=0x7fd01c014000 buf={"execute":"qom-list","arguments":{"path":"//machine/i440fx/pam-pci[15]"},"id":"libvirt-13"} len=94 ret=-1 errno=32
Then the corresponding process of the qom-list could be closed.
At the same time, qemuProcessKill happened:
2017-02-09 18:16:35.362+0000: 16737: debug : qemuProcessKill:5203 : vm=0x7fd01000d860 name=instance-00000019 pid=19945 flags=2
According to the log of instance-00000019 (http://logs.openstack.org/59/426459/4/check/gate-tempest-dsvm-neutron-full-ubuntu-xenial/0222b58/logs/libvirt/qemu/instance-00000019.txt.gz),
2017-02-09T18:16:34.314499Z qemu-system-x86_64: terminating on signal 15 from pid 16737
But ps.txt doesn't contain pid 16737, so we cannon know who kills the qemu-system-x86_64.
just before the above "Broken pipe", qom-list failed and errno is 32 which means "Broken pipe".
2017-02-09 18:16:35.362+0000: 16737: info : qemuMonitorIOWr ite:528 : QEMU_MONITOR_ IO_WRITE: mon=0x7fd01c014000 buf={"execute" :"qom-list" ,"arguments" :{"path" :"//machine/ i440fx/ pam-pci[ 15]"}," id":"libvirt- 13"}
len=94 ret=-1 errno=32
Then the corresponding process of the qom-list could be closed.
At the same time, qemuProcessKill happened:
2017-02-09 18:16:35.362+0000: 16737: debug : qemuProcessKill :5203 : vm=0x7fd01000d860 name=instance- 00000019 pid=19945 flags=2
According to the log of instance-00000019 (http:// logs.openstack. org/59/ 426459/ 4/check/ gate-tempest- dsvm-neutron- full-ubuntu- xenial/ 0222b58/ logs/libvirt/ qemu/instance- 00000019. txt.gz),
2017-02- 09T18:16: 34.314499Z qemu-system-x86_64: terminating on signal 15 from pid 16737
But ps.txt doesn't contain pid 16737, so we cannon know who kills the qemu-system-x86_64.