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:

Forbid using same file as external snapshot file for disks and memory

Version-Release number of selected component (if applicable):

libvirt-1.2.8-4.el7.x86_64

How reproducible:

100%

Steps to Reproduce:

1. prepare a running domain

2. Create external system checkpoint snapshot with same file for disks and memory
# virsh snapshot-create-as rhel7-i ss --diskspec vda,file=/tmp/s1 --memspec file=/tmp/s1 
Domain snapshot ss created

3.

Actual results:


Expected results:

error: unsupported configuration: external snapshot file for disks should not be same with external snapshot file for memory


Additional info:

There's a lot of ways to specify the same file for both diskcpec and memspec and I don't think it's worth handling them. After all, the command just does what the user asked for...