installation experience as the graphical installer, but has generally better
compatibility with very old and very new hardware.
+Install {pve} (Terminal UI, Serial Console)::
+
+Starts the terminal-mode installation wizard, additionally setting up the Linux
+kernel to use the (first) serial port of the machine for in- and output. This
+can be used if the machine is completely headless and only has a serial console
+available.
+
[thumbnail="screenshot/pve-tui-installer.png"]
Both modes use the same code base for the actual installation process to
benefit from more than a decade of bug fixes and ensure feature parity.
TIP: The 'Terminal UI' option can be used in case the graphical installer does
-not work correctly, due to e.g. driver issues.
+not work correctly, due to e.g. driver issues. See also
+xref:nomodeset_kernel_param[adding the `nomodeset` kernel parameter].
Advanced Options: Install {pve} (Graphical, Debug Mode)::
`minfree`::
Defines the amount of free space that should be left in the LVM volume group
-`pmg`. With more than 128GB storage available, the default is 16GB, otherwise
+`pve`. With more than 128GB storage available, the default is 16GB, otherwise
`hdsize/8` will be used.
+
NOTE: LVM requires free space in the VG for snapshot creation (not required for
Defines the `copies` parameter for `rpool`. Check the `zfs(8)` manpage for the
semantics, and why this does not replace redundancy on disk-level.
+`ARC max size`::
+
+Defines the maximum size the ARC can grow to and thus limits the amount of
+memory ZFS will use. See also the section on
+xref:sysadmin_zfs_limit_memory_usage[how to limit ZFS memory usage] for more
+details.
+
`hdsize`::
Defines the total hard disk size to be used. This is useful to save free space
# zpool add <pool-name> log </dev/path_to_fast_ssd>
----
+[[nomodeset_kernel_param]]
Adding the `nomodeset` Kernel Parameter
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Problems may arise on very old or very new hardware due to graphics drivers. If
-the installation hangs during the boot. In that case, you can try adding the
-`nomodeset` parameter. This prevents the Linux kernel from loading any
-graphics drivers and forces it to continue using the BIOS/UEFI-provided
-framebuffer.
+the installation hangs during boot, you can try adding the `nomodeset`
+parameter. This prevents the Linux kernel from loading any graphics drivers and
+forces it to continue using the BIOS/UEFI-provided framebuffer.
On the {pve} bootloader menu, navigate to 'Install {pve} (Terminal UI)' and
press `e` to edit the entry. Using the arrow keys, navigate to the line starting
Then press `Ctrl-X` or `F10` to boot the configuration.
+[[installation_unattended]]
+Unattended Installation
+-----------------------
+
+It is possible to install {pve} automatically in an unattended manner. This
+enables you to fully automate the setup process on bare-metal. Once the
+installation is complete and the host has booted up, automation tools like
+Ansible can be used to further configure the installation.
+
+The necessary options for the installer must be provided in an answer file. This
+file allows the use of filter rules to determine which disks and network cards
+should be used.
+
+To use the automated installation, it is first necessary to prepare an
+installation ISO.
+https://pve.proxmox.com/wiki/Automated_Installation[Visit our wiki] for more
+details and information on the unattended installation.
+
ifndef::wiki[]
Install {pve} on Debian
* link:/wiki/Prepare_Installation_Media[Prepare Installation Media]
-* link:/wiki/Install_Proxmox_VE_on_Debian_Buster[Install Proxmox VE on Debian Buster]
+* link:/wiki/Install_Proxmox_VE_on_Debian_12_Bookworm[Install Proxmox VE on Debian 12 Bookworm]
* link:/wiki/System_Requirements[System Requirements]
projects / pve-docs.git / blobdiff