This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira ( 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 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 "", 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 1519002 - RFE: libvirt - improve support for external snapshots (merge, delete, virsh, etc)
Summary: RFE: libvirt - improve support for external snapshots (merge, delete, virsh, ...
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libvirt
Version: 9.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: beta
: ---
Assignee: Pavel Hrdina
QA Contact: Han Han
Depends On: 1402581 1519001 2170826 2173142 2174397 2174700
Blocks: 1214187 1342543 1403951 1431852 1621944 1997885 2132850
TreeView+ depends on / blocked
Reported: 2017-11-29 22:43 UTC by Ademar Reis
Modified: 2023-09-22 17:51 UTC (History)
34 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 1402581
Last Closed: 2023-09-22 17:51:33 UTC
Type: Story
Target Upstream Version: 9.7.0

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-7528 0 None Migrated None 2023-09-22 17:51:55 UTC
Red Hat Issue Tracker RHELBU-1675 0 None None None 2022-10-10 04:03:10 UTC
Red Hat Knowledge Base (Solution) 30379 0 None None None 2022-09-22 04:43:51 UTC

Internal Links: 1845924

Description Ademar Reis 2017-11-29 22:43:31 UTC
+++ This bug was initially created as a clone of Bug #1402581 +++

Description of problem:
For historical reasons, 'virsh snapshot-create' defaults to internal snapshots, because external snapshots were not implemented for several years.  However, these days the qemu team recommends the use of external snapshots, and upper levels like RHEV prefer external snapshots.  It would be nice if there were a way to set up configuration defaults for virsh, so that typing 'virsh snapshot-create' could consult the configuration file on whether to default to internal or external, instead of forcing the user to remember to pass extra flags to get an external snapshot.

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

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

--- Additional comment from Laszlo Ersek on 2017-02-24 20:50:15 BRT ---

When designing this feature for virsh (and virt-manager), please don't forget about the UEFI varstore files (under /var/lib/libvirt/qemu/nvram), which are technically raw drives, but have very different storage properties from normal drives. They don't live in storage pools, they are not on shared storage, and also not subject to storage migration. QEMU automatically writes them out fully on the target host after migration finishes.

I'm unsure how this interacts with external snapshots, but I figure I'd better raise it. Thanks.

Comment 5 Peter Krempa 2020-06-30 20:05:46 UTC
There are multiple options how to create an external snapshot:

1) using virsh snapshot-create-as (see man page for further explanation):

1.1) if the VM is active, but the user doesn't want to take a snapshot of the memory

  virsh snapshot-create-as $VMNAME --disk-only

1.2) if the vm is active and memory snapshot is required
  virsh snapshot-create-as $VMNAME --memspec file=/path/to/memory-image,snapshot=external

1.3) if disks which take part of the snapshot need to be controlled:

  virsh snapshot-create-as $VMNAME --memspec file=/path/to/memory-image,snapshot=external --diskspec vda,snapshot=no --diskspec vdb,file=/path/to/overlay-img

1.4) any additional options such as snapshot name, description etc can be controlled using additional parameters. Please refer to the man page:

2) using virsh snapshot create

This option requires an XML document describing the snapshot as argument. Please refer to the documentation.

For inspiration, a sample XML can be obtained using the '--print-xml' argument for 'virsh snapshot-create-as' which prints the XML the command generates.

snapshot XML documentation:

Please note, that while creating external snapshots works, we don't yet have implementation for reverting or deleting external snapshots, thus internal snapshots must be supported until then.

Regarding customer's question, rhel-7.6 already supports external snapshots to the extent above.

If required there are manual steps which allow reversion or deletion of external snapshots.

Comment 29 RHEL Program Management 2023-09-22 17:50:43 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 30 RHEL Program Management 2023-09-22 17:51:33 UTC
This BZ has been automatically migrated to the Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit for general account information.

Note You need to log in before you can comment on or make changes to this bug.