Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
------------------------
block stream to a non-enough space path, block stream will stop when there is no space left, info block-jobs only shows "No active jobs", guest runs until when there is writing triggers "block I/O error in device 'drive-virtio-disk0': No space left on device (28)" and stopped, there should be a "block stream failed" prompt when using info block-jobs, or is there a way libvirt can tell this? 


Version-Release number of selected component (if applicable):
--------------------------------------------------------------
qemu-kvm-0.12.1.2-2.262.el6rhev.x86_64


How reproducible:
------------------
100%

Steps to Reproduce:
--------------------
1. qemu-img -f raw disk 1G
2. mkfs.ext4 disk
3. mount -o loop disk /path
4. (qemu) snapshot_blkdev drive-virtio-disk0 /path/sn1 qcow2
5. (qemu) block_stream drive-virtio-disk0
  
Actual results:
---------------
after no space left in /path, block stream stops:

(qemu) info block-jobs 
Streaming device drive-virtio-disk0: Completed 1968177152 of 21474836480 bytes, speed limit 0 bytes/s
(qemu) info block-jobs 
No active jobs

If you connect with QMP, you should get a BLOCK_JOB_COMPLETED monitor event with an error description.

(In reply to comment #2)
> If you connect with QMP, you should get a BLOCK_JOB_COMPLETED monitor event
> with an error description.

Right, the main test/verification tool should be QMP

Verified on QMP, list here for reference:

{ "execute": "block_stream", "arguments": { "device": "drive-virtio-disk0" } }
{"return": {}}

{"timestamp": {"seconds": 1332755362, "microseconds": 687432}, "event": "BLOCK_JOB_COMPLETED", "data": {"device": "drive-virtio-disk0", "len": 21474836480, "offset": 2036858880, "speed": 0, "type": "stream", "error": "No space left on device"}}