Red Hat Bugzilla – Bug 1582122
IOERROR pause code lost after resuming a VM while I/O error is still present [rhel-7.5.z]
Last modified: 2018-08-29 03:18:46 EDT
This bug has been copied from bug #1566153 and has been proposed to be backported to 7.5 z-stream (EUS).
Fix included in qemu-kvm-rhev-2.10.0-21.el7_5.4
Verified this bug on qemu-kvm-rhev-2.10.0-21.el7_5.4.x86_64: 1. Create a scratch image $ dd if=/dev/zero of=scratch.img bs=1M count=100 2. Prepare blkdebug configuration: $ cat >blkdebug.conf <<EOF [inject-error] event = "write_aio" errno = "5" EOF 3. Run a guest with an additional scratch disk -drive id=drive_image2,if=none,werror=stop,file=blkdebug:/root/blkdebug.conf:scratch.img,format=raw \ -device scsi-hd,id=image2,drive=drive_image2 \ 4. Connect to the QMP socket 5. Boot the guest. 6. In the guest, write to the scratch disk # dd if=/dev/zero of=/dev/sdb count=1 7. Issue QMP command 'cont': QMP> { "execute": "cont" } After step 6: {"timestamp": {"seconds": 1528789960, "microseconds": 913452}, "event": "BLOCK_IO_ERROR", "data": {"device": "drive_image2", "nospace": false, "__com.redhat_reason": "eio", "node-name": "#block437", "reason": "Input/output error", "operation": "write", "action": "stop"}} {"timestamp": {"seconds": 1528789960, "microseconds": 916870}, "event": "STOP"} After step 7: {"timestamp": {"seconds": 1528790040, "microseconds": 507430}, "event": "RESUME"} {"timestamp": {"seconds": 1528790040, "microseconds": 508316}, "event": "BLOCK_IO_ERROR", "data": {"device": "drive_image2", "nospace": false, "__com.redhat_reason": "eio", "node-name": "#block437", "reason": "Input/output error", "operation": "write", "action": "stop"}} {"timestamp": {"seconds": 1528790040, "microseconds": 509598}, "event": "STOP"} The event ordering 'RESUME' -> 'BLOCK_IO_ERROR' -> 'STOP' is triggered as expected. Thanks.
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-2018:2060
*** Bug 1612943 has been marked as a duplicate of this bug. ***