This change serves as a proof of concept that adds live migration support to
the Cloud Hypervisor driver. It is meant to show feasibility and to receive
early feedback.

I tested the live migration by invoking:
virsh -c ch:///session migrate --domain vmName --desturi ch+ssh://dstHost/session --live

Opens:
* What is required for a minimal viable live migration to be merged?
	* Job state tracking? (virDomainObjBeginJob, ...)
	* What should 'virsh domjobinfo' show?
	* Testing?
	* Anything else?

Stefan Kober (1):
  Initial CH migrate API

 src/ch/ch_conf.h                  |   4 +
 src/ch/ch_domain.h                |   2 +
 src/ch/ch_driver.c                | 362 +++++++++++++++++++++++++++++-
 src/ch/ch_monitor.c               | 156 +++++++++++++
 src/ch/ch_monitor.h               |   8 +
 src/ch/ch_process.c               | 136 ++++++++++-
 src/ch/ch_process.h               |   6 +
 src/hypervisor/domain_interface.c |   1 +
 src/libvirt-domain.c              |  15 +-
 9 files changed, 680 insertions(+), 10 deletions(-)

-- 
2.49.0

Friendly bump :)

The POC currently detaches the network device prior to live migration because there is some missing cloud hypervisor support.

We might want to restrict live mive migration to VMs without network devices until the issue is resolved in cloud hypervisor.

See https://github.com/cloud-hypervisor/cloud-hypervisor/issues/7054 for further information.