--- title: "Nodegrid Manager instatltion on Linux Qemu/KVM" slug: "nodegrid-manager-installation-on-linux-qemukvm" updated: 2024-08-26T08:50:20Z published: 2024-08-26T08:50:20Z canonical: "docs.zpesystems.com/nodegrid-manager-installation-on-linux-qemukvm" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.zpesystems.com/llms.txt > Use this file to discover all available pages before exploring further. # Nodegrid Manager installation on Linux Qemu/KVM This documentation details steps to create a Nodegrid Manager VM instance on Linux Qemu/KVM. Kernel-based Virtual Machine (KVM) is a full virtualization solution for Linux on x86 hardware with virtualization extensions support (e.g., Intel VT or AMD-V). It consists of a loadable kernel module on the host (kvm.co) that provides core virtualization infrastructure and a processor-specific module (e.g., kvm-intel.ko or kvm-amd.ko). KVM is a type 1 hypervisor (i.e., bare metal hypervisor) and enables the definition of virtual machines (VM guests). Each VM has private virtualized hardware like a network card, disk, graphics adapter, serial ports, and others. > The kernel component of KVM is included in mainline Linux, as of 2.6.20. The user space component of KVM is included in mainline QEMU, as of 1.3. The following diagram, Diagram-1, depicts the expected result: ![image.png](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/image-4CEFY1CI.png) This guide structure is as follows: 1. Linux Host requirements 2. Nodegrid Manager ISO image 3. Create a Nodegrid Manager instance 4. Web Access to the Nodegrid Manager ## 1. Linux Host requirements The requirements for Linux Qemu/KVM include: - Hardware: - Virtualization Technologies for x86 (AMD-V / Intel VT) - Software: - Linux kernel 2.6.20 or newer - QEMU 1.3 or newer This guide consider the following software: - OS: [Debian 11 *bullseye*](https://www.debian.org/releases/bullseye/) - [Libvirt](https://libvirt.org/), the virtualization API > libvirt is an open-source API, daemon and management tool for managing platform virtualization. - Virtual Machine Manager [virt-manager](https://virt-manager.org/) > The virt-manager application is a desktop user interface to manage virtual machines through libvirt. > NOTE: virt-manager is not required to be installed on the KVM hypervisor. It can be installed in a desktop, with `ssh` access to the KVM hypervisor. Here are further details about KVM installation on Debian 11 [https://wiki.debian.org/KVM](https://wiki.debian.org/KVM#Installation). ## 2. Nodegrid Manager ISO image The following steps describe how to obtain a Nodegrid Manager ISO file: 1. Access with your credentials to [https://zpecloud.com](https://zpecloud.com) or [https://zpecloud.eu](https://zpecloud.eu) based on your region. 2. Go to *PROFILES :: SOFTWARE*. 3. Select a VSR Nodegrid version, e.g., *Nodegrid_Platform_v5.8.2_20230114* 4. Download the ISO file > NOTE: The iso file can be obtained through the support portal. ## 3. Create a Nodegrid Manager instance The following steps describe the procedure to deploy a VM instance using the *virt-manager* graphical interface. This creates the resources shown in the *Diagram-1*. 1. Open the application *virt-manager* (Virtual Machine Manager) on your desktop 2. If the KVM hypervisor is installed on the same machine, skip to step 3. To access a remote KVM hypervisor via `ssh`: - Select **File > Add Connection** - Click **Connect to remote host over SSH** - Enter the credentials - Click **Connect** 3. Click **Create a new virtual machine**. 4. Click **Local install media (ISO image or CDROM) > Forward** ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/kvm-vm-1.png) 1. On **Choose ISO or CDROM install media**, go to **Browse > Browse Local** and locate the downloaded ISO file. 2. On **Choose the operating system to install**, insert *Generic Linux 2022* (unselect *Automatically detect from the installation media/source*) ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/kvm-vm-2.png) 1. Select **Memory**=4096, and **CPUs**=2 ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/kvm-vm-3.png) 1. **Create a disk image for the virtual machine** of 25GiB or greater ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/kvm-vm-4.png) 1. On the **Ready to begin installation** page: - Enter **Name** for the VM, e.g., *vsr-kvm-1* - Click **Customize configuration before install** - Select **Network selection > Virtual network 'default': NAT** - Click **Finish** ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/kvm-vm-5.png) The following window displays: ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/kvm-vm-6.png) The following configurations are required prior to **Begin Installation** 1. Select **Overview > Firmware > UEFI X86_64:/usr/share/OVMF/OVMF_CODE_4M.fd**. Apply the changes. ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/kvm-vm-7.png) 1. Select **Disk 1 > Disk bus: SATA > Apply** ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/kvm-vm-8.png) 1. Select **Add Hardware > TPM > Type: Emulated > Finish > Apply**. ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/kvm-vm-9.png) 1. Select **Add Hardware > Serial > Device Type: Output to a file (file)** - In **Path** enter a file path, e.g., */tmp/vsr-kvm-1.serial* - Select **Finish > Apply** ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/kvm-vm-10.png) 1. Click **Begin Installation**. The VM installation process starts. The VM installation process is: 1. Select **Normal Nodegrid installation** ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/vm-1.png) 1. To accept the License Agreement, enter *accept* ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/vm-2.png) 1. The Nodegrid Manager installation process shall take place. Once finished, reboot the VM ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/vm-3.png) 1. After the VM reboots, access the Nodegrid Manager terminal with these credentials: - user: admin - password: admin 2. Follow the process to change the admin password ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/vm-4.png) 1. On the CLI, execute the following commands: ```plaintext show settings/network_connections/ show system/routing_table ``` ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/vm-5.png) In this example, the IP address assigned to the Nodegrid Manager is `192.168.122.171`. The next section details how to access the Nodegrid Manager Web UI. ## 4. Web Access to the Nodegrid Manager To access the Nodegrid Manager WebUI depends on the client location: 1) access from the KVM hypervisor (same host), 2) access from a remote client (KVM hypervisor in a remote server) For the first case: 1. Open the link https://private-IP in a browser, e.g., https://192.168.122.171 2. Log in to the Nodegrid Manager Web UI. Default credentials: - user: admin - password: admin 1. Change the password 2. Congratulations! You have successfully deployed a Nodegrid Manager ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/web-ui-local.png) For the second case, the following options are: - Add a new interface to the VM that is bridged to your local LAN - Forward TCP/80 and TCP/8080 ports on the hypervisor toward the VM ## 5. Enroll Nodegrid Manager to ZPE Cloud A Nodegrid Manager can be managed from ZPE Cloud. It must be enrolled to the customer's ZPE Cloud instance. 1. Login to the ZPE Cloud account [Global](https://zpecloud.com) , [EU](https://zpecloud.eu), or onPrem 2. Go to *SETTINGS :: ENROLLMENT :: CLOUD*. 3. Copy the **Customer Code** and **Enrollment Key** (required to claim the vSR). ![settings-enrolment-cloud](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/settings-enrolment-cloud.png) 4. In a browser, login to Nodegrid Manager with **https://**. 5. Go to *Security :: Services* and enable ZPE Cloud service ![security-zpecloud](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/security-zpecloud.png) 6. Go to *System :: Toolkit :: Cloud Enrollment*. ![system-toolkit](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/system-toolkit.png) 7. Enter the following information 1. **URL**: URL of the zpecloud instance, default https://zpecloud.com for US users and https://zpecloud.eu for EU users. 2. **Customer Code**: Use the copied Customer Code from the Cloud Instance 3. **Enrollment Key**: Use the copied Enrollment Key ![settings-enrolment-cloud](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/settings-enrolment-cloud.png) 8. Click **ENROLL**. ![system-toolkit-cloud-enrolment-success](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/system-toolkit-cloud-enrolment-success.png) 9. The unit is enrolled on ZPE Cloud and become available in ZPE Cloud under *DEVICES :: AVAILABLE*. ![devices-available](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/devices-available.png) 10. To start management of the vSR, select and click on **ENROLL**. 11. When enrolled, the vSR is managed on ZPE Cloud the same as any other Nodegrid device.