From 4c1844c9daa4fe6467ec8e8b4cf9cd0d31462123 Mon Sep 17 00:00:00 2001 From: Dattu Date: Mon, 10 Nov 2025 20:16:18 +0530 Subject: [PATCH 1/2] Document KVM VM metadata handling in unmanage process Added a warning about KVM VM metadata preservation when unmanaged. --- .../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 bc197da889..bccc9b4ad0 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.0 release, when a KVM VM is unmanaged, its infrastructure metadata (zone, pod, cluster, and host) in the libvirt VM XML is preserved. + 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 From 4a596e469fe2395f62dd22fc0543173d0463b2fc Mon Sep 17 00:00:00 2001 From: Dattu Date: Wed, 12 Nov 2025 13:15:38 +0530 Subject: [PATCH 2/2] Update warning for KVM instance unmanaged metadata --- source/adminguide/virtual_machines/importing_unmanaging_vms.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/adminguide/virtual_machines/importing_unmanaging_vms.rst b/source/adminguide/virtual_machines/importing_unmanaging_vms.rst index bccc9b4ad0..7c3444b95f 100644 --- a/source/adminguide/virtual_machines/importing_unmanaging_vms.rst +++ b/source/adminguide/virtual_machines/importing_unmanaging_vms.rst @@ -361,7 +361,7 @@ The API has the following preconditions: - 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.0 release, when a KVM VM is unmanaged, its infrastructure metadata (zone, pod, cluster, and host) in the libvirt VM XML is preserved. + 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: