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.
+++ This bug was initially created as a clone of Bug #1083345 +++
Description of problem:
The --memspec parameters "snapshot=no" doesn't work when creating internal disk snapshot
Version-Release number of selected component (if applicable):
libvirt-1.1.1-29.el7.x86_64
qemu-kvm-rhev-1.5.3-59.el7ev.x86_64
How reproducible:
100%
Steps to Reproduce:
1.define an guest and keep it running status
# virsh list --name --state-running
rhel6.5
2.try to create internal disk-only snapshot
# virsh snapshot-create-as rhel6.5 diskonly-internal1 --memspec snapshot=no --diskspec vda,snapshot=internal --diskspec vdb,snapshot=internal
Domain snapshot diskonly-internal1 created
3. check snapshot info
# virsh snapshot-dumpxml rhel6.5 diskonly-internal1
<domainsnapshot>
<name>diskonly-internal1</name>
<state>running</state>
<parent>
<name>diskonly-internal</name>
</parent>
<creationTime>1396342930</creationTime>
<memory snapshot='internal'/>
<disks>
<disk name='vda' snapshot='internal'/>
<disk name='vdb' snapshot='internal'/>
</disks>
Actual results:
As above.
Expected results:
1) Suppose we support internal disk-only snapshot, we should succeed creating such snapshot in step3
2) If we don't support internal disk-only snapshot, it should come up with some error info when creating it as in step 2
Additional info:
Comment 3RHEL Program Management
2014-04-04 20:56:31 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.