On Tue, May 17, 2022 at 02:35:04PM +0800, huang...@chinatelecom.cn wrote: > From: Hyman Huang(黄勇) <huang...@chinatelecom.cn> > > Introduce migration dirtylimit capability, which can > be turned on before live migration and limit dirty > page rate durty live migration.
s/durty/during/ ? > > Dirtylimit dirtylimit capability is kind of like Doubled word > auto-converge but using dirtylimit instead of traditional > cpu-throttle to throttle guest down. > > To enable this feature, turn on the dirtylimit capability > before live migration using migratioin-set-capabilities, > and set dirtylimit-related parameters "vcpu-dirtylimit", > "vcpu-dirtylimit-period" suitably to speed up convergence. > > Signed-off-by: Hyman Huang(黄勇) <huang...@chinatelecom.cn> > --- > +++ b/qapi/migration.json > @@ -463,6 +463,9 @@ > # procedure starts. The VM RAM is saved with running > VM. > # (since 6.0) > # > +# @dirtylimit: Use dirtylimit to throttle down guest if enabled. > +# (since 7.0) 7.1 same question about naming it 'dirty-limit' -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org
