[pve-devel] [PATCH v2 pve-docs 3/3] Add pre/post-migrate section to VM hookscript documentation
Stefan Hanreich
s.hanreich at proxmox.com
Thu Oct 6 14:44:45 CEST 2022
Add a short information about how the hookscripts should be stored as
well as a short part about the preferred way of storing the migration
hookscripts.
Signed-off-by: Stefan Hanreich <s.hanreich at proxmox.com>
---
qm.adoc | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/qm.adoc b/qm.adoc
index 4d0c7c4..3f5c2cc 100644
--- a/qm.adoc
+++ b/qm.adoc
@@ -1410,6 +1410,16 @@ It will be called during various phases of the guests lifetime.
For an example and documentation see the example script under
`/usr/share/pve-docs/examples/guest-example-hookscript.pl`.
+pre/post-migrate
+~~~~~~~~~~~~~~~~
+Those hooks run before/after a VM migrates from one host to another. This
+hook is a bit special, since it gets executed on the source node as well as the
+target node. In order for this hookscript to function properly, the configured
+script file needs to be available on both nodes. If it is a local script, this
+means storing it on both server under the same path. The preferred option
+would be storing the hookscript on a shared storage, so it is accessible from
+both nodes.
+
[[qm_hibernate]]
Hibernation
-----------
--
2.30.2
More information about the pve-devel
mailing list