26 #include "migration/failover.h"
41 /* User need to know colo mode after COLO failover */
95     /* Can not do failover during the process of VM's loading VMstate, Or  in secondary_vm_do_failover()
102             error_report("Unknown error while do failover for secondary VM,"  in secondary_vm_do_failover()
144         error_report("Incorrect state (%s) while doing failover for "  in secondary_vm_do_failover()
148     /* Notify COLO incoming thread that failover work is finished */  in secondary_vm_do_failover()
186         error_report("Incorrect state (%s) while doing failover for Primary VM",  in primary_vm_do_failover()
197     /* Notify COLO thread that failover work is finished */  in primary_vm_do_failover()
214     /* Make sure VM stopped while failover happened. */  in colo_do_failover()
233                              bool has_failover, bool failover,  in qmp_xen_set_replication()  argument
241         error_setg(errp, "Parameter 'failover' is only for"  in qmp_xen_set_replication()
250             failover = NULL;  in qmp_xen_set_replication()
252         replication_stop_all(failover, failover ? NULL : errp);  in qmp_xen_set_replication()
436      * Failover request bh could be called after vm_stop_force_state(),  in colo_do_checkpoint_transaction()
583             error_report("failover request");  in colo_process_checkpoint()
610      * or the user triggered failover.  in colo_process_checkpoint()
627      * It is safe to unregister notifier after failover finished.  in colo_process_checkpoint()
637      * Must be called after failover BH is completed,  in colo_process_checkpoint()
638      * Or the failover BH may shutdown the wrong fd that  in colo_process_checkpoint()
901             error_report("failover request");  in colo_process_incoming_thread()
909      * or the user triggered failover.  in colo_process_incoming_thread()