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 1459725 - Prevent qemu-img resize from causing "Active L1 table too large"
Summary: Prevent qemu-img resize from causing "Active L1 table too large"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm
Version: 7.4
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Hanna Czenczek
QA Contact: Ping Li
URL:
Whiteboard:
Depends On: 1378694
Blocks: 1473046
TreeView+ depends on / blocked
 
Reported: 2017-06-08 00:35 UTC by Ping Li
Modified: 2018-04-10 14:32 UTC (History)
17 users (show)

Fixed In Version: qemu-kvm-1.5.3-149.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1378694
Environment:
Last Closed: 2018-04-10 14:32:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:0816 0 normal SHIPPED_LIVE Low: qemu-kvm security, bug fix, and enhancement update 2018-04-10 12:47:03 UTC

Comment 3 Miroslav Rezanina 2017-11-29 06:06:38 UTC 
Fix included in qemu-kvm-1.5.3-149.el7
Comment 5 Ping Li 2017-11-30 03:26:16 UTC 
Passed the test as below, set the bug as verified.

Packages tested:
kernel-3.10.0-799.el7.x86_64
qemu-kvm-1.5.3-149.el7

Test steps:
1. Create image with large size
# qemu-img create -f qcow2 test_large.qcow2 30720T
Formatting 'test_large.qcow2', fmt=qcow2 size=33776997205278720 encryption=off cluster_size=65536 lazy_refcounts=off 
qemu-img: test_large.qcow2: The image size is too large for file format 'qcow2' (try using a larger cluster size)
# qemu-img info test_large.qcow2 
image: test_large.qcow2
file format: qcow2
virtual size: 0 (0 bytes)
disk size: 192K
cluster_size: 65536
Format specific information:
    compat: 1.1
    lazy refcounts: false 

2. Resize the image with large size
# qemu-img create -f qcow2 test.qcow2 1G
Formatting 'test.qcow2', fmt=qcow2 size=1073741824 encryption=off cluster_size=65536 lazy_refcounts=off
# qemu-img info test.qcow2 
image: test.qcow2
file format: qcow2
virtual size: 1.0G (1073741824 bytes)
disk size: 196K
cluster_size: 65536
Format specific information:
    compat: 1.1
    lazy refcounts: false
# qemu-img resize test.qcow2 +30720T
qemu-img: Error resizing image: File too large
# qemu-img info test.qcow2 
image: test.qcow2
file format: qcow2
virtual size: 1.0G (1073741824 bytes)
disk size: 196K
cluster_size: 65536
Format specific information:
    compat: 1.1
    lazy refcounts: false
Comment 9 errata-xmlrpc 2018-04-10 14:32:19 UTC 
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://access.redhat.com/errata/RHSA-2018:0816
Note You need to log in before you can comment on or make changes to this bug.