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:
qemu-img fail to open the big(1000T) vdi format disk image with 'Invalid argument' error after created.
Version-Release number of selected component (if applicable):
host info:
3.10.0-183.el7.x86_64
qemu-kvm-rhev-2.1.2-4.el7
How reproducible:
100%
Steps to Reproduce:
1.create a big vdi image via qemu-img.
# qemu-img create -f vdi data-disk.vdi 1000TFormatting 'data-disk.vdi', fmt=vdi size=1099511627776000 static=off
2.use qemu-img to check the image info.
# qemu-img info data-disk.vdi
qemu-img: Could not open 'data-disk.vdi': Could not open 'data-disk.vdi': Invalid argument
Actual results:
Expected results:
It should open the big(1000T) vdi format disk image without any error via qemu-img.
Additional info:
It did not hit it with qemu-kvm-rhev-1.5.3-60.el7ev.
# qemu-img create -f vdi data-disk.vdi 1000T
Formatting 'data-disk.vdi', fmt=vdi size=1099511627776000 static=off
# qemu-img info data-disk.vdi
image: data-disk.vdi
file format: vdi
virtual size: 1000T (1099511627776000 bytes)
disk size: 2.0G
cluster_size: 1048576
Reproduce this bug using the following version:
qemu-kvm-rhev-2.1.2-23.el7.x86_64
kernel-3.10.0-232.el7.x86_64
Reproduce steps:
1.create a big vdi image via qemu-img.
# qemu-img create -f vdi data-disk.vdi 1000TFormatting 'data-disk.vdi', fmt=vdi size=1099511627776000 static=off
2.use qemu-img to check the image info.
# qemu-img info data-disk.vdi
qemu-img: Could not open 'data-disk.vdi': Could not open 'data-disk.vdi': Invalid argument
Test this bug using the following version:
qemu-kvm-rhev-2.2.0-8.el7.x86_64
kernel-3.10.0-232.el7.x86_64
Test steps:
1.create a 1000T vdi image via qemu-img.
# qemu-img create -f vdi data-disk.vdi 1000T
Formatting 'data-disk.vdi', fmt=vdi size=1099511627776000 static=off
qemu-img: data-disk.vdi: Unsupported VDI image size (size is 0x3e80000000000, max supported is 0x1fffff8000000)
2.create a 512T vdi image via qemu-img
# qemu-img create -f vdi data-disk.vdi 0x1fffff8000000
Formatting 'data-disk.vdi', fmt=vdi size=562949819203584 static=off
3. use qemu-img to check the imge info
# qemu-img info data-disk.vdi
image: data-disk.vdi
file format: vdi
virtual size: 512T (562949819203584 bytes)
disk size: 2.0G
cluster_size: 1048576
Test results:
qemu-img can create and check the maxsize 512T vdi image.
Based on the above results, I think this bug has been fixed.
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.
https://rhn.redhat.com/errata/RHBA-2015-2546.html