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:
Run 'virsh nodesuspend mem disk' then check return value, which is '1', but can't see any error output and also can't find error in libvirtd.log or /var/log/messages.

Version-Release number of selected component (if applicable):
libvirt-0.9.8-0rc2.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. virsh nodesuspend mem disk (mix 'mem' and 'disk' options)
2. check output, logs and return value 
  
Actual results:
# virsh nodesuspend mem disk

Note: nothing error output in here.
# echo $?
1

Note: but return value is 1, and also can't see error in related logs file.

Expected results:
Raising error information and writing them into libvirtd.log file.

Additional info:

The same issue with libvirt-0.9.8-1.el6.x86_64

Fixed with upstream commit:

commit b72c774b88b911a78d3040c02dc03c2411edd2d7
Author: Peter Krempa <pkrempa>
Date:   Tue Dec 13 14:50:30 2011 +0100

    virsh: Print error message if argument parsing fails for cmdNodesuspend
    
    If parsing of arguments failed, virsh did silently exit returning and
    error state, but not specifying the possible problem.


Errors are printed if parsing of arguments fails.

Verified this issue with libvirt-0.9.9-1.el6.x86_64.
# virsh nodesuspend mem disk
error: Invalid duration argument

# echo $?
1

So change the bug status to VERIFIED.

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
No Documentation needed

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-2012-0748.html