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:
I can find the following line in 'help ping-daemon':
This is a test probe into the guestfs daemon running inside the hypervisor.

In fact the guestfs daemon exist in the libguestfs appliance, this may lead misunderstanding when understand this API, as a user, mostly we call host as the hypervisor, so the correct description should be:
This is a test probe into the guestfs daemon running inside libguestfs appliance.


Version-Release number of selected component (if applicable):
libguestfs-1.28.1-1.14.el7


How reproducible:
100%


Steps to Reproduce:
#guestfish help ping-daemon
NAME
        ping-daemon - ping the guest daemon

SYNOPSIS
         ping-daemon

DESCRIPTION
        This is a test probe into the guestfs daemon running inside the
        hypervisor. Calling this function checks that the daemon responds to the
        ping message, without affecting the daemon or attached block device(s)
        in any other way.


Actual results:
As above


Expected results:
correcy 'hypervisor' to 'appliance'


Additional info:

Upstream fix:
https://github.com/libguestfs/libguestfs/commit/f6e74ecd73d9aeeb4c9ef0044d7112645b09172f

Verified with libguestfs-1.28.1-1.29.el7.

Step to verify:
1. # guestfish help ping-daemon
NAME
    ping-daemon - ping the guest daemon

SYNOPSIS
     ping-daemon

DESCRIPTION
    This is a test probe into the guestfs daemon running inside the
    libguestfs appliance. Calling this function checks that the daemon
    responds to the ping message, without affecting the daemon or attached
    block device(s) in any other way.


"hypervisor" is replaced with "libguestfs appliance". So fixed.

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.

https://rhn.redhat.com/errata/RHBA-2015-2183.html