On Thu, Feb 01, 2018 at 18:24:42 -0500, John Ferlan wrote: > https://bugzilla.redhat.com/show_bug.cgi?id=916061 > > If the QEMU version running is new enough (based on the DUMP_COMPLETED > event), then we can add a 'detach' boolean to the dump-guest-memory > command in order to tell QEMU to run in a thread. This ensures that we > don't lock out other commands while the potentially long running dump > memory is completed. > > This allows the usage of a qemuDumpWaitForCompletion which will wait > for the event while the qemuDomainGetJobInfoDumpStats can be used via > qemuDomainGetJobInfo in order to query QEMU to determine how far along > the job is. > > Now that we have a true async job, we'll only set the dump_memory_only > flag only when @detach=false; otherwise, we note that the job is a > for stats dump this allows the opposite end for job info to determine > what to copy. > > Signed-off-by: John Ferlan <jfer...@redhat.com> > --- > src/qemu/qemu_driver.c | 65 > ++++++++++++++++++++++++++++++++++++++++++++++---- > 1 file changed, 60 insertions(+), 5 deletions(-)
Looks OK. Jirka -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
