Tested with qemu-kvm-2.12.0-84.module+el8.1.0+3980+a02d9447, not hit this issue. So set status to VERIFIED.


Versions:
kernel-4.18.0-131.el8.x86_64
qemu-kvm-2.12.0-84.module+el8.1.0+3980+a02d9447


Steps:
1. Mount the gluster volume to local host, and full write it;

# mount.glusterfs gluster-virt-qe-01.lab.eng.pek2.redhat.com:/vol /home/gluster/
# dd if=/dev/zero of=/home/gluster/test.bin bs=1M oflag=direct
dd: error writing '/home/gluster/test.bin': No space left on device


2. Boot the vm with the image stored on the gluster volume;
/usr/libexec/qemu-kvm \
    -name 'rhel8.1' \
    -machine q35 \
    -nodefaults \
    -vga qxl \
    -object iothread,id=iothread0 \
    -rtc base=utc,clock=host,driftfix=slew \
    -device pcie-root-port,id=pcie.0-root-port-3,slot=3,chassis=3,addr=0x3,bus=pcie.0 \
    -drive if=none,cache=none,format=qcow2,id=drive_image1,aio=native,file=gluster://gluster-virt-qe-01.lab.eng.pek2.redhat.com/vol/rhel810-64-virtio.qcow2 \
    -device  virtio-blk-pci,id=image2,drive=drive_image1,write-cache=on,iothread=iothread0,bus=pcie.0-root-port-3,bootindex=0 \
    -device   pcie-root-port,id=pcie.0-root-port-2,slot=2,chassis=2,addr=0x2 \
    -device virtio-scsi-pci,id=scsi0,iothread=iothread0,bus=pcie.0-root-port-2,addr=0x0 \
    -blockdev driver=raw,cache.direct=off,cache.no-flush=on,file.filename=/home/data.qcow2,node-name=data_disk1,file.driver=file \
    -device scsi-hd,drive=data_disk1,id=data1,bootindex=1 \
    -vnc :0  \
    -monitor stdio \
    -m 4096 \
    -smp 8 \
    -device virtio-net-pci,mac=9a:b5:b6:b1:b2:b3,id=idMmq1jH,vectors=4,netdev=idxgXAlm,bus=pcie.0,addr=0x9  \
    -netdev tap,id=idxgXAlm \
    -qmp tcp:localhost:4444,server,nowait  \
    -device nec-usb-xhci,id=usb1,bus=pcie.0,addr=0x5 -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \

3. check vm status with qmp

# telnet localhost 4444
Trying ::1...
Connected to localhost.
Escape character is '^]'.
{"QMP": {"version": {"qemu": {"micro": 0, "minor": 12, "major": 2}, "package": "qemu-kvm-2.12.0-84.module+el8.1.0+3980+a02d9447"}, "capabilities": []}}

{"execute":"qmp_capabilities"}
{"return": {}}

{"execute":"query-status"}
{"return": {"status": "io-error", "singlestep": false, "running": false}}

{"timestamp": {"seconds": 1566287354, "microseconds": 377626}, "event": "RESUME"}
{"timestamp": {"seconds": 1566287354, "microseconds": 378318}, "event": "BLOCK_IO_ERROR", "data": {"device": "drive_image1", "nospace": false, "node-name": "#block254", "reason": "No medium found", "operation": "write", "action": "report"}}
{"timestamp": {"seconds": 1566287354, "microseconds": 379323}, "event": "BLOCK_IO_ERROR", "data": {"device": "drive_image1", "nospace": false, "node-name": "#block254", "reason": "No medium found", "operation": "write", "action": "report"}}
{"timestamp": {"seconds": 1566287354, "microseconds": 379582}, "event": "BLOCK_IO_ERROR", "data": {"device": "drive_image1", "nospace": false, "node-name": "#block254", "reason": "No medium found", "operation": "write", "action": "report"}}

4. check vm status in hmp:
    (qemu) info status 
VM status: paused (io-error)

5. Quit vm;
  (qemu)q


Actual result:
No core dump and qemu can quit successfully although vm in "paused(io-error)" status.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:3345