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:
we should disable and give friendly error warning message if not support block_resize for libiscsi storage disk or fix it to work well.
Version-Release number of selected component (if applicable):
host info:
3.10.0-10.el7.x86_64
qemu-kvm-1.5.3-20.el7.x86_64
seabios-1.7.2.2-4.el7.x86_64
guest info:
rhel6.5-32bit
How reproducible:
100%
Steps to Reproduce:
1.prepare a libiscsi storage(My libiscsi storage is about 30G here).
2.boot guest with this libiscsi storage.
e.g:/usr/libexec/qemu-kvm -M pc -cpu SandyBridge -enable-kvm...-drive file=iscsi://10.66.6.82:3260/iqn.2013-11.com.example:storage.disk1.juli.xyz/2,if=none,id=drive-data-disk,format=raw,cache=none,serial="QEMU-DISK" -device virtio-blk-pci,bus=pci.0,addr=0x7,drive=drive-data-disk,id=data-disk -iscsi id=iqn-sluo
3.do block_resize via HMP/QMP monitor.
Actual results:
after step 3,
It fail to do enlarging images and the message not very correctly, like:
(qemu) block_resize drive-data-disk 50G
Could not resize: Invalid argument
{ "execute": "block_resize", "arguments": { "device": "drive-data-disk", "size": 53687091200 }}
{"error": {"class": "GenericError", "desc": "Could not resize: Invalid argument"}}
If do shrinking images, it can run the shrinking command correctly, but it did not make effect in guest which not detect the logical block changes.
(qemu) block_resize drive-data-disk 10G
(qemu)
{ "execute": "block_resize", "arguments": { "device": "drive-data-disk", "size": 10737418240 }}
{"return": {}}
Expected results:
we should disable and give more friendly error warning message if not support block_resize for libiscsi storage disk or fix it to work well.
Additional info:
Description of problem: we should disable and give friendly error warning message if not support block_resize for libiscsi storage disk or fix it to work well. Version-Release number of selected component (if applicable): host info: 3.10.0-10.el7.x86_64 qemu-kvm-1.5.3-20.el7.x86_64 seabios-1.7.2.2-4.el7.x86_64 guest info: rhel6.5-32bit How reproducible: 100% Steps to Reproduce: 1.prepare a libiscsi storage(My libiscsi storage is about 30G here). 2.boot guest with this libiscsi storage. e.g:/usr/libexec/qemu-kvm -M pc -cpu SandyBridge -enable-kvm...-drive file=iscsi://10.66.6.82:3260/iqn.2013-11.com.example:storage.disk1.juli.xyz/2,if=none,id=drive-data-disk,format=raw,cache=none,serial="QEMU-DISK" -device virtio-blk-pci,bus=pci.0,addr=0x7,drive=drive-data-disk,id=data-disk -iscsi id=iqn-sluo 3.do block_resize via HMP/QMP monitor. Actual results: after step 3, It fail to do enlarging images and the message not very correctly, like: (qemu) block_resize drive-data-disk 50G Could not resize: Invalid argument { "execute": "block_resize", "arguments": { "device": "drive-data-disk", "size": 53687091200 }} {"error": {"class": "GenericError", "desc": "Could not resize: Invalid argument"}} If do shrinking images, it can run the shrinking command correctly, but it did not make effect in guest which not detect the logical block changes. (qemu) block_resize drive-data-disk 10G (qemu) { "execute": "block_resize", "arguments": { "device": "drive-data-disk", "size": 10737418240 }} {"return": {}} Expected results: we should disable and give more friendly error warning message if not support block_resize for libiscsi storage disk or fix it to work well. Additional info: