Re: [libvirt PATCH v2 0/7] qemu: introduce a per-VM event loop thread

2020-03-06 Thread Daniel P . Berrangé
On Fri, Mar 06, 2020 at 02:42:45PM +0100, Michal Prívozník wrote: > On 5. 3. 2020 13:51, Daniel P. Berrangé wrote: > > This series changes the way we manage the QEMU monitor and > > QEMU agent, such that all I/O is processed by a dedicated > > event loop thread. > > > > Many times in the past

Re: [libvirt PATCH v2 0/7] qemu: introduce a per-VM event loop thread

2020-03-06 Thread Michal Prívozník
On 5. 3. 2020 13:51, Daniel P. Berrangé wrote: > This series changes the way we manage the QEMU monitor and > QEMU agent, such that all I/O is processed by a dedicated > event loop thread. > > Many times in the past years people are reported issues > where long running monitor event callbacks

[libvirt PATCH v2 0/7] qemu: introduce a per-VM event loop thread

2020-03-05 Thread Daniel P . Berrangé
This series changes the way we manage the QEMU monitor and QEMU agent, such that all I/O is processed by a dedicated event loop thread. Many times in the past years people are reported issues where long running monitor event callbacks block the main libvirtd event loop for an unacceptably long