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:
this issue was separated from https://bugzilla.redhat.com/show_bug.cgi?id=877836#c28 
Fail to initialize the the data disk specified x-data-plane=on via 'Device Manager' in win7 64bit guest using the RPMs v3, with the prompt error 'The request could not be performed because of an I/O device error', i will atttach the log of screenshot later.

BTW, if specified x-data-plane=off to the data disk, it can be initialized and formatted successfully.

Version-Release number of selected component (if applicable):
host info:
kernel-2.6.32-348.el6.x86_64
qemu-kvm-0.12.1.2-2.345.el6.test.x86_64
guest info:
win7 64bit
virtio-win-prewhql-0.1-49 

qemu-kvm command line:
e.g:...-drive file=/home/windows_7_ultimate_sp1_x64.raw,if=none,id=drive-virtio-disk,format=raw,cache=none,aio=native,werror=stop,rerror=stop -device virtio-blk-pci,bus=pci.0,addr=0x4,scsi=off,x-data-plane=off,drive=drive-virtio-disk,id=virtio-disk,bootindex=1...-drive file=/dev/vg-qz/sluo-data-disk,if=none,id=drive-data-disk,format=raw,cache=none,aio=native,werror=stop,rerror=stop -device virtio-blk-pci,bus=pci.0,addr=0x6,scsi=off,x-data-plane=on,drive=drive-data-disk,id=data-disk...

Expected results:
it can initialize and format the data disk successfully.

Additional info:

Please try this build, it includes Windows patches:

https://brewweb.devel.redhat.com/taskinfo?taskID=5273068

(In reply to comment #2)
> Please try this build, it includes Windows patches:
> 
> https://brewweb.devel.redhat.com/taskinfo?taskID=5273068
ok, no problem, i will update the results here after i try.

Verify this issue qemu-kvm-0.12.1.2-2.352.el6 with the same steps as comment #0.

host info:
kernel-2.6.32-355.el6.x86_64
qemu-kvm-0.12.1.2-2.352.el6
guest info:
win7 64bit
virtio-win-prewhql-0.1-49 

Results:
it can initialize and format the data disk successfully without any problem.

Base on above, this issue has been fixed successfully.

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.

http://rhn.redhat.com/errata/RHBA-2013-0527.html