AdminGuide:GettingStarted:VM:Proxmox/en - Cronologia

Troccoli il 14:46, 16 feb 2022

2022-02-16T14:46:45Z

← Versione meno recente		Versione delle 14:46, 16 feb 2022
Riga 22:		Riga 22:
	<code># qmrestore vzdump-qemu-<versione>.vma.lzo <nnn> --storage <storage_name></code>		<code># qmrestore vzdump-qemu-<versione>.vma.lzo <nnn> --storage <storage_name></code>

	~~<div class="mw-translate-fuzzy">~~		Where:
	~~where~~ <nnn> is the ~~ID you wish~~ to ~~assign~~ to the VM (it must not be assigned to ~~any~~ other VMs~~). This step can be performed through~~ the Proxmox ~~GUI~~.		* '''<nnn>''' is the id to be assigned to the VM (must not be already assigned to other VMs in the Proxmox node/cluster).
	<~~/div~~>		* '''<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.		The VM is now operational and you can boot it and access the console to configure the network address.

	~~<div class="mw-translate-fuzzy">~~		'''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.
	'''~~N.B.~~''': ~~before booting~~ the machine, ~~you must edit~~ the VM settings ~~to enable~~ the "KVM ~~Hardware acceleration~~" flag, otherwise performance will be slow.
	~~</div>~~

	'''~~NOTA~~''': la VM ~~viene distribuita con un modello di~~ vCPU ~~generico~~, ~~che emula un processore~~ Pentium 4, ~~per la massima compatibilità~~. ~~Nel caso in cui si utilizzi la~~ VM ~~su singolo nodo~~, ~~o si disponga di nodi~~ Proxmox VE ~~omogenei~~ in ~~termini di CPU fisiche~~, ~~è possibile modificare il modello del processore al valore~~ "host", ~~che rimappa direttamente le funzioni del processore fisico~~, ~~rendendo quindi disponibili al S.O. della~~ VM ~~tutte le estensioni~~ hardware ~~presenti sulle CPU del~~ server. ~~A tale proposito si rimanda alla pagina di documentazione~~ Proxmox, ~~sezione~~ "CPU Type": https://pve.proxmox.com/wiki/Qemu/KVM_Virtual_Machines#_emulated_devices_and_paravirtualized_devices		'''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.		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.

	~~<div class="mw-translate-fuzzy">~~		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 ([[AdminGuide:Procedures:ERR_UNSAFE_PORT_resolution_for_Chrome_and_Firefox/en\|Click here]]).
	Once ~~the VM is connected to~~ the network, ~~you can activate~~ and ~~configure it through the~~ web interface (initially on port 10080, and after ~~installing~~ the phone firmware on ~~the~~ standard port 80).
	</~~div>~~

	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.		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.

Troccoli: Creata pagina con "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 re..."

2022-02-16T14:39:03Z

Creata pagina con "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 re..."

← Versione meno recente		Versione delle 14:39, 16 feb 2022
Riga 2:		Riga 2:
	Return to [[AdminGuide:GettingStarted:VM/en\|AdminGuide:GettingStarted:VM]]		Return to [[AdminGuide:GettingStarted:VM/en\|AdminGuide:GettingStarted:VM]]

	'''Update on 10/05/2020'''		'''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.		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.		'''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.

	~~Per installare~~ KalliopPBX ~~su ambiente~~ Proxmox ~~è necessario per prima cosa scaricare i due file~~ .vma.lzo e .log ~~nella cartella~~ /var/lib/vz/dump/		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/

	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
	! ~~Immagine~~ !! Link ~~download~~		! 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) <br> https://areaclienti.vianova.it/drive/download/F9zgxpv8UAhcJerD/ (vzdump-qemu-100-2020_05_10-23_03_40.log)		\| 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) <br> https://areaclienti.vianova.it/drive/download/F9zgxpv8UAhcJerD/ (vzdump-qemu-100-2020_05_10-23_03_40.log)
Riga 17:		Riga 17:
	\|}		\|}

	~~Una volta copiati i due file relativi all'immagine che si intende installare all'interno della cartella~~ /var/lib/vz/dump ~~della macchina~~ host (~~mantenendo i nomi originali~~, ~~indicati sopra~~), ~~deve essere eseguito il comando di ripristino~~ in ~~una nuova~~ VM:<br>		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:<br>.

Troccoli: Creata pagina con "'''Update on 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..."

2022-02-16T14:36:40Z

Creata pagina con "'''Update on 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..."

← Versione meno recente		Versione delle 14:36, 16 feb 2022
Riga 2:		Riga 2:
	Return to [[AdminGuide:GettingStarted:VM/en\|AdminGuide:GettingStarted:VM]]		Return to [[AdminGuide:GettingStarted:VM/en\|AdminGuide:GettingStarted:VM]]

	'''~~Aggiornamento del~~ 10/05/2020'''		'''Update on 10/05/2020'''
	~~E' disponibile una nuova immagine~~ Kalliope ~~per ambiente~~ Proxmox VE, ~~che supera i limiti della precedente immagine di poter utilizzare un massimo di~~ 8 ~~vCPU e di avere un disco di dimensioni predefinite pari~~ a 22GB. ~~La nuova immagine~~, ~~predisposta su ambiente~~ Proxmox VE ~~versione~~ 6.1 ~~e che dispone di un disco di 120 GB~~, ~~gestisce fino ad un massimo di~~ 128 ~~vCPU~~.		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.
	'''~~NOTA~~:''' ~~Non è possibile aggiornare la~~ VM ~~con 8vCPU a quella che ne supporta oltre~~ 8, ~~per cui~~ in ~~caso di nuove installazioni si raccomanda comunque di installare la nuova immagine~~, ~~anche se le saranno assegnate un numero di vCPU pari o inferiore~~ a 8.		'''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.

	Per installare KalliopPBX su ambiente Proxmox è necessario per prima cosa scaricare i due file .vma.lzo e .log nella cartella /var/lib/vz/dump/		Per installare KalliopPBX su ambiente Proxmox è necessario per prima cosa scaricare i due file .vma.lzo e .log nella cartella /var/lib/vz/dump/

FuzzyBot: Aggiornamento come da nuova versione della pagina di origine

2022-02-16T14:35:52Z

Aggiornamento come da nuova versione della pagina di origine

← Versione meno recente		Versione delle 14:35, 16 feb 2022
Riga 2:		Riga 2:
	Return to [[AdminGuide:GettingStarted:VM/en\|AdminGuide:GettingStarted:VM]]		Return to [[AdminGuide:GettingStarted:VM/en\|AdminGuide:GettingStarted:VM]]

			'''Aggiornamento del 10/05/2020'''
			E' disponibile una nuova immagine Kalliope per ambiente Proxmox VE, che supera i limiti della precedente immagine di poter utilizzare un massimo di 8 vCPU e di avere un disco di dimensioni predefinite pari a 22GB. La nuova immagine, predisposta su ambiente Proxmox VE versione 6.1 e che dispone di un disco di 120 GB, gestisce fino ad un massimo di 128 vCPU.
			'''NOTA:''' Non è possibile aggiornare la VM con 8vCPU a quella che ne supporta oltre 8, per cui in caso di nuove installazioni si raccomanda comunque di installare la nuova immagine, anche se le saranno assegnate un numero di vCPU pari o inferiore a 8.

	~~The KalliopePBX image~~ file ~~for Proxmox-VE (4~~.~~4) environment can be downloaded at the following link:~~		Per installare KalliopPBX su ambiente Proxmox è necessario per prima cosa scaricare i due file .vma.lzo e .log nella cartella /var/lib/vz/dump/

	vzdump-qemu-200-2017_06_28-10_06_39.vma.lzo : <br>		{\| class="wikitable"
	https://areaclienti.vianova.it/drive/download/~~0hh0XCroc9AOsFzt~~/		\|-
			! Immagine !! Link download
			\|-
			\| 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) <br> 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) <br> https://areaclienti.vianova.it/drive/download/vcZYocwlyIeqoHHd/ (vzdump-qemu-200-2017_06_28-10_06_39.log)
			\|}

	~~vzdump-qemu-200-2017_06_28-10_06_39.log~~ : <br>		Una volta copiati i due file relativi all'immagine che si intende installare all'interno della cartella /var/lib/vz/dump della macchina host (mantenendo i nomi originali, indicati sopra), deve essere eseguito il comando di ripristino in una nuova VM:<br>
	~~https://areaclienti.vianova.it/drive/download/vcZYocwlyIeqoHHd/~~


	~~The following is the procedure for restoring in a Proxmox environment:~~		<code># qmrestore vzdump-qemu-<versione>.vma.lzo <nnn> --storage <storage_name></code>

	~~1. Copy the two files to the /var/lib/vz/dump folder of the host machine, without renaming them.~~

	~~2. Execute the command~~

	<code># qmrestore ~~/var/lib/vz/dump/Kalliope..~~.vma.lzo <nnn></code>

			<div class="mw-translate-fuzzy">
	where <nnn> is the ID you wish to assign to the VM (it must not be assigned to any other VMs). This step can be performed through the Proxmox GUI.		where <nnn> is the ID you wish to assign to the VM (it must not be assigned to any other VMs). This step can be performed through the Proxmox GUI.
			</div>

	The VM is now operational and you can boot it and access the console to configure the network address.		The VM is now operational and you can boot it and access the console to configure the network address.

			<div class="mw-translate-fuzzy">
	'''N.B.''': before booting the machine, you must edit the VM settings to enable the "KVM Hardware acceleration" flag, otherwise performance will be slow.		'''N.B.''': before booting the machine, you must edit the VM settings to enable the "KVM Hardware acceleration" flag, otherwise performance will be slow.
			</div>

			'''NOTA''': la VM viene distribuita con un modello di vCPU generico, che emula un processore Pentium 4, per la massima compatibilità. Nel caso in cui si utilizzi la VM su singolo nodo, o si disponga di nodi Proxmox VE omogenei in termini di CPU fisiche, è possibile modificare il modello del processore al valore "host", che rimappa direttamente le funzioni del processore fisico, rendendo quindi disponibili al S.O. della VM tutte le estensioni hardware presenti sulle CPU del server. A tale proposito si rimanda alla pagina di documentazione Proxmox, sezione "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.		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.

			<div class="mw-translate-fuzzy">
	Once the VM is connected to the network, you can activate and configure it through the web interface (initially on port 10080, and after installing the phone firmware on the standard port 80).		Once the VM is connected to the network, you can activate and configure it through the web interface (initially on port 10080, and after installing the phone firmware on the standard port 80).
			</div>

	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.		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.

S.vistoli il 08:55, 5 nov 2018

2018-11-05T08:55:15Z

← Versione meno recente		Versione delle 08:55, 5 nov 2018
Riga 31:		Riga 31:
	Once the VM is connected to the network, you can activate and configure it through the web interface (initially on port 10080, and after installing the phone firmware on the standard port 80).		Once the VM is connected to the network, you can activate and configure it through the web interface (initially on port 10080, and after installing the phone firmware on the standard port 80).

	The VM must be able to reach in HTTP our license and update servers (license.kalliopepbx.it e updates.kalliopepbx.it), which currently both resolve the IP address 77.72.27.4.		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.

Silvia: Creata pagina con "The VM must be able to reach in HTTP our license and update servers (license.kalliopepbx.it e updates.kalliopepbx.it), which currently both resolve the IP address 77.72.27.4."

2018-02-21T09:54:17Z

Creata pagina con "The VM must be able to reach in HTTP our license and update servers (license.kalliopepbx.it e updates.kalliopepbx.it), which currently both resolve the IP address 77.72.27.4."

← Versione meno recente		Versione delle 09:54, 21 feb 2018
Riga 31:		Riga 31:
	Once the VM is connected to the network, you can activate and configure it through the web interface (initially on port 10080, and after installing the phone firmware on the standard port 80).		Once the VM is connected to the network, you can activate and configure it through the web interface (initially on port 10080, and after installing the phone firmware on the standard port 80).

	~~E' necessario che la~~ VM ~~abbia la raggiungibilità~~ in ~~HTTPS dei nostri server di licenza e di aggiornamenti~~ (license.kalliopepbx.it e updates.kalliopepbx.it) ~~che attualmente risolvono entrambi l'~~IP 77.72.27.4		The VM must be able to reach in HTTP our license and update servers (license.kalliopepbx.it e updates.kalliopepbx.it), which currently both resolve the IP address 77.72.27.4.

Silvia: Creata pagina con "Once the VM is connected to the network, you can activate and configure it through the web interface (initially on port 10080, and after installing the phone firmware on the s..."

2018-02-21T09:54:05Z

Creata pagina con "Once the VM is connected to the network, you can activate and configure it through the web interface (initially on port 10080, and after installing the phone firmware on the s..."

← Versione meno recente		Versione delle 09:54, 21 feb 2018
Riga 29:		Riga 29:
	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.		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.

	~~Una volta in rete~~, ~~l'attivazione e la configurazione avviene tramite interfaccia~~ web (~~inizialmente sulla porta~~ 10080, ~~e dopo l'installazione del~~ firmware ~~telefonico sulla porta~~ standard 80).		Once the VM is connected to the network, you can activate and configure it through the web interface (initially on port 10080, and after installing the phone firmware on the standard port 80).

	E' necessario che la VM abbia la raggiungibilità in HTTPS dei nostri server di licenza e di aggiornamenti (license.kalliopepbx.it e updates.kalliopepbx.it) che attualmente risolvono entrambi l'IP 77.72.27.4		E' necessario che la VM abbia la raggiungibilità in HTTPS dei nostri server di licenza e di aggiornamenti (license.kalliopepbx.it e updates.kalliopepbx.it) che attualmente risolvono entrambi l'IP 77.72.27.4

Silvia: Creata pagina con "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."

2018-02-21T09:53:56Z

Creata pagina con "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."

← Versione meno recente		Versione delle 09:53, 21 feb 2018
Riga 27:		Riga 27:


	~~A questo punto si opera come per le altre VM~~, ~~ossia si accede con credenziali~~ manager/manager, ~~e un~~ wizard ~~permette di effettuare le impostazioni di rete~~.		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.

	Una volta in rete, l'attivazione e la configurazione avviene tramite interfaccia web (inizialmente sulla porta 10080, e dopo l'installazione del firmware telefonico sulla porta standard 80).		Una volta in rete, l'attivazione e la configurazione avviene tramite interfaccia web (inizialmente sulla porta 10080, e dopo l'installazione del firmware telefonico sulla porta standard 80).

	E' necessario che la VM abbia la raggiungibilità in HTTPS dei nostri server di licenza e di aggiornamenti (license.kalliopepbx.it e updates.kalliopepbx.it) che attualmente risolvono entrambi l'IP 77.72.27.4		E' necessario che la VM abbia la raggiungibilità in HTTPS dei nostri server di licenza e di aggiornamenti (license.kalliopepbx.it e updates.kalliopepbx.it) che attualmente risolvono entrambi l'IP 77.72.27.4

Silvia: Creata pagina con "'''N.B.''': before booting the machine, you must edit the VM settings to enable the "KVM Hardware acceleration" flag, otherwise performance will be slow."

2018-02-21T09:53:37Z

Creata pagina con "'''N.B.''': before booting the machine, you must edit the VM settings to enable the "KVM Hardware acceleration" flag, otherwise performance will be slow."

← Versione meno recente		Versione delle 09:53, 21 feb 2018
Riga 24:		Riga 24:
	The VM is now operational and you can boot it and access the console to configure the network address.		The VM is now operational and you can boot it and access the console to configure the network address.

	'''~~NOTA IMPORTANTE~~''': ~~prima di avviare la macchina virtuale è necessario modificare le impostazioni della~~ VM ~~abilitando il flag~~ "KVM Hardware acceleration" , ~~altrimenti le prestazioni sono estremamente rallentate~~.		'''N.B.''': before booting the machine, you must edit the VM settings to enable the "KVM Hardware acceleration" flag, otherwise performance will be slow.

Silvia: Creata pagina con "The VM is now operational and you can boot it and access the console to configure the network address."

2018-02-21T09:53:13Z

Creata pagina con "The VM is now operational and you can boot it and access the console to configure the network address."

← Versione meno recente		Versione delle 09:53, 21 feb 2018
Riga 22:		Riga 22:
	where <nnn> is the ID you wish to assign to the VM (it must not be assigned to any other VMs). This step can be performed through the Proxmox GUI.		where <nnn> is the ID you wish to assign to the VM (it must not be assigned to any other VMs). This step can be performed through the Proxmox GUI.

	~~A questo punto la~~ VM ~~è operativa, è possibile avviarla e accedere alla~~ console ~~per effettuare la configurazione dell'indirizzo di rete~~.		The VM is now operational and you can boot it and access the console to configure the network address.

	'''NOTA IMPORTANTE''': prima di avviare la macchina virtuale è necessario modificare le impostazioni della VM abilitando il flag "KVM Hardware acceleration" , altrimenti le prestazioni sono estremamente rallentate.		'''NOTA IMPORTANTE''': prima di avviare la macchina virtuale è necessario modificare le impostazioni della VM abilitando il flag "KVM Hardware acceleration" , altrimenti le prestazioni sono estremamente rallentate.