> 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-xdr-3.x/cortex-xdr-3.x-documentation/data-management/broker-vm/set-up-and-configure-broker-vm/broker-vm-image-installations/set-up-broker-vm-on-nutanix-hypervisor.md). # Set up Broker VM on Nutanix Hypervisor After you download your Cortex XDR Broker virtual machine (VM) **QCOW2** image, you need to upload it to a Nutanix hypervisor. Nutanix AHV 10.3 or later is supported. {% hint style="warning" %} ### Prerequisite Download a Cortex XDR Broker VM **QCOW2** image. For more information, see the virtual machine compatibility requirements in [Set up and configure Broker VM](/cortex-xdr-3.x/cortex-xdr-3.x-documentation/data-management/broker-vm/set-up-and-configure-broker-vm.md). {% endhint %} Perform the following procedures in the order listed below.
Task 1. Upload the downloaded QCOW2 image file to a Nutanix hypervisor 1. Select **Compute** → **Images**, and click **Add Image**. 2. In the **Add Images** page, ensure the **Image Source** is set to **Image File**, and click **Add File**. 3. Select the downloaded QCOW2 file and click **Open**. Additional fields related to the QCOW2 file are automatically displayed in the **Add Image** page, where the **Name** and **Type** of file are automatically populated. Ensure the **Type** is set to **Disk**. 4. (Optional) Define the rest of the fields displayed for the QCOW2 file. 5. Click **Next**. 6. Select the location by defining the **Placement Method** and **Select Clusters** settings. 7. Click **Save**. The image is now listed in the list of images.

Note

Saving the image to Nutanix hypervisor can take time as it’s a large file. We recommend verifying periodically that the connection is alive for the upload process to finish successfully.

Task 2. Create a new VM 1. Select **Compute** → **VMs**, and click **Create VM**. 2. In the **Create VM** screen, set the following **Configuration** fields, and ensure the advanced settings options are not selected: * **Name**: Specify a name for the new VM. * **Description** (Optional): Specify a description to identify the VM. * **Number of VMs**: Select the number of VMs you want to create. The default is set to 1. * **VM Properties** * **CPU**: Select **4** CPUs. * **Cores per CPU**: Select the number of cores to create for each CPU. The default number is 1. * **Memory**: Select **8GB** as the allotted memory for the VM. 3. Click **Next**. 4. Set the **Resources** fields: **Disks** **Attach Disk** and set the following field settings: * **Type**: Leave the default **Disk** type. * **Operation**: Select **Clone from Image**. * **Image**: Select the QCOW2 image file that you uploaded. * **Capacity**: Specify the capacity of the image file as 512 GB. * **Bus Type**: Leave the default **SCUI** selected. When you finish, click **Save**. **Networks** **Attach to Subnet** and set the following field settings. * **Subnet**: Select the subnet from the list. * **Network Connection State**: Leave the default **Connected** option selected. When you finish, click **Save**. **Boot Configuration** Leave the default **Legacy BIOS Mode** selected. 5. Verify the **Shield VM Security Settings** options are not selected. 6. Click **Next**. 7. Set the **Management** fields, where you can leave the default settings for the various fields. 8. Click **Next**. 9. Click **Create VM**. The VM is now listed in the list of VMs.

Note

Creating the VM can take up to 15 minutes. The Broker VM Web user interface is not accessible during this time.

Task 3. Review the VM details for connecting to the VM Select **Summary** and you can use the **IP Addresses** and **Host IP** listed to connect to the VM.
--- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/cortex-xdr-3.x/cortex-xdr-3.x-documentation/data-management/broker-vm/set-up-and-configure-broker-vm/broker-vm-image-installations/set-up-broker-vm-on-nutanix-hypervisor.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.