Signed-off-by: George Dunlap <george.dun...@citrix.com>
---
Would someone be willing to take over this one?
CC: Ian Jackson <ian.jack...@citrix.com>
CC: Wei Liu <wei.l...@citrix.com>
CC: Andrew Cooper <andrew.coop...@citrix.com>
CC: Jan Beulich <jbeul...@suse.com>
CC: Stefano Stabellini <sstabell...@kernel.org>
CC: Konrad Wilk <konrad.w...@oracle.com>
CC: Tim Deegan <t...@xen.org>
CC: Roger Pau Monne <roger....@citrix.com>
CC: Anthony Perard <anthony.per...@citrix.com>
CC: Paul Durrant <paul.durr...@citrix.com>
CC: Julien Grall <julien.gr...@arm.com>
---
SUPPORT.md | 30 ++++++++++++++++++++++++++++++
1 file changed, 30 insertions(+)
diff --git a/SUPPORT.md b/SUPPORT.md
index c8fec4daa8..aa58fb0de3 100644
--- a/SUPPORT.md
+++ b/SUPPORT.md
@@ -324,6 +324,36 @@ This includes exposing event channels to HVM guests.
## High Availability and Fault Tolerance
+### Live Migration, Save & Restore
+
+ Status, x86: Supported, with caveats
+
+A number of features don't work with live migration / save / restore. These
include:
+ * PCI passthrough
+ * vNUMA
+ * Nested HVM
+
+XXX Need to check the following:
+
+ * Guest serial console
+ * Crash kernels
+ * Transcendent Memory
+ * Alternative p2m
+ * vMCE
+ * vPMU
+ * Intel Platform QoS
+ * Remus
+ * COLO
+ * PV protocols: Keyboard, PVUSB, PVSCSI, PVTPM, 9pfs, pvcalls?
+ * FlASK?
+ * CPU / memory hotplug?
+
+Additionally, if an HVM guest was booted with memory != maxmem,
+and the balloon driver hadn't hit the target before migration,
+the size of the guest on the far side might be unexpected.
+
+See docs/features/migration.pandoc for more details
+
### Remus Fault Tolerance
Status: Experimental
--
2.15.0
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
