AdminGuide:GettingStarted:VM:Proxmox
Return to AdminGuide:GettingStarted:VM
Update - 10/05/2020 A new Kalliope image for Proxmox VE environment is now available, which overcomes the limitations of the previous image to use a maximum of 8 vCPUs and to have a default disk size of 22GB. The new image, prepared on Proxmox VE version 6.1 environment and having a 120GB disk, handles up to a maximum of 128 vCPUs. NOTE: It is not possible to upgrade the VM with 8vCPUs to the one that supports more than 8, so in case of new installations it is recommended to install the new image anyway, even if it will be assigned a number of vCPUs equal or lower than 8.
To install KalliopPBX on Proxmox environment you first need to download the two files: .vma.lzo and .log in the folder: /var/lib/vz/dump/
| Image | Download Link |
|---|---|
| KalliopePBX v4 (max 128 vCPU) | https://areaclienti.vianova.it/drive/download/6qmKASR4EfpHbG11/ (vzdump-qemu-100-2020_05_10-23_03_40.vma.lzo - 1,4 GB) https://areaclienti.vianova.it/drive/download/F9zgxpv8UAhcJerD/ (vzdump-qemu-100-2020_05_10-23_03_40.log) |
| KalliopePBX v4 (max 8 vCPU) | https://areaclienti.vianova.it/drive/download/0hh0XCroc9AOsFzt/ (vzdump-qemu-200-2017_06_28-10_06_39.vma.lzo - 1,0 GB) https://areaclienti.vianova.it/drive/download/vcZYocwlyIeqoHHd/ (vzdump-qemu-200-2017_06_28-10_06_39.log) |
Once copied the two files related to the image you want to install inside the /var/lib/vz/dump folder of the host machine (keeping the original names, indicated above), the restore command must be executed in a new VM:
.
# qmrestore vzdump-qemu-<versione>.vma.lzo <nnn> --storage <storage_name>
Where:
- <nnn> is the id to be assigned to the VM (must not be already assigned to other VMs in the Proxmox node/cluster).
- <storage_name> is the name of the storage in which you restore the VM to (normally it is "local" or "storage").
The VM is now operational and you can boot it and access the console to configure the network address.
IMPORTANT NOTE: Before starting the virtual machine, it is necessary to change the VM settings by enabling the "KVM hardware virtualization" flag, which is disabled in the exported image, otherwise performance will be extremely slow. The new image already has this flag enabled by default, so it is no longer necessary to change this setting; however, it is recommended to check its actual value.
NOTE: The VM is deployed with a generic vCPU model, which emulates a Pentium 4 processor, for maximum compatibility. If you use the VM on a single node, or you have homogeneous Proxmox VE nodes in terms of physical CPUs, you can change the processor model to the "host" value, which directly remaps the functions of the physical processor, thus making available to the OS of the VM all the hardware extensions present on the server CPUs. In this regard, refer to the Proxmox documentation page, section "CPU Type": https://pve.proxmox.com/wiki/Qemu/KVM_Virtual_Machines#_emulated_devices_and_paravirtualized_devices
After this, you can operate as with other VMs, i.e. by accessing with manager/manager credentials, and a wizard will let you configure the network settings.
Once on the network, activation and configuration is done via web interface (initially on port 10080, and after installation of the phone firmware on standard port 80). In case UNSAFE_PORT error appears follow this procedure (Click here).
The VM must be able to reach in HTTP our license and update servers (license.kalliopepbx.it and updates.kalliopepbx.it), which currently both resolve the IP address 77.72.27.4.