This is an automated email from the ASF dual-hosted git repository.
sureshanaparti pushed a commit to branch 4.22
in repository https://gitbox.apache.org/repos/asf/cloudstack-documentation.git
The following commit(s) were added to refs/heads/4.22 by this push:
new b258a083 Document KVM VM metadata handling in unmanage process (#595)
b258a083 is described below
commit b258a08356026991f41d79c47593a81b93fc4493
Author: Dattu <[email protected]>
AuthorDate: Tue May 19 12:18:44 2026 +0530
Document KVM VM metadata handling in unmanage process (#595)
* Added a warning about KVM VM metadata preservation when unmanaged.
* Update warning for KVM instance unmanaged metadata
---
source/adminguide/virtual_machines/importing_unmanaging_vms.rst | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/source/adminguide/virtual_machines/importing_unmanaging_vms.rst
b/source/adminguide/virtual_machines/importing_unmanaging_vms.rst
index bc197da8..7c3444b9 100644
--- a/source/adminguide/virtual_machines/importing_unmanaging_vms.rst
+++ b/source/adminguide/virtual_machines/importing_unmanaging_vms.rst
@@ -360,6 +360,10 @@ The API has the following preconditions:
- The Instance state must be 'Running’ or ‘Stopped’
- The Instance must be a VMware Instance (as of CloudStack 4.19, it's also
possible to unmanage a KVM-based Instances)
+.. warning::
+ Starting with the 4.22.1 release, when a KVM instance is unmanaged, the
infrastructure metadata (zone, pod, cluster, and host details) is preserved in
the libvirt VM XML.
+ This information is left for the user’s discretion—allowing them to either
retain it or remove it manually or through scripts.
+
The API execution will perform the following pre-checks, failing if they are
not met:
- There are no Volume Snapshots associated with any of the Instance volumes
