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:
The warning message pop up 8 times repeatly when there is no enough free space to allocate for virt-install.
For example:
#virt-install -n vm1 -r 1024 --disk path=vm1.img,size=100000000 -c /dev/cdrom
WARNING The filesystem will not have enough free space to fully allocate the sparse file when the guest is running. 102400000000 M requested > 183327 M available
WARNING The filesystem will not have enough free space to fully allocate the sparse file when the guest is running. 102400000000 M requested > 183327 M available
WARNING The filesystem will not have enough free space to fully allocate the sparse file when the guest is running. 102400000000 M requested > 183327 M available
WARNING The filesystem will not have enough free space to fully allocate the sparse file when the guest is running. 102400000000 M requested > 183327 M available
WARNING The filesystem will not have enough free space to fully allocate the sparse file when the guest is running. 102400000000 M requested > 183327 M available
WARNING The filesystem will not have enough free space to fully allocate the sparse file when the guest is running. 102400000000 M requested > 183327 M available
WARNING The filesystem will not have enough free space to fully allocate the sparse file when the guest is running. 102400000000 M requested > 183327 M available
WARNING The filesystem will not have enough free space to fully allocate the sparse file when the guest is running. 102400000000 M requested > 183327 M available
ERROR The filesystem will not have enough free space to fully allocate the sparse file when the guest is running. 102400000000 M requested > 183327 M available (Use --prompt or --force to override)
Version-Release number of selected component (if applicable):
python-virtinst-0.600.0-8.el6.noarch
How reproducible:
100%
Steps to Reproduce:
Run a virt-convert command with unknown output format
#virt-install -n vm1 -r 1024 --disk path=vm1.img,size=100000000 -c /dev/cdrom
check the warning and error messages
Actual results:
The warning message pop up 8 times repeatly
Expect result:
The warning message should display one time