Skip to content

Document KVM VM metadata handling in unmanage process #595

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: 4.22
Choose a base branch
from
Open

Document KVM VM metadata handling in unmanage process #595

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4c1844c
Document KVM VM metadata handling in unmanage process
pavanaravapalli Nov 10, 2025
4a596e4
Update warning for KVM instance unmanaged metadata
pavanaravapalli Nov 12, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions source/adminguide/virtual_machines/importing_unmanaging_vms.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down