On 02/03/2012 01:12 AM, Daniel Veillard wrote:
> On Thu, Feb 02, 2012 at 12:54:28PM -0500, Laine Stump wrote:
>> When libvirt's virDomainDestroy API is shutting down the qemu process,
>> it first sends SIGTERM, then waits for 1.6 seconds and, if it sees the
>> process still there, sends a SIGKILL.
On Thu, Feb 02, 2012 at 12:54:28PM -0500, Laine Stump wrote:
> When libvirt's virDomainDestroy API is shutting down the qemu process,
> it first sends SIGTERM, then waits for 1.6 seconds and, if it sees the
> process still there, sends a SIGKILL.
>
> There have been reports that this behavior can
When libvirt's virDomainDestroy API is shutting down the qemu process,
it first sends SIGTERM, then waits for 1.6 seconds and, if it sees the
process still there, sends a SIGKILL.
There have been reports that this behavior can lead to data loss
because the guest running in qemu doesn't have time t
