Proxmox Virtual Environment - Revision history

Rtjure at 21:31, 17 January 2025

2025-01-17T21:31:54Z

← Older revision		Revision as of 21:31, 17 January 2025
Line 5:		Line 5:
	[[File:Proxmox-VE-8-0-Cluster-Summary.png\|thumb\|Proxmox-VE-8-0-Cluster-Summary]]		[[File:Proxmox-VE-8-0-Cluster-Summary.png\|thumb\|Proxmox-VE-8-0-Cluster-Summary]]

	PVE can manage a ~~so called~~ "data center" as a cluster of machines and storage.		PVE can manage a "data center" as a cluster of machines and storage through a unified Webgui that allows management of the whole cluster through each of the nodes.

	Proxmox VE uses		Proxmox VE uses

Rtjure at 21:27, 17 January 2025

2025-01-17T21:27:48Z

← Older revision		Revision as of 21:27, 17 January 2025
Line 1:		Line 1:
	[https://www.proxmox.com/proxmox-ve {{PAGENAME}}] - shortened ''PVE'' - ([[wikipedia:en:{{PAGENAME}}]]) is a platform for containerization and virtualization. PVE ~~can manage~~ a ~~so called "data center" as~~ a ~~cluster~~ of ~~machines and storage~~. ~~(It supports file systems like~~ [[ZFS]] and [[Ceph]].~~) It is primarily used with a WebGui (~~[[~~wikipedia:en:web user interface\|WUI~~]]~~) but~~ also ~~provides~~ an API~~, editable~~ Configfiles and CLI-Commands. ~~It is open source and is based on~~ [[~~Debian~~]]~~ GNU/Linux (with~~ a ~~customized kernel~~ of ~~[[Ubuntu]])~~.		[https://www.proxmox.com/proxmox-ve {{PAGENAME}}] - shortened ''PVE'' - ([[wikipedia:en:{{PAGENAME}}]]) is a platform for containerization and virtualization.

			PVE is open source and is based on Debian GNU/Linux (with a customized kernel from Ubuntu) and supports a variety of filesystems (e.g.[[ZFS]]) and storage-backends/network-filesystems (e.g.[[Ceph]]). [[Ceph]] can be setup, administrated and monitored through the Webinterface, just as most other functions of PVE. There is also an API and a way to configure PVE through Configfiles and CLI-Commands.

			[[File:Proxmox-VE-8-0-Cluster-Summary.png\|thumb\|Proxmox-VE-8-0-Cluster-Summary]]

			PVE can manage a so called "data center" as a cluster of machines and storage.

	Proxmox VE uses		Proxmox VE uses

Rtjure at 19:10, 15 January 2025

2025-01-15T19:10:31Z

← Older revision		Revision as of 19:10, 15 January 2025
Line 1:		Line 1:
	[https://www.proxmox.com/proxmox-ve {{PAGENAME}}] - shortened ''PVE'' - ([[wikipedia:en:{{PAGENAME}}]]) is a platform for containerization and virtualization. PVE can manage a so called "data center" as a cluster of machines and storage. (It supports file systems like [[ZFS]] and [[Ceph]].) ~~Mostly it can be~~ used with a [[wikipedia:en:web user interface\|WUI]]. It is open source and is based on [[Debian]] GNU/Linux (with a customized kernel of [[Ubuntu]]).		[https://www.proxmox.com/proxmox-ve {{PAGENAME}}] - shortened ''PVE'' - ([[wikipedia:en:{{PAGENAME}}]]) is a platform for containerization and virtualization. PVE can manage a so called "data center" as a cluster of machines and storage. (It supports file systems like [[ZFS]] and [[Ceph]].) It is primarily used with a WebGui ([[wikipedia:en:web user interface\|WUI]]) but also provides an API, editable Configfiles and CLI-Commands. It is open source and is based on [[Debian]] GNU/Linux (with a customized kernel of [[Ubuntu]]).

	Proxmox VE uses		Proxmox VE uses

Mic92: enable syntax highlighting

2025-01-15T18:42:23Z

enable syntax highlighting

← Older revision		Revision as of 18:42, 15 January 2025
Line 102:		Line 102:

	The template built above without any options does not come with <code>/etc/nixos/configuration.nix</code>. A minimal working example is presented below. Be sure to run <code>nix-channel --update</code>, reboot the container running before <code>nixos-rebuild switch</code>.		The template built above without any options does not come with <code>/etc/nixos/configuration.nix</code>. A minimal working example is presented below. Be sure to run <code>nix-channel --update</code>, reboot the container running before <code>nixos-rebuild switch</code>.
	<~~pre~~>		<syntaxHighlight lang=nix>
	{ pkgs, modulesPath, ... }:		{ pkgs, modulesPath, ... }:

Line 114:		Line 114:
	];		];
	}		}
	</~~pre~~>		</syntaxHighlight>

	=== LXC Console ===		=== LXC Console ===

Mic92: add proxmox-nixos

2025-01-15T18:21:19Z

add proxmox-nixos

← Older revision		Revision as of 18:21, 15 January 2025
Line 9:		Line 9:
	The instructions should work for PVE 7.2 and later with NixOS 22.05 and later.		The instructions should work for PVE 7.2 and later with NixOS 22.05 and later.
	</blockquote>		</blockquote>

			== Deploying Proxmox with NixOS ==

			The [https://github.com/SaumonNet/proxmox-nixos/ proxmox-nixos] project allows to run the Proxmox Hypervisor on top of NixOS.

	== KVM ==		== KVM ==

Granddave: Reorder list of PVE uses to match order of sections

2024-12-14T15:39:28Z

Reorder list of PVE uses to match order of sections

← Older revision		Revision as of 15:39, 14 December 2024
Line 1:		Line 1:
	[https://www.proxmox.com/proxmox-ve {{PAGENAME}}] - shortened ''PVE'' - ([[wikipedia:en:{{PAGENAME}}]]) is a platform for containerization and virtualization. PVE can manage a so called "data center" as a cluster of machines and storage. (It supports file systems like [[ZFS]] and [[Ceph]].) Mostly it can be used with a [[wikipedia:en:web user interface\|WUI]]. It is open source and is based on [[Debian]] GNU/Linux (with a customized kernel of [[Ubuntu]]).		[https://www.proxmox.com/proxmox-ve {{PAGENAME}}] - shortened ''PVE'' - ([[wikipedia:en:{{PAGENAME}}]]) is a platform for containerization and virtualization. PVE can manage a so called "data center" as a cluster of machines and storage. (It supports file systems like [[ZFS]] and [[Ceph]].) Mostly it can be used with a [[wikipedia:en:web user interface\|WUI]]. It is open source and is based on [[Debian]] GNU/Linux (with a customized kernel of [[Ubuntu]]).

	~~PVE~~ uses		Proxmox VE uses
	* [[#~~LXC~~]] for ~~containerization~~ and		* [[#KVM]] for virtualization and
	* [[#~~KVM~~]] for ~~virtualization~~.		* [[#LXC]] for containerization.
	NixOS runs on both.		NixOS runs on both.

Granddave: Capitalize Proxmox, and add "VE" in some fitting places

2024-12-14T15:38:28Z

Capitalize Proxmox, and add "VE" in some fitting places

← Older revision		Revision as of 15:38, 14 December 2024
Line 14:		Line 14:
	It is possible to generate generic qcow2 images and attach them to VMs with <code>qm importdisk</code> as shown [https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE#Importing_to_Proxmox_VE here].		It is possible to generate generic qcow2 images and attach them to VMs with <code>qm importdisk</code> as shown [https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE#Importing_to_Proxmox_VE here].

	A better option is to generate a VMA image that can be imported as a VM on ~~proxmox~~. With this method, many VM configuration options such as CPU, memory, network interfaces, and serial terminals can be specified in nix instead of manually setting them on the ~~proxmox~~ UI.		A better option is to generate a VMA image that can be imported as a VM on Proxmox VE. With this method, many VM configuration options such as CPU, memory, network interfaces, and serial terminals can be specified in nix instead of manually setting them on the Proxmox UI.

	=== Generating VMA ===		=== Generating VMA ===
Line 26:		Line 26:
	Pass additional nix configuration to the template with <code>--configuration filename.nix</code>. In addition to NixOS module options, proxmox-specific options present in [https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/virtualisation/proxmox-image.nix nixos/modules/virtualisation/proxmox-image.nix] can be used to set core, memory, disk and other VM hardware options.		Pass additional nix configuration to the template with <code>--configuration filename.nix</code>. In addition to NixOS module options, proxmox-specific options present in [https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/virtualisation/proxmox-image.nix nixos/modules/virtualisation/proxmox-image.nix] can be used to set core, memory, disk and other VM hardware options.

	=== Deploying on ~~proxmox~~ ===		=== Deploying on Proxmox VE ===

	The generated vma.zst file can be copied to <code>/var/lib/vz/dump/</code> (or any other configured VM dump storage path). A new VM can be spun up from it either using the GUI or the CLI:		The generated vma.zst file can be copied to <code>/var/lib/vz/dump/</code> (or any other configured VM dump storage path). A new VM can be spun up from it either using the GUI or the CLI:
Line 34:		Line 34:
	</pre>		</pre>
	<blockquote>		<blockquote>
	note: the MAC address of net0 defaults to <code>00:00:00:00:00:00</code>. This must either be overridden through <code>proxmox.qemuConf.net0</code>, or the <code>unique</code> attribute must be set to true when importing the image on ~~proxmox~~.		note: the MAC address of net0 defaults to <code>00:00:00:00:00:00</code>. This must either be overridden through <code>proxmox.qemuConf.net0</code>, or the <code>unique</code> attribute must be set to true when importing the image on Proxmox.
	</blockquote>		</blockquote>
	By default, the generated image is set up to expose a serial terminal interface for ease of access.		By default, the generated image is set up to expose a serial terminal interface for ease of access.
Line 87:		Line 87:
	=== Network configuration ===		=== Network configuration ===

	The proxmox LXC template uses systemd-networkd by default to allow network configuration by ~~proxmox~~. <code>proxmoxLXC.manageNetwork</code> can be set to true to disable this.		The proxmox LXC template uses systemd-networkd by default to allow network configuration by Proxmox. <code>proxmoxLXC.manageNetwork</code> can be set to true to disable this.

	=== ~~deploying~~ on ~~proxmox~~ ===		=== Deploying on Proxmox VE ===

	Copy the tarball to ~~proxmox~~, then create a new LXC with this template through the web UI or the CLI. The “nesting” feature needs to be enabled. Newer versions of ~~proxmox~~ will have it enabled by default.		Copy the tarball to Proxmox, then create a new LXC with this template through the web UI or the CLI. The “nesting” feature needs to be enabled. Newer versions of Proxmox will have it enabled by default.

	As of now, not all of the configuration options on the web UI work for ~~proxmox~~ LXCs. Network configuration and adding SSH keys to root user work, while setting a password for the root user and setting hostname don’t.		As of now, not all of the configuration options on the web UI work for Proxmox LXCs. Network configuration and adding SSH keys to root user work, while setting a password for the root user and setting hostname don’t.

	It is suggested to set a root password within the container on first boot.		It is suggested to set a root password within the container on first boot.

Klinger: Category:VirtualizationCategory:Software

2024-04-19T17:33:46Z

Category:Virtualization Category:Software

← Older revision		Revision as of 17:33, 19 April 2024
Line 130:		Line 130:
	== References ==		== References ==
	<references />		<references />


			[[Category:Software]]
			[[Category:Virtualization]]

imported>Lindenk: fixed typo

2024-02-11T15:48:35Z

fixed typo

← Older revision		Revision as of 15:48, 11 February 2024
Line 14:		Line 14:
	It is possible to generate generic qcow2 images and attach them to VMs with <code>qm importdisk</code> as shown [https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE#Importing_to_Proxmox_VE here].		It is possible to generate generic qcow2 images and attach them to VMs with <code>qm importdisk</code> as shown [https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE#Importing_to_Proxmox_VE here].

	A better option is to generate a VMA image that can be imported as a VM on proxmox. With this method, many VM configuration options such as CPU, memory, ~~netowrk~~ interfaces, and serial terminals can be specified in nix instead of manually setting them on the proxmox UI.		A better option is to generate a VMA image that can be imported as a VM on proxmox. With this method, many VM configuration options such as CPU, memory, network interfaces, and serial terminals can be specified in nix instead of manually setting them on the proxmox UI.

	=== Generating VMA ===		=== Generating VMA ===

imported>Bradfitz: typo fixes

2023-11-26T03:35:34Z

typo fixes

← Older revision		Revision as of 03:35, 26 November 2023
Line 34:		Line 34:
	</pre>		</pre>
	<blockquote>		<blockquote>
	note: the MAC address of net0 defaults to <code>00:00:00:00:00:00</code>. This must either be ~~overriden thruogh~~ <code>proxmox.qemuConf.net0</code>, or the <code>unique</code> attribute must be set to true when importing the image on proxmox.		note: the MAC address of net0 defaults to <code>00:00:00:00:00:00</code>. This must either be overridden through <code>proxmox.qemuConf.net0</code>, or the <code>unique</code> attribute must be set to true when importing the image on proxmox.
	</blockquote>		</blockquote>
	By default, the generated image is set up to expose a serial terminal interface for ease of access.		By default, the generated image is set up to expose a serial terminal interface for ease of access.