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:
fail to boot guest with x-data-plane=on specified for libiscsi storage disk, qemu will quit with warning message prompt 'drive is incompatible with x-data-plane, use format=raw,cache=none,aio=native'. We can fix it to work well or disable it with friendly warning message if not support it.
Also tried:
1.it can boot up guest with x-data-plane=off specified for libiscsi storage disk.
2.it can boot up guest with x-data-plane=on specified for local file storage disk.
Version-Release number of selected component (if applicable):
host info:
3.10.0-50.el7.x86_64
qemu-kvm-rhev-1.5.3-19.el7.x86_64
seabios-1.7.2.2-4.el7.x86_64
guest info:
rhel6.5 32bit/64bit
2.6.32-425.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1.boot guest with x-data-plane=on specified for libiscsi storage disk.
e.g:/usr/libexec/qemu-kvm -M q35 -S -cpu SandyBridge -enable-kvm -m 2048 -smp 2,sockets=2,cores=1,threads=1 -no-kvm-pit-reinjection...-drive file=iscsi://10.66.6.82:3260/iqn.2013-11.com.example:storage.disk1.juli.xyz/5,if=none,id=drive-data-disk,format=raw,cache=none,aio=native,werror=stop,rerror=stop -device virtio-blk-pci,bus=pcie.0,addr=0x7,scsi=off,x-data-plane=on,config-wce=off,drive=drive-data-disk,id=data-disk -iscsi id=iqn1
2.boot guest with x-data-plane=off specified for libiscsi storage disk.
e.g:/usr/libexec/qemu-kvm -M q35 -S -cpu SandyBridge -enable-kvm -m 2048 -smp 2,sockets=2,cores=1,threads=1 -no-kvm-pit-reinjection...-drive file=iscsi://10.66.6.82:3260/iqn.2013-11.com.example:storage.disk1.juli.xyz/5,if=none,id=drive-data-disk,format=raw,cache=none,aio=native,werror=stop,rerror=stop -device virtio-blk-pci,bus=pcie.0,addr=0x7,scsi=off,x-data-plane=off,config-wce=off,drive=drive-data-disk,id=data-disk -iscsi id=iqn1
3.boot up guest with x-data-plane=on/off specified for local file storage disk.
e.g:/usr/libexec/qemu-kvm -M q35 -S -cpu SandyBridge -enable-kvm -m 2048 -smp 2,sockets=2,cores=1,threads=1 -no-kvm-pit-reinjection...-drive file=/home/my-data-disk.raw,if=none,id=drive-data-disk,format=raw,cache=none,aio=native,werror=stop,rerror=stop -device virtio-blk-pci,bus=pcie.0,addr=0x7,scsi=off,x-data-plane=on,config-wce=off,drive=drive-data-disk,id=data-disk
Actual results:
after step 1, qemu will quit and fail to boot up.
QEMU 1.5.3 monitor - type 'help' for more information
(qemu) qemu-kvm: -device virtio-blk-pci,bus=pcie.0,addr=0x7,scsi=off,x-data-plane=on,config-wce=off,drive=drive-data-disk,id=data-disk: drive is incompatible with x-data-plane, use format=raw,cache=none,aio=native
qemu-kvm: -device virtio-blk-pci,bus=pcie.0,addr=0x7,scsi=off,x-data-plane=on,config-wce=off,drive=drive-data-disk,id=data-disk: Device initialization failed.
qemu-kvm: -device virtio-blk-pci,bus=pcie.0,addr=0x7,scsi=off,x-data-plane=on,config-wce=off,drive=drive-data-disk,id=data-disk: Device initialization failed.
qemu-kvm: -device virtio-blk-pci,bus=pcie.0,addr=0x7,scsi=off,x-data-plane=on,config-wce=off,drive=drive-data-disk,id=data-disk: Device 'virtio-blk-pci' could not be initialized
after step 2, it can boot up successfully.
after step 3, it can boot up successfully.
Expected results:
We can fix it to work well with x-data-plane=on specified for libiscsi storage disk or disable it with friendly warning message if not support it.
Additional info: