Bug 662042

Summary: [libvirt] kill qemu process using 'kill' behaves as user shutdown command and not as 'lost connection with qemu process'
Product: Red Hat Enterprise Linux 6 Reporter: RHEL Program Management <pm-rhel>
Component: libvirtAssignee: Daniel Veillard <veillard>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: urgent    
Version: 6.1CC: abaron, berrange, cpelland, dallan, danken, dyuan, eblake, hateya, iheim, jdenemar, kxiong, mgoldboi, mjenner, plyons, pm-eus, xen-maint, yimwang, ykaul
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: libvirt-0.8.1-27.el6_0.2 Doc Type: Bug Fix
Doc Text:
Prior to this update, libvirt was not able to recognize whether a domain crashed or was properly shut down. With this update, a SHUTDOWN event sent by qemu is recognized by libvirt when a domain is properly shut down. If the SHUTDOWN event is not received, the domain is declared to have crashed.
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-14 16:18:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 656845    
Bug Blocks:    

Description RHEL Program Management 2010-12-10 12:23:01 UTC
This bug has been copied from bug #656845 and has been proposed
to be backported to 6.0 z-stream (EUS).

Comment 3 Jiri Denemark 2010-12-10 13:53:09 UTC
Fixed in libvirt-0.8.1-27.el6_0.2

Comment 7 koka xiong 2011-01-30 03:05:10 UTC
Verified on libvirt without vdsm as we don't have vdsm env. 
From that result shows it fixed on plain libvirt env.
libvirt: libvirt-0.8.1-27.el6_0.3
kernel: kernel-2.6.32-71.16.1.el6
qemu-kvm: qemu-kvm-0.12.1.2-2.113.el6_0.6
1.After kill qemu process,go to libvirtd.log
2.It will output:
03:21:28.124: debug : qemuMonitorIO:575 : Triggering EOF callback error? 0
03:21:28.124: debug : qemuHandleMonitorEOF:1121 : Received EOF on 0x79b950 'RHEL5-qcow2'
03:21:28.124: debug : qemuHandleMonitorEOF:1127 : Monitor connection to 'RHEL5-qcow2' closed without SHUTDOWN event; assuming the domain crashed
03:21:28.124: debug : qemudShutdownVMDaemon:4287 : Shutting down VM 'RHEL5-qcow2' migrated=0

Comment 8 errata-xmlrpc 2011-04-14 16:18:40 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0446.html

Comment 9 Martin Prpič 2011-04-15 14:21:24 UTC
    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:
Prior to this update, libvirt was not able to recognize whether a domain crashed or was properly shut down. With this update, a SHUTDOWN event sent by qemu is recognized by libvirt when a domain is properly shut down. If the SHUTDOWN event is not received, the domain is declared to have crashed.