Import the appliance into Proxmox

You need the .qcow2 file from Download & setup on dash.retivo.net. See Install the Retivo appliance for what the VM needs.

With the shell (quickest)

On the Proxmox host (Datacenter > your node > Shell), download the image and create the VM. Use a free VM ID instead of 9100, and your storage instead of local-lvm:

cd /var/tmp
wget https://download.retivo.ae/appliance/<version>/retivo-appliance-<version>.qcow2
qm create 9100 --name retivo --memory 4096 --cores 2 --cpu host --ostype l26 \
  --net0 virtio,bridge=vmbr0 --scsihw virtio-scsi-single --agent enabled=1 --serial0 socket
qm importdisk 9100 retivo-appliance-<version>.qcow2 local-lvm
qm set 9100 --scsi0 local-lvm:vm-9100-disk-0,discard=on,ssd=1 --boot order=scsi0
qm start 9100
rm retivo-appliance-<version>.qcow2

Use the bridge that reaches your devices and the internet instead of vmbr0, and add ,tag=<VLAN> to --net0 if that network is a VLAN.

Open the VM's Console in the Proxmox web interface and carry on with First start of the appliance.

With the web interface

1. Upload the .qcow2 to a storage that holds disk images: your storage > Import > Upload (Proxmox VE 8.2 and later), or copy it to the host with scp.
2. Create VM: name retivo; OS: Do not use any media, type Linux; System: SCSI controller VirtIO SCSI single, tick Qemu Agent; Disks: delete the default disk; CPU: 2 cores, type host; Memory: 4096 MB; Network: your bridge, model VirtIO. Don't start it yet.
3. Attach the image: on Proxmox VE 8.2 and later, Hardware > Add > Hard Disk, choose Import and pick the uploaded image. On older versions, run the qm importdisk and qm set lines above in the host shell.
4. Options > Boot Order: enable the new disk and move it to the top.
5. Start the VM and open its Console.

Good to know

• The appliance includes the QEMU guest agent: Proxmox shows its IP address and shuts it down cleanly.
• Make the disk bigger with Hardware > Disk Action > Resize; the appliance uses the new space after the next start.
• Don't clone the VM to make a second Retivo: dash.retivo.net refuses a clone. Import the image again and link the new VM as its own node.