FreeSBC:Cloud:Proxmox Installation A - Revision history

Luc Morissette at 18:20, 24 July 2025

2025-07-24T18:20:11Z

← Older revision		Revision as of 14:20, 24 July 2025
Line 1:		Line 1:
	{{DISPLAYTITLE:ProSBC:Cloud:Proxmox Installation}}		{{DISPLAYTITLE:ProSBC:Cloud:Proxmox Installation}}

			= '''Please refer to this page instead:''' [https://docs.prosbc.com/initial-installation/1.-instructions-by-platform/virtual-self-hosted-installation/virtual-proxmox ProSBC Proxmox installation] =

			__________________________________________________________________________________________

	==Introduction==		==Introduction==

Allyntree: /* Tune VM for your ProSBC */

2024-08-23T15:13:28Z

Tune VM for your ProSBC

← Older revision		Revision as of 11:13, 23 August 2024
Line 105:		Line 105:
	== Tune VM for your ProSBC ==		== Tune VM for your ProSBC ==

	Go to the "Hardware" tab on your VM, ~~then~~:		Go to the "Hardware" tab on your VM, and do the following:

	*Remove CD/DVD Drive~~, because we~~ do not need it.		*Remove CD/DVD Drive. We do not need it.

	*Detach and delete Hard Disk. We do not need it and we will attach the KVM image later.		*Detach and delete Hard Disk. We do not need it and we will attach the KVM image later.

	*Add network adapters according to your network configuration. '''Keep in mimd''' that a standalone ProSBC needs at least one adapter for management and one for ~~the~~ voice, ~~for~~ initial setup. If you wish to have an HA configuration, then you need at least one more adapter for intra-cluster communications. Although, network adapters may be added at any time, it's a good idea to set up a correct network configuration at the start.		*Add network adapters according to your network configuration. '''Keep in mimd''' that a standalone ProSBC needs at least one adapter for management and one for voice, in the initial setup.

			If you wish to have an HA configuration, then you need at least one more adapter for intra-cluster communications. Although, network adapters may be added at any time, it's a good idea to set up a correct network configuration at the start.

	== Attaching image file to VM ==		== Attaching image file to VM ==

Allyntree: /* Create VM for ProSBC */

2024-08-23T15:11:46Z

Create VM for ProSBC

← Older revision		Revision as of 11:11, 23 August 2024
Line 98:		Line 98:
	In newer Proxmox versions (screenshot from version 8.2), you can delete the suggested disk by clicking on the trash can.<br><br/>		In newer Proxmox versions (screenshot from version 8.2), you can delete the suggested disk by clicking on the trash can.<br><br/>
	[[File:Proxmox installation, step HDD.png\|400px\|Proxmox 8.2]]<br/><br/>		[[File:Proxmox installation, step HDD.png\|400px\|Proxmox 8.2]]<br/><br/>
	3. CPU: choose core count. Important: CPU Type must be set to '''"host"'''.<br/><br/> [[File:Proxmox_CPU.png\|400px]]<br/><br/>		4. CPU: choose core count. Important: CPU Type must be set to '''"host"'''.<br/><br/> [[File:Proxmox_CPU.png\|400px]]<br/><br/>
	4. In the advanced area parameter "CPU units" may be increased to ensure that CPU resources will be allocated to ProSBC with priority.<br/><br/>		5. In the advanced area parameter "CPU units" may be increased to ensure that CPU resources will be allocated to ProSBC with priority.<br/><br/>
	5. Memory: Set the memory size<br/> [[File:Proxmox_Memory.png\|400px]]<br/><br/>		6. Memory: Set the memory size<br/> [[File:Proxmox_Memory.png\|400px]]<br/><br/>
	6. Network: Set up the interface you will use for management according to your network configuration. Model '''VirtIO''' tested, any other may work too.<br/> <br/>[[File:Proxmox_Network.png\|400px]]<br/><br/>		7. Network: Set up the interface you will use for management according to your network configuration. Model '''VirtIO''' tested, any other may work too.<br/> <br/>[[File:Proxmox_Network.png\|400px]]<br/><br/>

	== Tune VM for your ProSBC ==		== Tune VM for your ProSBC ==

Allyntree: /* Create VM for ProSBC */

2024-08-23T15:11:09Z

Create VM for ProSBC

Allyntree: /* Create VM for ProSBC */

2024-08-23T15:09:11Z

Create VM for ProSBC

← Older revision		Revision as of 11:09, 23 August 2024
Line 92:		Line 92:
	Follow the VM creation process by dialog tabs as below		Follow the VM creation process by dialog tabs as below

	#General: choose VM name and location as usual. This manual uses VM ID 1000 as a reference.<br/>		#General: choose VM name and location as usual. This manual uses VM ID 1000 as a reference.<br/><br/>
	#OS: check '''Do not use any media''', keep default Linux OS with '''4.X/3.X/2.6 Kernel'''. <br/> [[File:Proxmox_OS.png\|400px]]<br/>		#OS: check '''Do not use any media''', keep default Linux OS with '''4.X/3.X/2.6 Kernel'''. <br/><br/> [[File:Proxmox_OS.png\|400px]]<br/>
	#Hard Disk: choose your favorite device type and keep all the rest to default.<br/> [[File:Proxmox_HDD.png\|400px]]<br/><br/>		#Hard Disk: choose your favorite device type and keep all the rest to default.<br/> [[File:Proxmox_HDD.png\|400px]]<br/><br/>
	In newer Proxmox versions (screenshot from version 8.2), you can delete the suggested disk by clicking on the trash can.<br>		In newer Proxmox versions (screenshot from version 8.2), you can delete the suggested disk by clicking on the trash can.<br><br/>
	[[File:Proxmox installation, step HDD.png\|400px\|Proxmox 8.2]]		[[File:Proxmox installation, step HDD.png\|400px\|Proxmox 8.2]]<br/><br/>
	#CPU: choose core count. Important: CPU Type must be set to '''"host"'''.<br/> [[File:Proxmox_CPU.png\|400px]]		#CPU: choose core count. Important: CPU Type must be set to '''"host"'''.<br/><br/> [[File:Proxmox_CPU.png\|400px]]<br/>
	#*In the advanced area parameter "CPU units" may be increased to ensure that CPU resources will be allocated to ProSBC with priority.<br/>		#*In the advanced area parameter "CPU units" may be increased to ensure that CPU resources will be allocated to ProSBC with priority.<br/><br/>
	#Memory: Set the memory size<br/> [[File:Proxmox_Memory.png\|400px]]		#Memory: Set the memory size<br/> [[File:Proxmox_Memory.png\|400px]]
	#Network: Set up the interface you will use for management according to your network configuration. Model '''VirtIO''' tested, any other may work too.<br/> [[File:Proxmox_Network.png\|400px]]		#Network: Set up the interface you will use for management according to your network configuration. Model '''VirtIO''' tested, any other may work too.<br/> <br/>[[File:Proxmox_Network.png\|400px]]

	== Tune VM for your ProSBC ==		== Tune VM for your ProSBC ==

Allyntree at 14:58, 23 August 2024

2024-08-23T14:58:55Z

← Older revision		Revision as of 10:58, 23 August 2024
Line 94:		Line 94:
	#General: choose VM name and location as usual. This manual uses VM ID 1000 as a reference.<br/>		#General: choose VM name and location as usual. This manual uses VM ID 1000 as a reference.<br/>
	#OS: check '''Do not use any media''', keep default Linux OS with '''4.X/3.X/2.6 Kernel'''. <br/> [[File:Proxmox_OS.png\|400px]]<br/>		#OS: check '''Do not use any media''', keep default Linux OS with '''4.X/3.X/2.6 Kernel'''. <br/> [[File:Proxmox_OS.png\|400px]]<br/>
	#Hard Disk: choose your favorite device type and keep all the rest to default.<br/> [[File:Proxmox_HDD.png\|400px]]<br/>		#Hard Disk: choose your favorite device type and keep all the rest to default.<br/> [[File:Proxmox_HDD.png\|400px]]<br/><br/>
	In newer Proxmox versions (screenshot from version 8.2) you can ~~just~~ delete the suggested disk by clicking on the trash can<br>		In newer Proxmox versions (screenshot from version 8.2), you can delete the suggested disk by clicking on the trash can.<br>
	[[File:Proxmox installation, step HDD.png\|400px\|Proxmox 8.2]]		[[File:Proxmox installation, step HDD.png\|400px\|Proxmox 8.2]]
	#CPU: choose core count. Important: CPU Type must be set to '''"host"'''.<br/> [[File:Proxmox_CPU.png\|400px]]		#CPU: choose core count. Important: CPU Type must be set to '''"host"'''.<br/> [[File:Proxmox_CPU.png\|400px]]

Anestis Mavrofillidis at 12:04, 23 August 2024

2024-08-23T12:04:31Z

← Older revision		Revision as of 08:04, 23 August 2024
Line 95:		Line 95:
	#OS: check '''Do not use any media''', keep default Linux OS with '''4.X/3.X/2.6 Kernel'''. <br/> [[File:Proxmox_OS.png\|400px]]<br/>		#OS: check '''Do not use any media''', keep default Linux OS with '''4.X/3.X/2.6 Kernel'''. <br/> [[File:Proxmox_OS.png\|400px]]<br/>
	#Hard Disk: choose your favorite device type and keep all the rest to default.<br/> [[File:Proxmox_HDD.png\|400px]]<br/>		#Hard Disk: choose your favorite device type and keep all the rest to default.<br/> [[File:Proxmox_HDD.png\|400px]]<br/>
			In newer Proxmox versions (screenshot from version 8.2) you can just delete the suggested disk by clicking on the trash can<br>
			[[File:Proxmox installation, step HDD.png\|400px\|Proxmox 8.2]]
	#CPU: choose core count. Important: CPU Type must be set to '''"host"'''.<br/> [[File:Proxmox_CPU.png\|400px]]		#CPU: choose core count. Important: CPU Type must be set to '''"host"'''.<br/> [[File:Proxmox_CPU.png\|400px]]
	#*In the advanced area parameter "CPU units" may be increased to ensure that CPU resources will be allocated to ProSBC with priority.<br/>		#*In the advanced area parameter "CPU units" may be increased to ensure that CPU resources will be allocated to ProSBC with priority.<br/>

Allyntree at 14:55, 20 August 2024

2024-08-20T14:55:32Z

← Older revision		Revision as of 10:55, 20 August 2024
Line 1:		Line 1:
	{{DISPLAYTITLE:ProSBC:Cloud:Proxmox Installation}}		{{DISPLAYTITLE:ProSBC:Cloud:Proxmox Installation}}

	This step-by-step guide helps to install and run ProSBC KVM image on Proxmox platform. The installation requires root-level access to Proxmox host and ~~can not~~ be completed with web-interface ~~only~~.		==Introduction==
			This step-by-step guide helps you to install and run the ProSBC KVM image on a Proxmox platform. The installation requires root-level access to the Proxmox host, and it cannot be completed with web-interface alone.

	== Requirements ==		== Requirements ==
Line 63:		Line 64:
	Multiple 10 Gbps		Multiple 10 Gbps
	\|}		\|}
	<nowiki>**</nowiki> The CPU number is based on Intel R630 with Xeon E5-2643. Double the ~~CPUs~~ number if ~~yours are~~ from a earlier generations.		<nowiki>**</nowiki> The CPU number is based on Intel R630 with Xeon E5-2643. Double the CPU number if your processor is from a earlier generations.

	More details on HW/CPU/NIC requirements can be found here: [[FreeSBC:RequirementsMatrix\|RequirementsMatrix]]		More details on the HW/CPU/NIC requirements can be found here: [[FreeSBC:RequirementsMatrix\|RequirementsMatrix]]

	For better performance		For better performance
Line 74:		Line 75:

	== Getting the Image ==		== Getting the Image ==
	~~Please go~~ to our [http://freesbc.telcobridges.com/pricing/ ProSBC Download site] to get a copy of the latest ProSBC Image. In the Download Section, while filling the form, choose correct platform "KVM".		Go to our [http://freesbc.telcobridges.com/pricing/ ProSBC Download site] to get a copy of the latest ProSBC Image. In the Download Section, while filling out the form, choose the correct platform "KVM".
	As a result, you should ~~get file~~ freesbc_kvm_[version].qcow2. Please, mention "Product Key" and keep containing email in a safe place.		As a result, you should receive freesbc_kvm_[version].qcow2. Please, mention "Product Key" and keep containing email in a safe place.

	== Upload Image File to Proxmox cloud ==		== Upload Image File to Proxmox cloud ==
	You need an SFTP client to upload ProSBC image to Proxmox. For example, using WinSCP SFTP Client .		You need an SFTP client to upload ProSBC image to Proxmox. For example, using WinSCP SFTP Client .
	~~All the~~ next ~~step~~ assumed that image file freesbc_kvm_[version].qcow2 resides in the /root directory		The next steps assumed that the image file freesbc_kvm_[version].qcow2 resides in the /root directory

	== Unzip the file ==		== Unzip the file ==
	~~In case~~ you have received a .tar.gz file, ~~you can~~ unzip it with the command:		If you have received a .tar.gz file, unzip it with the command:

	tar -xvzf <filename>		tar -xvzf <filename>
Line 103:		Line 104:
	Go to the "Hardware" tab on your VM, then:		Go to the "Hardware" tab on your VM, then:

	*Remove CD/DVD Drive, we ~~don't~~ need it.		*Remove CD/DVD Drive, because we do not need it.

	*Detach and delete Hard Disk~~, we don't~~ need it and we will attach KVM image later		*Detach and delete Hard Disk. We do not need it and we will attach the KVM image later.

	*Add network adapters according to your network configuration. ~~Please, mind~~ that standalone ProSBC needs at least one for management and one for the voice for initial setup. If you wish to ~~use~~ HA configuration, then you need at least one more for intra-cluster communications. ~~While~~ network adapters may be added any time, it's a good idea to ~~setup~~ correct network configuration ~~just now~~.		*Add network adapters according to your network configuration. '''Keep in mimd''' that a standalone ProSBC needs at least one adapter for management and one for the voice, for initial setup. If you wish to have an HA configuration, then you need at least one more adapter for intra-cluster communications. Although, network adapters may be added at any time, it's a good idea to set up a correct network configuration at the start.

	== Attaching image file to VM ==		== Attaching image file to VM ==
Line 113:		Line 114:
	Go to Proxmox host shell and copy the image file to VM's directory, root privileges required. For VM ID 1000 and image file, located in /root this will be:		Go to Proxmox host shell and copy the image file to VM's directory, root privileges required. For VM ID 1000 and image file, located in /root this will be:
	cp -v /root/freesbc_kvm_[version].qcow2 /var/lib/vz/images/1000/		cp -v /root/freesbc_kvm_[version].qcow2 /var/lib/vz/images/1000/
	After that, we need force Proxmox to include this image to VM config file and make it available for web-interface. Do that with shell command qm rescan
			After that, we need to force Proxmox to include this image to the VM config file and make it available for web-interface. Do that with shell command qm rescan
	# qm rescan		# qm rescan
	rescan volumes...		rescan volumes...
	VM 1000: add unreferenced volume 'local:1000/freesbc_kvm_[version].qcow2' as 'unused0' to config.		VM 1000: add unreferenced volume 'local:1000/freesbc_kvm_[version].qcow2' as 'unused0' to config.
	#		#

	If qm rescan doesn't have the expected result, you can try following:		If qm rescan doesn't have the expected result, you can try following:
	#		#
	qm importdisk <vmid> <filename> <storage>		qm importdisk <vmid> <filename> <storage>
	#		#

	Return to the web-interface and VM's Hardware tab. Now the image referenced as "Unused Disk 0". Select it and press "Edit".		Return to the web-interface and VM's Hardware tab. Now the image referenced as "Unused Disk 0". Select it and press "Edit".

	Select bus/device and put "Write through" to the Cache selector. For some bugs, Proxmox VMs can't start with default in this field. Press "Add". Now the image attached as root drive. Make sure that device reference ~~math~~ in the "Boot Order" selector of VM's Options tab.		Select bus/device and put "Write through" to the Cache selector. For some bugs, Proxmox VMs can't start with default in this field. Press "Add". Now the image is attached as root drive. Make sure that device reference path is in the "Boot Order" selector of the VM's Options tab.

	~~Now~~, VM is ready to run.		At this point, the VM is ready to run.

	It's highly recommended to move the disk to ZFS storage and ~~make~~ a snapshot of this state to rollback in case of later installation mistakes. If you plan HA ProSBC installation, this point is ~~good~~ to clone VM. ~~Cloned~~ VM can be configured as the secondary later.		It's highly recommended to move the disk to ZFS storage, and to take a snapshot of this state. This snapshot can be used if you need to rollback, in case of later installation mistakes. If you plan an HA ProSBC installation, at this point it is wise to clone the VM. A cloned VM can be configured as the secondary later on.

	== Accessing the web portal ==		== Accessing the web portal ==
	# Open a web browser to the management IP of the ProSBC, on port 12358. ~~Example~~ if your server address is 192.168.178.30, the URL would be: <br/> http://192.168.178.30:12358		# Open a web browser to the management IP of the ProSBC, on port 12358. For example, if your server address is 192.168.178.30, the URL would be: <br/> http://192.168.178.30:12358
	# You should get to the ProSBC Configuration Wizard <br/> [[File:TSBC_WebPortal_Configuration_wizard.jpg\|350px]]		# You should get to the ProSBC Configuration Wizard <br/> [[File:TSBC_WebPortal_Configuration_wizard.jpg\|350px]]

	From here, you can go to [[TSBC-SW:WebPortal:Initial Configuration\|Web Portal Initial Configuration Guide]] to continue the installation.		From here, you can go to [[TSBC-SW:WebPortal:Initial Configuration\|Web Portal Initial Configuration Guide]] to continue the installation.

Anestis Mavrofillidis at 14:26, 20 August 2024

2024-08-20T14:26:27Z

← Older revision		Revision as of 10:26, 20 August 2024
Line 82:		Line 82:

	== Unzip the file ==		== Unzip the file ==
	In case you have received a .tar.gz file, you can ~~unzi~~ it with the command:		In case you have received a .tar.gz file, you can unzip it with the command:

	tar -xvzf <filename>		tar -xvzf <filename>

Anestis Mavrofillidis at 14:25, 20 August 2024

2024-08-20T14:25:56Z

← Older revision		Revision as of 10:25, 20 August 2024
Line 80:		Line 80:
	You need an SFTP client to upload ProSBC image to Proxmox. For example, using WinSCP SFTP Client .		You need an SFTP client to upload ProSBC image to Proxmox. For example, using WinSCP SFTP Client .
	All the next step assumed that image file freesbc_kvm_[version].qcow2 resides in the /root directory		All the next step assumed that image file freesbc_kvm_[version].qcow2 resides in the /root directory

			== Unzip the file ==
			In case you have received a .tar.gz file, you can unzi it with the command:
			tar -xvzf <filename>

	== Create VM for ProSBC ==		== Create VM for ProSBC ==

← Older revision		Revision as of 11:11, 23 August 2024
Line 90:		Line 90:

	Define the amount of CPUs and RAM according to requirements.		Define the amount of CPUs and RAM according to requirements.
	Follow the VM creation process by dialog tabs as below
			Follow the VM creation process by dialog tabs as indicated below:

	#General: choose VM name and location as usual. This manual uses VM ID 1000 as a reference.<br/><br/>		#General: choose VM name and location as usual. This manual uses VM ID 1000 as a reference.<br/><br/>
	#OS: check '''Do not use any media''', keep default Linux OS with '''4.X/3.X/2.6 Kernel'''. <br/><br/> [[File:Proxmox_OS.png\|400px]]<br/>		#OS: check '''Do not use any media''', keep default Linux OS with '''4.X/3.X/2.6 Kernel'''. <br/><br/> [[File:Proxmox_OS.png\|400px]]<br/><br/>
	#Hard Disk: choose your favorite device type and keep all the rest to default.<br/> [[File:Proxmox_HDD.png\|400px]]<br/><br/>		#Hard Disk: choose your favorite device type and keep all the rest to default.<br/><br/> [[File:Proxmox_HDD.png\|400px]]<br/><br/>
	In newer Proxmox versions (screenshot from version 8.2), you can delete the suggested disk by clicking on the trash can.<br><br/>		In newer Proxmox versions (screenshot from version 8.2), you can delete the suggested disk by clicking on the trash can.<br><br/>
	[[File:Proxmox installation, step HDD.png\|400px\|Proxmox 8.2]]<br/><br/>		[[File:Proxmox installation, step HDD.png\|400px\|Proxmox 8.2]]<br/><br/>
	#CPU: choose core count. Important: CPU Type must be set to '''"host"'''.<br/><br/> [[File:Proxmox_CPU.png\|400px]]<br/>		3. CPU: choose core count. Important: CPU Type must be set to '''"host"'''.<br/><br/> [[File:Proxmox_CPU.png\|400px]]<br/><br/>
	#*In the advanced area parameter "CPU units" may be increased to ensure that CPU resources will be allocated to ProSBC with priority.<br/><br/>		4. In the advanced area parameter "CPU units" may be increased to ensure that CPU resources will be allocated to ProSBC with priority.<br/><br/>
	#Memory: Set the memory size<br/> [[File:Proxmox_Memory.png\|400px]]		5. Memory: Set the memory size<br/> [[File:Proxmox_Memory.png\|400px]]<br/><br/>
	#Network: Set up the interface you will use for management according to your network configuration. Model '''VirtIO''' tested, any other may work too.<br/> <br/>[[File:Proxmox_Network.png\|400px]]		6. Network: Set up the interface you will use for management according to your network configuration. Model '''VirtIO''' tested, any other may work too.<br/> <br/>[[File:Proxmox_Network.png\|400px]]<br/><br/>

	== Tune VM for your ProSBC ==		== Tune VM for your ProSBC ==