Add VIR_DOMAIN_ABORT_JOB_POSTCOPY flag for virDomainAbortJobFlags

Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
Reviewed-by: Peter Krempa <pkrempa@redhat.com>
Reviewed-by: Pavel Hrdina <phrdina@redhat.com>
This commit is contained in:
Jiri Denemark 2022-05-10 15:20:25 +02:00
parent fb50e56569
commit 479d8e9f09
2 changed files with 22 additions and 4 deletions

View File

@ -4099,6 +4099,22 @@ int virDomainGetJobStats(virDomainPtr domain,
unsigned int flags); unsigned int flags);
int virDomainAbortJob(virDomainPtr dom); int virDomainAbortJob(virDomainPtr dom);
/**
* virDomainAbortJobFlagsValues:
*
* Flags OR'ed together to provide specific behavior when aborting a domain job.
*
* Since: 8.5.0
*/
typedef enum {
/* Interrupt post-copy migration. Since migration in a post-copy phase
* cannot be aborted without losing the domain (none of the hosts involved
* in migration has a complete state of the domain), the migration will be
* suspended and it can later be resumed using virDomainMigrate* APIs with
* VIR_MIGRATE_POSTCOPY_RESUME flag. (Since: 8.5.0) */
VIR_DOMAIN_ABORT_JOB_POSTCOPY = 1 << 0,
} virDomainAbortJobFlagsValues;
int virDomainAbortJobFlags(virDomainPtr dom, int virDomainAbortJobFlags(virDomainPtr dom,
unsigned int flags); unsigned int flags);

View File

@ -9473,12 +9473,12 @@ virDomainAbortJob(virDomainPtr domain)
/** /**
* virDomainAbortJobFlags: * virDomainAbortJobFlags:
* @domain: a domain object * @domain: a domain object
* @flags: extra flags; not used yet, callers should always pass 0 * @flags: bitwise-OR of virDomainAbortJobFlagsValues
* *
* Requests that the current background job be aborted at the * Requests that the current background job be aborted at the
* soonest opportunity. In case the job is a migration in a post-copy mode, * soonest opportunity. In case the job is a migration in a post-copy mode,
* this function will report an error (see virDomainMigrateStartPostCopy for * this function will report an error unless VIR_DOMAIN_ABORT_JOB_POSTCOPY
* more details). * flag is used (see virDomainMigrateStartPostCopy for more details).
* *
* Returns 0 in case of success and -1 in case of failure. * Returns 0 in case of success and -1 in case of failure.
* *
@ -9816,7 +9816,9 @@ virDomainMigrateGetMaxSpeed(virDomainPtr domain,
* will remain running with VIR_DOMAIN_RUNNING_POSTCOPY_FAILED reason. * will remain running with VIR_DOMAIN_RUNNING_POSTCOPY_FAILED reason.
* It's up to the upper layer to decide what to do in such case. Because of * It's up to the upper layer to decide what to do in such case. Because of
* this, libvirt will refuse to cancel post-copy migration via * this, libvirt will refuse to cancel post-copy migration via
* virDomainAbortJob. * virDomainAbortJobFlags unless it is called with
* VIR_DOMAIN_ABORT_JOB_POSTCOPY, in which case the post-copy migration will be
* paused.
* *
* Failed post-copy migration can be recovered once the cause for the failure * Failed post-copy migration can be recovered once the cause for the failure
* (e.g., a network issue) is resolved by repeating the migration with an * (e.g., a network issue) is resolved by repeating the migration with an