mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-11-08 14:29:56 +00:00
Allow setting migration max downtime any time
This removes the artificial and unnecessary restriction that virDomainSetMaxDowntime() only be called while a migration is in progress. https://bugzilla.redhat.com/show_bug.cgi?id=1146618 Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
This commit is contained in:
parent
bd2b0968c1
commit
fe808d95bf
@ -12023,12 +12023,6 @@ qemuDomainMigrateSetMaxDowntime(virDomainPtr dom,
|
|||||||
|
|
||||||
priv = vm->privateData;
|
priv = vm->privateData;
|
||||||
|
|
||||||
if (priv->job.asyncJob != QEMU_ASYNC_JOB_MIGRATION_OUT) {
|
|
||||||
virReportError(VIR_ERR_OPERATION_INVALID,
|
|
||||||
"%s", _("domain is not being migrated"));
|
|
||||||
goto endjob;
|
|
||||||
}
|
|
||||||
|
|
||||||
VIR_DEBUG("Setting migration downtime to %llums", downtime);
|
VIR_DEBUG("Setting migration downtime to %llums", downtime);
|
||||||
qemuDomainObjEnterMonitor(driver, vm);
|
qemuDomainObjEnterMonitor(driver, vm);
|
||||||
ret = qemuMonitorSetMigrationDowntime(priv->mon, downtime);
|
ret = qemuMonitorSetMigrationDowntime(priv->mon, downtime);
|
||||||
|
Loading…
Reference in New Issue
Block a user