--- title: "Create a Manager instance using a qcow2 file" slug: "create-a-manager-instance-using-a-qcow2-file-3" tags: ["Install and Get Started", "IPS 11.1.x"] updated: 2026-11-19T12:29:31Z published: 2026-11-19T12:29:31Z canonical: "docs.trellix.com/create-a-manager-instance-using-a-qcow2-file-3" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Create a Manager instance using a qcow2 file You can create a virtual instance of the Linux-based Manager/Central Manager using the qcow2 file on both the KVM and the Nutanix platform. > [!WARNING] > Important > > **You cannot perform a direct upgrade from 11.1 Update 9 (MLOS) to 11.1 Update 10 (Trellix OS) using the** `upgrade` **command**. To install the 11.1 Update 10 version of the Trellix OS Manager on a VM, you must perform a fresh deployment and restore the `All Table Backup`. ### Create a Manager instance using a qcow2 file in the KVM server This section describes how to deploy the Linux-based Manager/Central Manager in a KVM environment. **Prerequisites:** - Verify your KVM setup meets the server requirements. See the corresponding sections in [Server requirements](/network-and-platform/docs/server-requirements-3) and [How to host the Manager on virtualization platforms](/network-and-platform/docs/how-to-host-the-manager-on-virtualization-platforms-1). - Install KVM on Red Hat Enterprise. For installation, refer to the section [Installing KVM on a Linux Machine](/network-and-platform/docs/installing-kvm-on-a-linux-machine) in Trellix Virtual Intrusion Prevention System 11.1.x Product Guide. **Steps:** The following steps describe how to install a Linux-based Manager/Central Manager through the KVM user interface: 1. Log on to the Linux server user interface using the IP address and the credentials. 2. Launch the virt-manager application by executing the `virt-manager` command through the server's command line terminal. > [!NOTE] > Note > > It is recommended to use MobaXterm for remotely accessing the virtual machine manager. It will direct you to a UI prompt where you can create the required virtual machine. If you have any instances running, you see these instances listed in this window. 3. Click the ![GUID-0186445C-CBEA-4DFB-9806-66D05AAA4DB8-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-e6eec574-b878-9a32-8003-f10b132ab7d2(2).png?sv=2026-02-06&spr=https&st=2026-11-20T05%3A29%3A41Z&se=2026-11-20T06%3A29%3A41Z&sr=c&sp=r&sig=8pAmFt%2F9aRgZlGgofuWR84gU0bW0Zs6du7AwCZ4Slnw%3D) icon to create a new virtual machine. The **Create a new virtual machine** wizard window appears. 4. In Step 1 of the wizard, you will be choosing the operating system (OS) installation format and the **Architecture**. Since you are installing the operating system from an image, you need to select the **Import existing disk image** radio button. 5. Click **Forward** to proceed to Step 2 of the wizard. In Step 2, you will be setting the: - Path where the image file is located - OS type - OS Version 6. From the **OS type** drop-down list, select **Linux**. 7. From the **Version** drop-down list, select **Red Hat Enterprise Linux Unknown** or **Red Hat Enterprise Linux 8.2**. 8. Browse to the location where the Linux-based Manager image is placed and select the .qcow2 image. Upon selecting the image, click **Forward**. > [!NOTE] > Note > > Trellix recommends that you place the software image in a folder other than the root folder. You come to Step 3 in the deployment, where you will be setting the memory and CPU requirements for the Manager. 9. Manually enter the **Memory (RAM)** and the number of **CPUs** required. The minimum required RAM is **20** GB, and the number of CPUs is **8**. 10. Click **Forward** to proceed to Step 4. 11. In Step 4 of the wizard: 1. Enter a name for the Manager. 2. Select the **Customize configuration before install** checkbox. 12. Click **Finish** to apply all the changes. You are routed to the next step in the deployment, where you can review the entire configuration tab-by-tab. 13. The configuration wizard appears with the **Overview** tab selected by default. This tab displays the basic configuration details of the VM. 1. Make sure that the **Hypervisor** is **KVM** and the **Architecture** is **x86_64**. 2. From the **Firmware** drop-down list, make sure **BIOS** is selected. 14. Click the **CPUs** tab. 1. Expand **Topology**, select the **Manually set CPU topology** checkbox and make sure that the number of **Sockets** is `1`, **Cores** are `8`, and **Threads** is `1` for better performance. 2. Click **Apply** to confirm your changes. 15. Click the **VirtIO Disk 1** tab. Navigate to **Advanced options**. From the **Direct bus** drop-down, select **IDE**, and click **Apply**. 16. Click the **NIC** tab. 1. From the **Network source** drop-down list, choose the required network interface, leave the other options set to default values, and click **Apply**. 17. Click **Begin Installation** to deploy the Linux-based Manager. Creation of the virtual machine begins. This process takes a few minutes. Once deployed, you can configure the Linux-based Manager using SSH. ### Create a Manager instance using a qcow2 file in the Nutanix server This section describes how to deploy the Linux-based Manager/Central Manager in a Nutanix environment. **Prerequisite**: Verify your Nutanix setup meets the server requirements. See the corresponding sections in [Server requirements](/network-and-platform/docs/server-requirements-3) and [How to host the Manager on virtualization platforms](/network-and-platform/docs/how-to-host-the-manager-on-virtualization-platforms-1). **Steps**: 1. Log on to **Prism Central** with administrator privileges using port 9440. For example: `https://<ip address>:9440/console/#` 2. Upload and deploy a qcow2 file in the Nutanix AHV platform: 1. Go to **Compute** → **Images** and select **Add Image**. The **Add Image** dialog box is displayed. 2. Select **Image File** from **Image Source** and click **Add File**. Go to the location where the qcow2 file is stored and select the required file. The qcow2 file will be displayed in the list after the upload process is complete. 3. Deploy the Linux-based Manager/Central Manager VM through **Prism Central**: 1. Navigate to **Compute** → **VM** and select **Create VM**. The **Create VM** dialog box is displayed. 2. Go to the **Configuration** tab, allocate the following details: 1. **Name**: Provide the name of VM. 2. **Project**: Provide the name of project. 3. **Cluster**: Provide the cluster details. 4. **Number of VMs**: Select the required number of VMs. 5. **CPUs**: Select the required number of CPU. The number of CPUs required are **8**. 6. **Cores Per CPU**: Select the required number of CPU cores. The cores per CPU required is **1**. 7. **Memory**: Select the required memory. The minimum required memory is **20** GB. 8. Click **Next**. 3. Go to **Disks** section of **Resources** tab: 1. Click **Attach Disk**. The **Attach Disk** dialog box is displayed. 2. **Operation**: Select **Clone from Image** from the drop-down. 3. **Image**: Select the imported qcow2 file from the drop-down. 4. **Bus Type**: Select **IDE** from the drop-down. 5. Click **Save**. 4. Go to **Networks** section of **Resources** tab: 1. Click **Attach to Subnet**. The **Attach to Subnet** dialog box is displayed. 2. **Subnet**: Select the required subnet from the drop-down and click **Save**. 5. Go to **Boot Configuration** and select **Legacy BIOS Mode**. Now, click **Confirm** to apply the configuration. 6. Click **Next**. 7. [Optional] Configure the required settings in **Management** tab and click **Next**. 8. Review the configurations and click **Create VM**. 4. Navigate to **Compute** → **VM** and select **List** tab: 1. From the list, select the newly created VM. 2. **Actions**: Go to **Power Operations** and click **Power On**. The VM launch could take approximately 7 to 8 minutes. 5. Once the VM is up and running, select the VM hyperlink and click on **Launch console** to configure the VM. ###