6 Mar
2019
6 Mar
'19
1:03 p.m.
On Wed, Mar 06, 2019 at 12:29:05 +0100, Ján Tomko wrote:
On Wed, Mar 06, 2019 at 12:15:08PM +0100, Jiri Denemark wrote:
The qemuMigrationParamsApply internal API was designed to apply all migration parameters and capabilities before we start to migrate a domain. The API can also be called outside migration job, e.g., via a call to qemuDomainMigrateSetMaxSpeed with VIR_DOMAIN_MIGRATE_MAX_SPEED_POSTCOPY flag, but in that case it should only apply migration parameters and ignore capabilities.
Is there a public bug you can link here?
No. Jirka