During migration, the libxl driver starts a modify job in the
begin phase, ending the job in the confirm phase. This is
essentially VIR_MIGRATE_CHANGE_PROTECTION semantics, but the
driver does not support that flag. Without CHANGE_PROTECTION
support, the job would never be terminated in error conditions
where migrate confirm phase is not executed. Further attempts
to modify the domain would result in failure to acquire a job
after LIBXL_JOB_WAIT_TIME.
Similar to the qemu driver, end the job in the begin phase.
Protecting the domain object across all phases of migration can
be done in a future patch adding CHANGE_PROTECTION support.
goto cleanup;
if (libxlDomainMigrationPerform(driver, vm, dom_xml, dconnuri,
- uri, dname, flags) < 0) {
- /* Job terminated and vm unlocked if MigrationPerform failed */
- vm = NULL;
+ uri, dname, flags) < 0)
goto cleanup;
- }
ret = 0;
xml = virDomainDefFormat(def, VIR_DOMAIN_XML_SECURE);
+ endjob:
+ if (!libxlDomainObjEndJob(driver, vm))
+ vm = NULL;
+
cleanup:
if (vm)
virObjectUnlock(vm);
virDomainDefFree(tmpdef);
virObjectUnref(cfg);
return xml;
-
- endjob:
- if (!libxlDomainObjEndJob(driver, vm))
- vm = NULL;
- goto cleanup;
}
virDomainDefPtr
virObjectLock(vm);
cleanup:
- /* If failure, terminate the job started in MigrationBegin */
- if (ret == -1) {
- if (libxlDomainObjEndJob(driver, vm))
- virObjectUnlock(vm);
- }
VIR_FORCE_CLOSE(sockfd);
virURIFree(uri);
return ret;
ret = 0;
cleanup:
- if (!libxlDomainObjEndJob(driver, vm))
- vm = NULL;
if (event)
libxlDomainEventQueue(driver, event);
if (vm)