Proxmox - Revision history

M: /* Changing VM Memory allocation */

2025-06-28T16:02:17Z

Changing VM Memory allocation

← Older revision		Revision as of 16:02, 28 June 2025
Line 105:		Line 105:

	== Changing VM Memory allocation ==		== Changing VM Memory allocation ==
	I have 128GB of memory and it is slightly overallocated, which is not great. Leads to [[#Swappiness]]. If a VM needs more memory, try to steal it from another before increasing, if you can!		I have 128GB of memory and it is slightly overallocated, which is not great. Leads to [[Proxmox#Swappiness\|Swappiness]]. If a VM needs more memory, try to steal it from another before increasing, if you can!

	== VM remote desktop display ==		== VM remote desktop display ==

M: /* Changing VM CPU allocation */

2025-06-28T16:01:26Z

Changing VM CPU allocation

← Older revision		Revision as of 16:01, 28 June 2025
Line 103:		Line 103:
	* Adjust core count. Overallocation is a very good idea. CPU cores will be used only as threads need them. I've read that some shops successfully overallocate by a factor of 20:1. With our 12 Ryzen 9 cores, that means we would allocate 120 total cores to our VMs(!). Don't do that, ha.		* Adjust core count. Overallocation is a very good idea. CPU cores will be used only as threads need them. I've read that some shops successfully overallocate by a factor of 20:1. With our 12 Ryzen 9 cores, that means we would allocate 120 total cores to our VMs(!). Don't do that, ha.
	* Stick with 1 socket (that's just for sizing to match any paid licensing)		* Stick with 1 socket (that's just for sizing to match any paid licensing)

			== Changing VM Memory allocation ==
			I have 128GB of memory and it is slightly overallocated, which is not great. Leads to [[#Swappiness]]. If a VM needs more memory, try to steal it from another before increasing, if you can!

	== VM remote desktop display ==		== VM remote desktop display ==

M: /* Proxmox config */

2025-06-28T15:56:16Z

Proxmox config

@@ Line 114: / Line 114: @@
 == Proxmox config ==
 There is a LOT of configuration.  After getting it all set, I copied it all out, following [https://forum.proxmox.com/threads/how-to-backup-proxmox-configuration-files.67789/ some forum suggestion].  Try to keep it updated!
@@ Line 137: / Line 139: @@
 Remember to set Content Type to include the things you will place there.
-=== Backups ===
+=== Swappiness ===
 * I am backing up to softraid/backup on bitpost.  See the bitpost-backup SMB share under the melange tree in the lefthand bar.

M: /* Samba */

2024-10-15T18:10:58Z

Samba

← Older revision		Revision as of 18:10, 15 October 2024
Line 176:		Line 176:
	Samba is supposed to work so you don't have to touch it, but when it goes down it's not easy to restart. I'm still trying to figure out how to restart samba, short of restarting the box.		Samba is supposed to work so you don't have to touch it, but when it goes down it's not easy to restart. I'm still trying to figure out how to restart samba, short of restarting the box.

	I think bitpost.com losing its DNS may cause a real problem for proxmox. Prolly good to follow this advice:		I think bitpost.com losing its DNS may cause a real problem for proxmox. Prolly good to follow this advice. I use "bitpost" with the LAN IP in /etc/hosts:

	* From the [https://melange:8006/pve-docs/chapter-pvesm.html#storage_cifs manual]: To avoid DNS lookup delays, it is usually preferable to use an IP address instead of a DNS name - unless you have a very reliable DNS server, or list the server in the local /etc/hosts file.		* From the [https://melange:8006/pve-docs/chapter-pvesm.html#storage_cifs manual]: To avoid DNS lookup delays, it is usually preferable to use an IP address instead of a DNS name - unless you have a very reliable DNS server, or list the server in the local /etc/hosts file.

M at 18:09, 15 October 2024

2024-10-15T18:09:42Z

← Older revision		Revision as of 18:09, 15 October 2024
Line 171:		Line 171:
	ssh melange		ssh melange
	sudo apt-get --allow-releaseinfo-change update		sudo apt-get --allow-releaseinfo-change update

			== Troubleshooting ==
			=== Samba ===
			Samba is supposed to work so you don't have to touch it, but when it goes down it's not easy to restart. I'm still trying to figure out how to restart samba, short of restarting the box.

			I think bitpost.com losing its DNS may cause a real problem for proxmox. Prolly good to follow this advice:

			* From the [https://melange:8006/pve-docs/chapter-pvesm.html#storage_cifs manual]: To avoid DNS lookup delays, it is usually preferable to use an IP address instead of a DNS name - unless you have a very reliable DNS server, or list the server in the local /etc/hosts file.

	== Proxmox Installation ==		== Proxmox Installation ==

M at 12:49, 28 August 2024

2024-08-28T12:49:37Z

← Older revision		Revision as of 12:49, 28 August 2024
Line 12:		Line 12:
	*** Proxmox > (VM) > hardware > DVD > remove		*** Proxmox > (VM) > hardware > DVD > remove
	*** Proxmox > (VM) > shutdown, then start		*** Proxmox > (VM) > shutdown, then start

			== Proxmox update ==
			See [[Melange#Upgrade\|melange upgrade notes]].

			== Creating and cloning VMs ==
			[[Melange]] has specific instructions here:

			[[Add a new VM to melange]] - [[Clone a melange VM]]

	== Changing VM disk size ==		== Changing VM disk size ==
Line 163:		Line 171:
	ssh melange		ssh melange
	sudo apt-get --allow-releaseinfo-change update		sudo apt-get --allow-releaseinfo-change update

	~~== Proxmox update ==~~
	~~See [[Melange#Upgrade\|melange upgrade notes]].~~

	== Proxmox Installation ==		== Proxmox Installation ==

M: /* VM remote desktop display */

2024-06-16T23:10:28Z

VM remote desktop display

← Older revision		Revision as of 23:10, 16 June 2024
Line 97:		Line 97:

	== VM remote desktop display ==		== VM remote desktop display ==
	I'm using [[SPICE]] for a full responsive 4k UI on other thin(ner) clients.		I'm using [[SPICE]] for a full responsive 4k UI on other thin(ner) clients. BUT... use the VirtIO-GPU Display driver! (NOT SPICE)

			=== SPICE ===

	NOTE that the qmu driver CRASHES even after fixing the memory allocated (see below). Instead, use the VirtIO-GPU Display driver, which works fine with SPICE,		NOTE that the qmu driver CRASHES even after fixing the memory allocated (see below). Instead, use the VirtIO-GPU Display driver, which works fine with SPICE,

	~~=== SPICE memory ===~~		When using qmu driver, using vscode on abtdev1 on a second desktop would crash the VM with SPICE memory set to 36(MB). I bumped it to 80 and it lasted a bit longer. It apparently needs more when you use more desktops, in both Windows and linux, according to [https://melange:8006/pve-docs/chapter-qm.html#qm_display this]. But ... jsut don't use qmu/SPICE display!
	~~Using~~ vscode on abtdev1 on a second desktop would crash the VM with SPICE memory set to 36(MB). I bumped it to 80 and it ~~seems okay~~. It apparently needs more when you use more desktops, in both Windows and linux, according to [https://melange:8006/pve-docs/chapter-qm.html#qm_display this].

	== Proxmox config ==		== Proxmox config ==

M: /* VM remote desktop display */

2024-06-16T23:08:19Z

VM remote desktop display

← Older revision		Revision as of 23:08, 16 June 2024
Line 98:		Line 98:
	== VM remote desktop display ==		== VM remote desktop display ==
	I'm using [[SPICE]] for a full responsive 4k UI on other thin(ner) clients.		I'm using [[SPICE]] for a full responsive 4k UI on other thin(ner) clients.

			NOTE that the qmu driver CRASHES even after fixing the memory allocated (see below). Instead, use the VirtIO-GPU Display driver, which works fine with SPICE,

	=== SPICE memory ===		=== SPICE memory ===

M: /* Mac */

2024-03-24T23:31:57Z

Mac

← Older revision		Revision as of 23:31, 24 March 2024
Line 39:		Line 39:
	==== Mac ====		==== Mac ====
	For a macOS VM, thenickdude has [https://www.nicksherlock.com/2021/12/expanding-the-disk-of-your-proxmox-macos-vm/ notes].		For a macOS VM, thenickdude has [https://www.nicksherlock.com/2021/12/expanding-the-disk-of-your-proxmox-macos-vm/ notes].

			* In proxmox, stop the VM, find the hardware disk and do a Disk operation to increase the size, and restart the VM
			* Fix it up in an OSX terminal:
			diskutil list
			# fix the partition
			diskutil repairDisk disk0
			# actually resize the contents
			diskutil apfs resizeContainer disk1 0

	==== Windows ====		==== Windows ====

M: /* Grow */

2023-09-18T19:50:50Z

Grow

← Older revision		Revision as of 19:50, 18 September 2023
Line 19:		Line 19:
	* (VM) > Hardware > Hard Disk > Disk Action > Resize > Add number of GB to increase		* (VM) > Hardware > Hard Disk > Disk Action > Resize > Add number of GB to increase
	* reboot the VM		* reboot the VM
			* Update the OS
			==== Ubuntu ====
	* Update the ubuntu filesystem (if you didn't use LVM (which is basically useless))		* Update the ubuntu filesystem (if you didn't use LVM (which is basically useless))
	sudo parted /dev/sda # use the right one, obv!		sudo parted /dev/sda # use the right one, obv!
Line 25:		Line 27:
	End? 100%		End? 100%
	sudo resize2fs /dev/sda#		sudo resize2fs /dev/sda#

	~~For a macOS VM, thenickdude has [https://www.nicksherlock.com/2021/12/expanding-the-disk-of-your-proxmox-macos-vm/ notes].~~

	If you used LVM in ubuntu (stop doing that!), you have to do all this:		If you used LVM in ubuntu (stop doing that!), you have to do all this:
Line 36:		Line 36:
	lvextend -l +100%FREE /dev/ubuntu-vg/ubuntu-lv # to resize the logical volume		lvextend -l +100%FREE /dev/ubuntu-vg/ubuntu-lv # to resize the logical volume
	resize2fs /dev/ubuntu-vg/ubuntu-lv		resize2fs /dev/ubuntu-vg/ubuntu-lv

			==== Mac ====
			For a macOS VM, thenickdude has [https://www.nicksherlock.com/2021/12/expanding-the-disk-of-your-proxmox-macos-vm/ notes].

			==== Windows ====
			* Use diskpart to remove the restore partition, if it is in the way of expanding the C:\ drive.
			* Use disk manager to expand C:\

	=== Shrink ===		=== Shrink ===