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.
Created attachment 486181[details]
libvirtd logs when the failure occurred
libvirtd logs when the failure occurred.
Description of problem:
After doing the a sequence of operations on a guest, for example, domain start,
shutdown, start, destroy, suspend, resume, the guest always failed to save to a
file.
libvir: QEMU error : cannot send monitor command '{"execute":"stop"}':
Connection reset by peer
API error message: API Error:'cannot send monitor command
\'{"execute":"stop"}\': Connection reset by peer', error code is 38
Version-Release number of selected component (if applicable):
libvirt-0.8.7-13.el6.x86_64
libvirt-python-0.8.7-13.el6.x86_64
qemu-kvm-0.12.1.2-2.150.el6.x86_64
kernel-2.6.32-120.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. do a serials of operation to guest
2. virsh save <guest>
3.
Actual results:
report errors as above
Expected results:
save operation succeeds
Additional info:
I attached libvirtd log to the bz.
Comment 2RHEL Program Management
2011-04-04 02:10:27 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
libvir: QEMU error : cannot send monitor command '{"execute":"stop"}':
Connection reset by peer
API error message: API Error:'cannot send monitor command
\'{"execute":"stop"}\': Connection reset by peer', error code is 38
This is not the exact error libvirt throws, what libvirt throws is: "cannot send monitor command '{"execute":"stop"}': Connection reset by peer", other parts are by QE's testing suite.
And this problem could only be reproduced by QE's test suite on specified testing box.
Connection reset by peer is often an indication that qemu has crashed. Without further information, we will have to close this BZ as INSUFFICIENT_DATA. Is the problem still reproducible?
(In reply to comment #4)
> Connection reset by peer is often an indication that qemu has crashed. Without
> further information, we will have to close this BZ as INSUFFICIENT_DATA. Is
> the problem still reproducible?
Closing as INSUFFICIENT DATA; please reopen if the behavior reappears.
Created attachment 486181 [details] libvirtd logs when the failure occurred libvirtd logs when the failure occurred. Description of problem: After doing the a sequence of operations on a guest, for example, domain start, shutdown, start, destroy, suspend, resume, the guest always failed to save to a file. libvir: QEMU error : cannot send monitor command '{"execute":"stop"}': Connection reset by peer API error message: API Error:'cannot send monitor command \'{"execute":"stop"}\': Connection reset by peer', error code is 38 Version-Release number of selected component (if applicable): libvirt-0.8.7-13.el6.x86_64 libvirt-python-0.8.7-13.el6.x86_64 qemu-kvm-0.12.1.2-2.150.el6.x86_64 kernel-2.6.32-120.el6.x86_64 How reproducible: always Steps to Reproduce: 1. do a serials of operation to guest 2. virsh save <guest> 3. Actual results: report errors as above Expected results: save operation succeeds Additional info: I attached libvirtd log to the bz.