> For the complete documentation index, see [llms.txt](https://docs.vectra.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vectra.ai/deployment/ndr-virtual-cloud-appliances/kvm-brain/brain-deployment-in-proxmox.md).

# Brain deployment in Proxmox

How to download the Brain .OVA and deploy it in Proxmox.

{% hint style="info" %}
**Please Note:**

Proxmox Brains use the same OVA source image as a VMware deployment. 
{% endhint %}

## Downloading the latest Brain OVA image

The current Brain OVA image can be downloaded from the Vectra Customer Support Portal after logging in.

The URL for the download page is: <https://support.vectra.ai/vectra/additional-resources>.

* Click on the **Download** tab.
* Click on the **VMWare Brain OVA File** (see note above) and then the **File: Download** link.
  * A SHA256 hash is also provided to allow you to verify the download.

{% hint style="info" %}
Always download a current copy when you go to deploy a new Proxmox Brain for your organization. This will save time during deployment as fewer updates will need to be downloaded after deployment. Make this file available via a URL or the local filesystem where you will run the Proxmox client from.
{% endhint %}

<figure><img src="https://4227135129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJ1ltuWFvsArFWtevnRn%2Fuploads%2FKQhu9lN7RbDrF1D7dupy%2Fimage.png?alt=media&amp;token=07201acd-b4f2-4515-97c5-121db1f8e5a3" alt=""><figcaption></figcaption></figure>

## Deploying the OVA in Proxmox

* Log into your Proxmox web interface.

* Enable imports in your storage location:

  * In the left sidebar, click **Datacenter.**
  * Click **Storage,** select the storage location, and click the **Edit** button:

  <figure><img src="https://4227135129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJ1ltuWFvsArFWtevnRn%2Fuploads%2FG9Af4U4m9FKE5UIOjB8Z%2Fimage.png?alt=media&amp;token=93cbb75d-7c88-4d92-9116-c06126eb709f" alt=""><figcaption></figcaption></figure>

  * In the **Edit** popup, within the **Content** dropdown, ensure that **Import, Disk Image,** and **ISO Image** are selected:

  <figure><img src="https://4227135129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJ1ltuWFvsArFWtevnRn%2Fuploads%2FOmMKKhoxeQDjNjNrkzdD%2Fimage.png?alt=media&amp;token=1e077728-50a4-4445-9b26-c981d4d08356" alt=""><figcaption></figcaption></figure>

* Import the OVA
  * In the left sidebar, click the storage location you just edited.
  * Click **Import**, and then click the either the **Upload** button (for locally stored files) or the **Download from URL** button (for files stored remotely).
  * Select your file location or paste the URL and select **Upload** or **Download**, respectively.
  * Select the URL or Local file option depending on where you made the image available.
  * When the import completes, a text summary will appear with "TASK OK" at the bottom.  Close the popup window:

<figure><img src="https://4227135129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJ1ltuWFvsArFWtevnRn%2Fuploads%2FaluSJvkCWje7zz6WoOW9%2Fimage.png?alt=media&amp;token=fd87547d-5020-424b-a41d-eccee83787a9" alt=""><figcaption></figcaption></figure>

* Deploy the Brain from the OVA file:

  * Double click the imported file - an **Import Guest** window will appear.
  * Name the VM what you'd like.
  * Change the **CPU Type** dropdown to **host** - this allows the CPU instruction sets to be passed through properly.
  * Set the total number of cores and RAM to match one of the supported sizes described in the [Introduction and requirements](/deployment/ndr-virtual-cloud-appliances/kvm-brain/introduction-and-requirements.md#performance-and-kvm-requirements) section.
  * In the **Default Storage** dropdown, select a thin-provision (lvmthin) device.
  * In the **Default Bridge** dropdown, select the bridge network you'd like the VM to be connected to.
  * Example 8 core deployment:

  <figure><img src="https://4227135129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJ1ltuWFvsArFWtevnRn%2Fuploads%2FJ6ar0rmdspZs8Mi6zl2H%2Fimage.png?alt=media&amp;token=b0a5dbdc-fedf-4e82-96f4-48991169acde" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Please Note: 32 Core NUMA Configuration**

This section applies to the 32 core Brain only. No changes are required for other Brain sizes.

The required Proxmox NUMA configuration cannot be reliably specified in the `.ova`. On some 32 core Proxmox Brains, depending on the underlying hardware platform, the CPU topology may need to be changed by the customer after VM deployment. Otherwise, the Brain may encounter errors during boot.

If the VM reboots frequently (approximately every 3 to 4 minutes), run `show system-health` from the Brain CLI. If the output contains a NUMA-related error, the VM may require a different CPU topology.

If you experience this issue, change the CPU configuration from **1 socket × 32 cores** to **2 sockets × 16 cores**.

To do this, shut down the VM and go to the **Hardware** section in Proxmox. Select **Processors**, then change the number of sockets to **2** and the number of cores to **16**.

Then **Start** the VM again.
{% endhint %}

* Click the **Import** button, wait for the operation to complete:

<figure><img src="https://4227135129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJ1ltuWFvsArFWtevnRn%2Fuploads%2FljSIMJPDgWa2aU5BffTy%2Fimage.png?alt=media&amp;token=6710ab87-4d85-4984-9d86-b75b8c324d07" alt=""><figcaption></figcaption></figure>

* After the import completes, the VM is created and shown in the **Virtual Machines** list.
* Change the **SCSI Controller** type.
  * In the sidebar, select the newly created VM.
  * Click **Hardware** in the submenu.
  * Double click the **SCSI Controller** entry.
  * In the dropdown, select **VirtIO SCSI Single.**
  * Click **OK.**
* Change the **Network Device** type.
  * In the sidebar, select the newly created VM.
  * Click **Hardware** in the submenu.
  * Double click the **Network Device** entry.
  * In the **Model** dropdown, select **VirtIO (paravirtualized).**
  * Set **Multiqueue** to the number of CPU cores of the Brain. (If this is not visible, click on the **Advanced** checkbox.)
  * Click **OK.**
* Change the QEMU Guest Agent Settings:
  * In the sidebar, select the newly created VM.
  * Click **Options** in the submenu.
  * Double click the **QEMU Guest Agent** entry.
  * Check the **Use QEMU Guest Agent** checkbox.
  * Select the **VirtIO** type from the **Type** dropdown.
* Start the VM
  * In the sidebar, select the newly created VM.
  * At the top of the screen, click **Start.**


---

# 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://docs.vectra.ai/deployment/ndr-virtual-cloud-appliances/kvm-brain/brain-deployment-in-proxmox.md?ask=<question>&goal=<endgoal>
```

`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.