Re: [libvirt] [PATCH] qemu: Transition domain to PAUSED after 'stop' command

2012-09-20 Thread Michal Privoznik
On 19.09.2012 14:59, Martin Kletzander wrote: > On 09/19/2012 12:16 PM, Michal Privoznik wrote: >> On 19.09.2012 11:43, Michal Privoznik wrote: >>> Currently, we mark domain PAUSED (but not emit an event) >>> just before we issue 'stop' on monitor; This command can >>> take ages to finish, esp. whe

Re: [libvirt] [PATCH] qemu: Transition domain to PAUSED after 'stop' command

2012-09-19 Thread Martin Kletzander
On 09/19/2012 12:16 PM, Michal Privoznik wrote: > On 19.09.2012 11:43, Michal Privoznik wrote: >> Currently, we mark domain PAUSED (but not emit an event) >> just before we issue 'stop' on monitor; This command can >> take ages to finish, esp. when domain's doing a lot of >> IO - users can enforce

Re: [libvirt] [PATCH] qemu: Transition domain to PAUSED after 'stop' command

2012-09-19 Thread Michal Privoznik
On 19.09.2012 11:43, Michal Privoznik wrote: > Currently, we mark domain PAUSED (but not emit an event) > just before we issue 'stop' on monitor; This command can > take ages to finish, esp. when domain's doing a lot of > IO - users can enforce qemu to open files with O_DIRECT > which doesn't retur

[libvirt] [PATCH] qemu: Transition domain to PAUSED after 'stop' command

2012-09-19 Thread Michal Privoznik
Currently, we mark domain PAUSED (but not emit an event) just before we issue 'stop' on monitor; This command can take ages to finish, esp. when domain's doing a lot of IO - users can enforce qemu to open files with O_DIRECT which doesn't return from write() until data reaches the block device. Hav