Re: [libvirt] [PATCH] do not send monitor command after monitor met error

2011-03-30 Thread Wen Congyang
At 03/29/2011 05:59 PM, Daniel P. Berrange Write: On Tue, Mar 29, 2011 at 03:22:40PM +0800, Wen Congyang wrote: If the monitor met a error, and we will call qemuProcessHandleMonitorEOF(). But we may try to send monitor command after qemuProcessHandleMonitorEOF() returned. Then libvirtd will be

[libvirt] [PATCH] do not send monitor command after monitor met error

2011-03-29 Thread Wen Congyang
If the monitor met a error, and we will call qemuProcessHandleMonitorEOF(). But we may try to send monitor command after qemuProcessHandleMonitorEOF() returned. Then libvirtd will be blocked in qemuMonitorSend(). Steps to reproduce this bug: 1. use gdb to attach libvirtd, and set a breakpoint in

Re: [libvirt] [PATCH] do not send monitor command after monitor met error

2011-03-29 Thread Daniel P. Berrange
On Tue, Mar 29, 2011 at 03:22:40PM +0800, Wen Congyang wrote: If the monitor met a error, and we will call qemuProcessHandleMonitorEOF(). But we may try to send monitor command after qemuProcessHandleMonitorEOF() returned. Then libvirtd will be blocked in qemuMonitorSend(). Steps to