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.
Does the guest see the correct disk size, e.g. in the partitioner?
If so, this is not a qcow2 bug, but just what would happen on raw images or even real hardware, too.
(In reply to comment #2)
> Does the guest see the correct disk size, e.g. in the partitioner?
>
> If so, this is not a qcow2 bug, but just what would happen on raw images or
> even real hardware, too.
1.if image is raw format, it has the same issue.
2.use 5G size iscsi block to create 10G size qcow2 images and install guest, installation work well.
# lvscan
ACTIVE '/dev/test/data2' [5.00 GiB] inherit
# qemu-img info /dev/test/data2
image: /dev/test/data2
file format: qcow2
virtual size: 10G (10737418240 bytes)
disk size: 0
cluster_size: 65536
5G is still not enough disk space to perform an installation using automatic partitioning and including the desktop package group. Automatic partitioning sets up a /boot volume of 500M, the rest is then in a volume group. The logical volumes include swap, /, and /home.
/boot and swap are created along with the other filesystems. Installation cannot continue because your / filesystem lacks enough space. The reason your qcow2 image is 2.6G is because of swap space being allocated and the other filesystems being allocated.
I would argue that it's a bug in the automatic partitioner if the hard disk is big enough to actually contain an installation and only the partitioning makes it impossible to fit.
But the user specifically requested the desktop group. We don't look at a system and say, "ehhh, it's not really big enough for what you asked for, so we're just going to deselect some stuff so some other stuff will fit." The error reported in the screenshot in comment #1 tells you why we can't continue. The installation guide explains what partitions the automatic partitioning will allocate and how.