> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/migrate-to-a-new-broker-vm-image/migrating-to-a-new-broker-vm-image.md).

# Learn more about migrating to the latest Broker VM image

Learn more about migrating to the latest Broker VM image in Cortex Cloud Runtime Security.

Following is the recommended process for migrating to the latest Broker VM image installed with Debian 13. This process ensures that you can upgrade to the latest supported Broker VM versions and continue to benefit from new features.

These procedures are recommended for all brokers that were deployed with a Broker VM image, downloaded prior to February 22, 2026 (installed with Ubuntu 20.04 or earlier).

{% hint style="warning" %}

#### Important

When a new Broker VM boots for the first time, it performs initial setup operations, which must complete successfully. Disturbing these operations by performing actions like taking a snapshot, hard resetting, or cloning the machine during this period can cause unrecoverable malfunctions. This process typically takes a few minutes to finish.

* **Do not perform a clone or snapshot while the machine is powered ON**.
* **If you need to shut down the Broker VM, ensure you do so gracefully** using the **Shutdown** option from the Cortex Cloud dashboard or the **Reset** option in the Broker VM TUI (administration console).
  {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/migrate-to-a-new-broker-vm-image/migrating-to-a-new-broker-vm-image.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
