Bug 735716 - QEMU should report the PID of the process that sent it signals for troubleshooting purposes
QEMU should report the PID of the process that sent it signals for troublesho...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm (Show other bugs)
6.2
x86_64 Linux
unspecified Severity medium
: rc
: ---
Assigned To: Gleb Natapov
Virtualization Bugs
:
Depends On: 677614
Blocks: Rhel5KvmTier2 677620
  Show dependency treegraph
 
Reported: 2011-09-05 03:12 EDT by Gleb Natapov
Modified: 2013-12-08 19:55 EST (History)
10 users (show)

See Also:
Fixed In Version: qemu-kvm-0.12.1.2-2.206.el6
Doc Type: Bug Fix
Doc Text:
If qemu process is killed by another process we want to log this information for troubleshooting purposes.
Story Points: ---
Clone Of: 677614
Environment:
Last Closed: 2011-12-06 11:03:00 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Comment 2 juzhang 2011-09-05 03:34:45 EDT
Reproduce this issue with qemu-kvm-0.12.1.2-2.184.el6.x86_64,mark ack+
Comment 12 Eduardo Habkost 2011-10-28 13:58:53 EDT
Moving to ON_QA because Errata Tool did not do it
Comment 14 Gleb Natapov 2011-11-20 04:28:42 EST
    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:
If qemu process is killed by another process we want to log this information for troubleshooting purposes.
Comment 15 errata-xmlrpc 2011-12-06 11:03:00 EST
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-2011-1531.html

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