GitHub user daviftorres edited a comment on the discussion: What does Snapshots, Backups, and Incremental Snapshots mean in CloudStack
> **Note:** I had to include memory because the instance snapshots could (in > that occasion) only be taken when the instance is in the Running state. > Please correct me if I am wrong. This instance was deployed from an ISO. Answering my own question, the fact that limited the Instance Snapshot without adding the memory was the missing setting `rootDiskController` = `osdefault`: <img width="1009" height="418" alt="image" src="https://github.com/user-attachments/assets/d3d547e0-52fe-4600-9a5c-88b161707097"; /> I managed to "fix" the ISO template by adding those settings in the table `vm_template_details`. <img width="477" height="90" alt="image" src="https://github.com/user-attachments/assets/cb874e90-52ee-4d3b-91b9-7396ae214ae4"; /> Besides the fix mentioned above, there is a limitation around mixing snapshot types. If a snapshot that includes memory already exists, the system does not allow creating a snapshot without memory. The reverse is also true. My understanding is that disk-only snapshots use QCOW2 metadata, while disk-plus-memory snapshots use a chain-based approach. Because these rely on different underlying mechanisms, mixing them is not allowed, likely to prevent data corruption or loss. Like described in PR https://github.com/apache/cloudstack/pull/11039 GitHub link: https://github.com/apache/cloudstack/discussions/12475#discussioncomment-15573905 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
