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.
Bug 1309201 - blkdebug: Operation not supported
Summary: blkdebug: Operation not supported
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Fam Zheng
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-17 07:43 UTC by Qianqian Zhu
Modified: 2016-07-05 07:31 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-05 07:31:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Qianqian Zhu 2016-02-17 07:43:18 UTC 
Description of problem:
qemu-kvm: -drive if=none,id=drive0,rerror=stop,file=blkdebug:blkdebug.cfg:test.raw: could not open disk image blkdebug:blkdebug.cfg:test.raw: Operation not supported

Version-Release number of selected component (if applicable):
qemu-img-0.12.1.2-2.487.el6.x86_64
qemu-kvm-0.12.1.2-2.487.el6.x86_64
kernel-2.6.32-584.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1.# cat blkdebug.conf
[inject-error]
event = "read_aio"
errno = "28"
2.# qemu-img create test.raw 1G
3.# /usr/libexec/qemu-kvm -enable-kvm -m 1024 -cpu host -device virtio-scsi-pci -drive if=none,id=drive0,rerror=stop,file=blkdebug:blkdebug.cfg:test.raw  -device scsi-hd,drive=drive0 -monitor stdio

Actual results:
qemu-kvm: -drive if=none,id=drive0,rerror=stop,file=blkdebug:blkdebug.cfg:test.raw: could not open disk image blkdebug:blkdebug.cfg:test.raw: Operation not supported

Expected results:
qemu launched and trigger error like this:
[root@hp-dl388g7-02 ~]# /usr/libexec/qemu-kvm -enable-kvm -m 1024 -cpu host -device virtio-scsi-pci -drive if=none,id=drive0,rerror=stop,file=blkdebug:blkdebug.cfg:test.raw  -device scsi-hd,drive=drive0 -monitor stdio
QEMU 2.1.2 monitor - type 'help' for more information
(qemu) VNC server running on `::1:5900'
block I/O error in device 'drive0': No space left on device (28)

Additional info:
The expected result is from rhel7 with qemu-kvm-rhev-2.1.2-23.el7.x86_64, where blkdebug works well.
Comment 2 Fam Zheng 2016-04-11 06:34:53 UTC 
This is not a user visible feature. I'm not sure how important this is for RHEL 6. What is to achieve here? Can you give some justification in additional to the expectation?
Comment 3 Qianqian Zhu 2016-04-12 01:41:50 UTC 
(In reply to Fam Zheng from comment #2)
> This is not a user visible feature. I'm not sure how important this is for
> RHEL 6. What is to achieve here? Can you give some justification in
> additional to the expectation?

For my perspective, this feature is only for testing purpose, it might help to accomplish some test cases or trigger some potential bugs, but anyway, this might be in low severity.
Note You need to log in before you can comment on or make changes to this bug.