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:
there is not error message when create external checkpoint with
--memspec= (NULL)

Version-Release number of selected component (if applicable):
libvirt-0.10.2-9.el6.x86_64

How reproducible:
100

Steps to Reproduce:
1.virsh cmd fail but no error
# virsh snapshot-create-as v9 v1 --memspec=


2.console return 1
[root@intel-q9400-4-7 ~]# echo $?
1


Actual results:
no error pop up

Expected results:
some error like this :
# virsh snapshot-create-as v9 v1 --diskspec=
error: unsupported configuration: no disk named ''


Additional info:

Fix posted for upstream review:
http://www.redhat.com/archives/libvir-list/2012-November/msg00968.html

Fixed upstream:

commit fe910efd8a67c25c9d0538bbb466239af113dc71
Author: Peter Krempa <pkrempa>
Date:   Thu Nov 22 11:00:14 2012 +0100

    virsh: Report error when taking a snapshot with empty --memspec argument
    
    When the value of memspec was empty taking of a snapshot failed without
    reporting an error.

POSTed downstream:
http://post-office.corp.redhat.com/archives/rhvirt-patches/2012-November/msg00258.html

Verify this bug with:
libvirt-0.10.2-10.el6.x86_64

# virsh snapshot-create-as v9 v2323 --memspec=
error: memspec argument must not be empty

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-0276.html