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.
Previously, the number of characters in the file name strings for virtual machine (VM) images was limited. Because repeated creation of VM image snapshots gradually increases the file name string size, this eventually resulted in either of the following problems when the size limit was reached: creating an image snapshot failed to be executed, or the VM did not successfully boot. This update fixes the handling of file names so that long file names are now supported, and the mentioned problems no longer occur.
Created attachment 870610[details]
Script to reproduce relative pathname bug with just qemu-kvm and qemu-img
Attached is a script to reproduce this bug with just qemu-kvm, and qemu-img.
This can be seen via either live snapshots, or image creation with qemu-img.
This script will do the following:
1) create test directory
2) create a qcow2 base image
3) launch qemu-kvm with qmp over localhost tcp
4) attempt to create 80 live snapshots with a relative pathname, to parent directory and then back into the test directory
5) run qemu-img, create a different set of 80 snapshots off the same base image.
6) kill the process started in step #3
All you should need to edit in the script is the executable path for qemu and qemu-img.
The test directory is left after the script runs, with the created snapshots and an output log, for later examination.
Expected outcome:
Post fix: All snapshot created successfully (live and via qemu-img)
Prior to fix: First ~24 snapshots succeed, those after that fail
If you edit the script to create 150 snapshots instead of 80, you will see the fix fail as well.
Comment 5Miroslav Rezanina
2014-03-05 10:33:20 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.
Created attachment 870610 [details] Script to reproduce relative pathname bug with just qemu-kvm and qemu-img Attached is a script to reproduce this bug with just qemu-kvm, and qemu-img. This can be seen via either live snapshots, or image creation with qemu-img. This script will do the following: 1) create test directory 2) create a qcow2 base image 3) launch qemu-kvm with qmp over localhost tcp 4) attempt to create 80 live snapshots with a relative pathname, to parent directory and then back into the test directory 5) run qemu-img, create a different set of 80 snapshots off the same base image. 6) kill the process started in step #3 All you should need to edit in the script is the executable path for qemu and qemu-img. The test directory is left after the script runs, with the created snapshots and an output log, for later examination. Expected outcome: Post fix: All snapshot created successfully (live and via qemu-img) Prior to fix: First ~24 snapshots succeed, those after that fail If you edit the script to create 150 snapshots instead of 80, you will see the fix fail as well.