> 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-generic-kvm.md).

# Brain deployment in other KVM Virtual Machine Managers

Generic instructions for how to deploy a KVM virtual Brain in virtual machine managers other than the recommended ones.

{% hint style="warning" %}
This information is provided for reference and will not match your software exactly. You will have to be familiar with setting up virtual virtual machines using your software so that you can find the settings that correspond to the generic information documented here.
{% endhint %}

{% hint style="info" %}
**Please Note for 32 core KVM Brains:**

Per the [Introduction and requirements](/deployment/ndr-virtual-cloud-appliances/kvm-brain/introduction-and-requirements.md#performance-and-kvm-requirements) section, 32 core Brains may need their NUMA settings adjusted after deployment, before the initial power on. If deploying a 32 core Brain, please see [32 Core NUMA Configuration](#id-32-core-numa-configuration) for details on checking and, if required, setting the NUMA autosize parameter.
{% endhint %}

## Downloading the latest KVM Brain OVA or QCOW2 image

You may use either the OVA or the QCOW2 images, depending on what your virtual machine manager supports.

The current Brain images 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 and KVM (Proxmox) .ova Brain Image** or **KVM (Generic) .qcow2 Brain Image** and then the **File: Download** link.
  * A SHA256 hash is also provided to allow you to verify the download completed successfully.

{% hint style="info" %}
Always download a current copy when you go to deploy a new KVM 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 vSphere client from.
{% endhint %}

<figure><img src="https://4227135129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJ1ltuWFvsArFWtevnRn%2Fuploads%2FZRfjLcso7GWo9C9dMqdJ%2Fimage.png?alt=media&amp;token=0156cd7c-01c4-4a69-a06c-9162047c0cef" alt=""><figcaption></figcaption></figure>

<figure><img src="https://4227135129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJ1ltuWFvsArFWtevnRn%2Fuploads%2FscPqJd2HmGRwS3mGn1Mx%2Fimage.png?alt=media&amp;token=6c1c8c16-0910-4ead-9de6-affc49763b2a" alt=""><figcaption></figcaption></figure>

## If Deploying the OVA

* Import the OVA to your virtual machine management software.
* Deploy the OVA to a new virtual machine. Do not power it on yet.
* Proceed to [#virtual-hardware-configuration](#virtual-hardware-configuration "mention")

## If Deploying the QCOW2

* Import each disk to your virtual machine management software.
* Create a new virtual machine. Enter a name of your choice.
* Add **Disk 0** to the virtual machine first, followed by **Disk 1**.
* Do not power on the virtual machine yet.
* Proceed to [#virtual-hardware-configuration](#virtual-hardware-configuration "mention")

## Virtual hardware configuration

Make sure the hardware configuration of your virtual machine matches the following:

<table><thead><tr><th width="199">Hardware Item</th><th>Configuration</th></tr></thead><tbody><tr><td>Boot type</td><td>Legacy BIOS</td></tr><tr><td>Operating system (if available)</td><td>Closest match to "Linux 5.4 64-bit" or "Ubuntu 20.04 64-bit"</td></tr><tr><td>CPU</td><td>For less than 32-core Brains:<br>1 socket<br>Number of cores from <a data-mention href="/deployment/ndr-virtual-cloud-appliances/kvm-brain/kvm-deployment-details-and-considerations.md">KVM deployment details and considerations</a><br>For 32-core Brains: see <a data-mention href="#id-32-core-numa-configuration">#id-32-core-numa-configuration</a></td></tr><tr><td>Memory</td><td>Amount from <a data-mention href="/deployment/ndr-virtual-cloud-appliances/kvm-brain/kvm-deployment-details-and-considerations.md">KVM deployment details and considerations</a></td></tr><tr><td>Memory Ballooning</td><td>disabled</td></tr><tr><td>Disks</td><td><ul><li>disk-0</li><li>disk-1</li></ul><p>Controller: <code>virtio-scsi-single</code> or <code>virtio-scsi</code> or <code>virtio</code><br><em>Note: disk 0 must have a lower address on the controller than disk 1. Adding them in order should work for most virtual machine managers.</em></p></td></tr><tr><td>Network</td><td><ul><li>Connected to management network</li></ul><p>Controller: <code>virtio-net</code> or <code>virtio</code> (multiqueue enabled, number of queues equal to the number of CPU cores of the virtual machine)</p></td></tr><tr><td>Console</td><td>VGA (optional but recommended)</td></tr><tr><td>QEMU Guest Agent</td><td>Enabled (only network interface info and power control will be allowed by the Brain)</td></tr><tr><td>Cloud Init</td><td>None</td></tr><tr><td>Boot order</td><td>Disk 0 first</td></tr></tbody></table>

Once the virtual hardware configuration is correct, you may start the virtual machine.

## 32 Core NUMA Configuration

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

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

If your host system does not have enough resources in one NUMA node for the entire Brain, you will need to configure the Brain VM with two NUMA nodes as follows:

| Resource      | NUMA Node 0         | NUMA Node 1         |
| ------------- | ------------------- | ------------------- |
| Socket        | 0                   | 1                   |
| vCPUs         | 0-15                | 16-31               |
| RAM           | 50%                 | 50%                 |
| NUMA distance | Match host topology | Match host topology |

Make sure the vCPUs in each NUMA node correspond to physical CPU cores on the same NUMA node on the host system.

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

The 32 core Brain only supports 1 or 2 NUMA nodes. If the virtual NUMA configuration is incorrect, you might experience one of the following symptoms:

* Reduced Brain performance
* The VM reboots frequently, every 3 to 4 min
* The output of `show system-health` at the CLI of your KVM Brain contains a message about NUMA
  {% 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://docs.vectra.ai/deployment/ndr-virtual-cloud-appliances/kvm-brain/brain-deployment-in-generic-kvm.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.