]> git.proxmox.com Git - pve-docs.git/blame_incremental - pve-installation.adoc
fix #3884: Add section for kernel samepage merging
[pve-docs.git] / pve-installation.adoc
... / ...
CommitLineData
1[[chapter_installation]]
2Installing {pve}
3================
4ifndef::manvolnum[]
5:pve-toplevel:
6endif::manvolnum[]
7ifdef::wiki[]
8:title: Installation
9endif::wiki[]
10
11{pve} is based on Debian. This is why the install disk images (ISO files)
12provided by Proxmox include a complete Debian system as well as all necessary
13{pve} packages.
14
15TIP: See the xref:faq-support-table[support table in the FAQ] for the
16relationship between {pve} releases and Debian releases.
17
18The installer will guide you through the setup, allowing you to partition the
19local disk(s), apply basic system configurations (for example, timezone,
20language, network) and install all required packages. This process should not
21take more than a few minutes. Installing with the provided ISO is the
22recommended method for new and existing users.
23
24Alternatively, {pve} can be installed on top of an existing Debian system. This
25option is only recommended for advanced users because detailed knowledge about
26{pve} is required.
27
28ifndef::wiki[]
29
30include::pve-system-requirements.adoc[]
31
32include::pve-installation-media.adoc[]
33
34endif::wiki[]
35
36
37[[installation_installer]]
38Using the {pve} Installer
39-------------------------
40
41The installer ISO image includes the following:
42
43* Complete operating system (Debian Linux, 64-bit)
44
45* The {pve} installer, which partitions the local disk(s) with ext4, XFS,
46 BTRFS (technology preview), or ZFS and installs the operating system.
47
48* {pve} Linux kernel with KVM and LXC support
49
50* Complete toolset for administering virtual machines, containers, the host
51 system, clusters and all necessary resources
52
53* Web-based management interface
54
55NOTE: All existing data on the for installation selected drives will be removed
56during the installation process. The installer does not add boot menu entries
57for other operating systems.
58
59Please insert the xref:installation_prepare_media[prepared installation media]
60(for example, USB flash drive or CD-ROM) and boot from it.
61
62TIP: Make sure that booting from the installation medium (for example, USB) is
63enabled in your servers firmware settings.
64
65[thumbnail="screenshot/pve-grub-menu.png"]
66
67After choosing the correct entry (e.g. Boot from USB) the {pve} menu will be
68displayed and one of the following options can be selected:
69
70Install {pve}::
71
72Starts the normal installation.
73
74TIP: It's possible to use the installation wizard with a keyboard only. Buttons
75can be clicked by pressing the `ALT` key combined with the underlined character
76from the respective button. For example, `ALT + N` to press a `Next` button.
77
78Install {pve} (Debug mode)::
79
80Starts the installation in debug mode. A console will be opened at several
81installation steps. This helps to debug the situation if something goes wrong.
82To exit a debug console, press `CTRL-D`. This option can be used to boot a live
83system with all basic tools available. You can use it, for example, to
84xref:chapter_zfs[repair a degraded ZFS 'rpool'] or fix the
85xref:sysboot[bootloader] for an existing {pve} setup.
86
87Rescue Boot::
88
89With this option you can boot an existing installation. It searches all attached
90hard disks. If it finds an existing installation, it boots directly into that
91disk using the Linux kernel from the ISO. This can be useful if there are
92problems with the boot block (grub) or the BIOS is unable to read the boot block
93from the disk.
94
95Test Memory::
96
97Runs `memtest86+`. This is useful to check if the memory is functional and free
98of errors.
99
100[thumbnail="screenshot/pve-select-target-disk.png"]
101
102After selecting *Install {pve}* and accepting the EULA, the prompt to select the
103target hard disk(s) will appear. The `Options` button opens the dialog to select
104the target file system.
105
106The default file system is `ext4`. The Logical Volume Manager (LVM) is used when
107`ext4` or `xfs` is selected. Additional options to restrict LVM space
108can also be set (see <<advanced_lvm_options,below>>).
109
110{pve} can be installed on ZFS. As ZFS offers several software RAID levels, this
111is an option for systems that don't have a hardware RAID controller. The target
112disks must be selected in the `Options` dialog. More ZFS specific settings can
113be changed under `Advanced Options` (see <<advanced_zfs_options,below>>).
114
115WARNING: ZFS on top of any hardware RAID is not supported and can result in data
116loss.
117
118[thumbnail="screenshot/pve-select-location.png", float="left"]
119
120The next page asks for basic configuration options like the location, the time
121zone, and keyboard layout. The location is used to select a download server
122close by to speed up updates. The installer usually auto-detects these settings.
123They only need to be changed in the rare case that auto detection fails or a
124different keyboard layout should be used.
125
126[thumbnail="screenshot/pve-set-password.png"]
127
128Next the password of the superuser (root) and an email address needs to be
129specified. The password must consist of at least 5 characters. It's highly
130recommended to use a stronger password. Some guidelines are:
131
132- Use a minimum password length of 12 to 14 characters.
133
134- Include lowercase and uppercase alphabetic characters, numbers, and symbols.
135
136- Avoid character repetition, keyboard patterns, common dictionary words,
137 letter or number sequences, usernames, relative or pet names, romantic links
138 (current or past), and biographical information (for example ID numbers,
139 ancestors' names or dates).
140
141The email address is used to send notifications to the system administrator.
142For example:
143
144- Information about available package updates.
145
146- Error messages from periodic CRON jobs.
147
148[thumbnail="screenshot/pve-setup-network.png"]
149
150The last step is the network configuration. Please note that during installation
151you can either use an IPv4 or IPv6 address, but not both. To configure a dual
152stack node, add additional IP addresses after the installation.
153
154[thumbnail="screenshot/pve-installation.png", float="left"]
155
156The next step shows a summary of the previously selected options. Re-check every
157setting and use the `Previous` button if a setting needs to be changed. To
158accept, press `Install`. The installation starts to format disks and copies
159packages to the target. Please wait until this step has finished; then remove
160the installation medium and restart your system.
161
162[thumbnail="screenshot/pve-install-summary.png"]
163
164If the installation failed check out specific errors on the second TTY
165(`CTRL + ALT + F2'), ensure that the systems meets the
166xref:install_minimal_requirements[minimum requirements]. If the installation
167is still not working look at the xref:getting_help[how to get help chapter].
168
169Further configuration is done via the Proxmox web interface. Point your browser
170to the IP address given during installation (https://youripaddress:8006).
171
172NOTE: Default login is "root" (realm 'PAM') and the root password is defined
173during the installation process.
174
175[[advanced_lvm_options]]
176Advanced LVM Configuration Options
177~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
178
179The installer creates a Volume Group (VG) called `pve`, and additional Logical
180Volumes (LVs) called `root`, `data`, and `swap`. To control the size of these
181volumes use:
182
183`hdsize`::
184
185Defines the total hard disk size to be used. This way you can reserve free space
186on the hard disk for further partitioning (for example for an additional PV and
187VG on the same hard disk that can be used for LVM storage).
188
189`swapsize`::
190
191Defines the size of the `swap` volume. The default is the size of the installed
192memory, minimum 4 GB and maximum 8 GB. The resulting value cannot be greater
193than `hdsize/8`.
194+
195NOTE: If set to `0`, no `swap` volume will be created.
196
197`maxroot`::
198
199Defines the maximum size of the `root` volume, which stores the operation
200system. The maximum limit of the `root` volume size is `hdsize/4`.
201
202`maxvz`::
203
204Defines the maximum size of the `data` volume. The actual size of the `data`
205volume is:
206+
207`datasize = hdsize - rootsize - swapsize - minfree`
208+
209Where `datasize` cannot be bigger than `maxvz`.
210+
211NOTE: In case of LVM thin, the `data` pool will only be created if `datasize` is
212bigger than 4GB.
213+
214NOTE: If set to `0`, no `data` volume will be created and the storage
215configuration will be adapted accordingly.
216
217`minfree`::
218
219Defines the amount of free space left in the LVM volume group `pve`. With more
220than 128GB storage available the default is 16GB, else `hdsize/8` will be used.
221+
222NOTE: LVM requires free space in the VG for snapshot creation (not required for
223lvmthin snapshots).
224
225[[advanced_zfs_options]]
226Advanced ZFS Configuration Options
227~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
228The installer creates the ZFS pool `rpool`. No swap space is created but you can
229reserve some unpartitioned space on the install disks for swap. You can also
230create a swap zvol after the installation, although this can lead to problems.
231(see <<zfs_swap,ZFS swap notes>>).
232
233`ashift`::
234
235Defines the `ashift` value for the created pool. The `ashift` needs to be set at
236least to the sector-size of the underlying disks (2 to the power of `ashift` is
237the sector-size), or any disk which might be put in the pool (for example the
238replacement of a defective disk).
239
240`compress`::
241
242Defines whether compression is enabled for `rpool`.
243
244`checksum`::
245
246Defines which checksumming algorithm should be used for `rpool`.
247
248`copies`::
249
250Defines the `copies` parameter for `rpool`. Check the `zfs(8)` manpage for the
251semantics, and why this does not replace redundancy on disk-level.
252
253`hdsize`::
254
255Defines the total hard disk size to be used. This is useful to save free space
256on the hard disk(s) for further partitioning (for example to create a
257swap-partition). `hdsize` is only honored for bootable disks, that is only the
258first disk or mirror for RAID0, RAID1 or RAID10, and all disks in RAID-Z[123].
259
260
261ZFS Performance Tips
262~~~~~~~~~~~~~~~~~~~~
263
264ZFS works best with a lot of memory. If you intend to use ZFS make sure to have
265enough RAM available for it. A good calculation is 4GB plus 1GB RAM for each TB
266RAW disk space.
267
268ZFS can use a dedicated drive as write cache, called the ZFS Intent Log (ZIL).
269Use a fast drive (SSD) for it. It can be added after installation with the
270following command:
271
272----
273# zpool add <pool-name> log </dev/path_to_fast_ssd>
274----
275
276ifndef::wiki[]
277
278Install {pve} on Debian
279-----------------------
280
281{pve} ships as a set of Debian packages and can be installed on to of a standard
282Debian installation.
283xref:sysadmin_package_repositories[After configuring the repositories] you need
284to run the following commands:
285
286----
287# apt-get update
288# apt-get install proxmox-ve
289----
290
291Installing on top of an existing Debian installation looks easy, but it presumes
292that the base system has been installed correctly and that you know how you want
293to configure and use the local storage. You also need to configure the network
294manually.
295
296In general, this is not trivial, especially when LVM or ZFS is used.
297
298A detailed step by step how-to can be found on the
299{webwiki-url}Install_Proxmox_VE_on_Debian_Buster[wiki].
300
301
302endif::wiki[]
303
304ifdef::wiki[]
305
306Video Tutorials
307---------------
308
309* List of all official tutorials on our
310 https://www.youtube.com/proxmoxve[{pve} YouTube Channel]
311
312* Tutorials in Spanish language on
313 https://www.youtube.com/playlist?list=PLUULBIhA5QDBdNf1pcTZ5UXhek63Fij8z[ITexperts.es
314 YouTube Play List]
315
316
317See Also
318--------
319
320* link:/wiki/Prepare_Installation_Media[Prepare Installation Media]
321
322* link:/wiki/Install_Proxmox_VE_on_Debian_Buster[Install Proxmox VE on Debian Buster]
323
324* link:/wiki/System_Requirements[System Requirements]
325
326* link:/wiki/Package_Repositories[Package Repositories]
327
328* link:/wiki/Host_System_Administration[Host System Administration]
329
330* link:/wiki/Network_Configuration[Network Configuration]
331
332* link:/wiki/Installation:_Tips_and_Tricks[Installation: Tips and Tricks]
333
334endif::wiki[]