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.
Bug 998485 - guestfish remote prints "libguestfs: error: waitpid (qemu): No child processes"
Summary: guestfish remote prints "libguestfs: error: waitpid (qemu): No child processes"
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libguestfs
Version: 7.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Richard W.M. Jones
QA Contact: Virtualization Bugs
URL:
Whiteboard: QJ130807-012
Depends On: 998482
Blocks: 839484
TreeView+ depends on / blocked
 
Reported: 2013-08-19 12:32 UTC by Richard W.M. Jones
Modified: 2014-06-18 02:00 UTC (History)
10 users (show)

Fixed In Version: libguestfs-1.22.6-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of: 998482
Environment:
Last Closed: 2014-06-13 11:44:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Richard W.M. Jones 2013-08-19 12:32:49 UTC
+++ This bug was initially created as a clone of Bug #998482 +++

Reported by: Kazuya Saito

Note for some reason that I cannot work out, this is only reproducible
in the libguestfs source directory.

(a) Checkout libguestfs from git and compile it in the usual way.

(b) make -C tests/guests check

(c) In one window, run:

  ./run ./fish/guestfish --listen --ro -a ./tests/guests/debian.img -i

This will print out (the number will be different):

  GUESTFISH_PID=13170; export GUESTFISH_PID

(d) In another window, run:

  GUESTFISH_PID=13170 ./run ./fish/guestfish --remote exit

In the first window you'll see an error:

  libguestfs: error: waitpid (qemu): No child processes

That is a bug.

Comment 3 Can Zhang 2013-11-08 06:46:25 UTC
I installed libguestfs-1.22.2-1.el7, and ran `LIBGUESTFS_BACKEND=direct guestfish --listen --ro -a RHEL-Server-7.0-64-hvm.raw -i -v` in one terminal. Then opened a new terminal window and run `GUESTFISH_PID=8403 guestfish --remote exit`. And I saw error outputs from the first terminal:

# guestfish(8403): exit
libguestfs: closing guestfs handle 0x7fe56a024180 (state 2)
guestfsd: main_loop: proc 73 (mount_ro) took 0.10 seconds
guestfsd: main_loop: new request, len 0x28
umount /sysroot/boot
umount /sysroot
fsync /dev/sda
libguestfs: sending SIGTERM to process 8385
libguestfs: error: waitpid (qemu): No child processes
libguestfs: command: run: rm
libguestfs: command: run: \ -rf /tmp/libguestfsOIXqJe

And in a newer version, libguestfs-1.22.6-15.el7, no error message outputs.

Comment 4 Ludek Smid 2014-06-13 11:44:36 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


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