[pve-docs.git] / pve-installation.adoc
1 Installing Proxmox VE
2 ---------------------
3 include::attributes.txt[]
5 {pve} ships as a set of Debian packages, so you can simply install it
6 on top of a normal Debian installation. After configuring the
7 repositories, you need to run:
9 [source,bash]
10 ----
11 apt-get update
12 apt-get install proxmox-ve
13 ----
15 While this looks easy, it presumes that you have correctly installed
16 the base system, and you know how you want to configure and use the
17 local storage. Network configuration is also completely up to you.
19 In general, this is not trivial, especially when you use LVM or
20 ZFS. This is why we provide an installation CD-ROM for {pve}. That
21 installer just ask you a few questions, then partitions the local
22 disk(s), installs all required packages, and configures the system
23 including a basic network setup. You can get a fully functional system
24 within a few minutes, including the following:
26 * Complete operating system (Debian Linux, 64-bit)
27 * Partition the hard drive with ext4 (alternative ext3 or xfs) or ZFS
28 * {pve} Kernel with LXC and KVM support
29 * Complete toolset
30 * Web based management interface
32 NOTE: By default, the complete server is used and all existing data is
33 removed.
36 Using the {pve} Installation CD-ROM
37 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
39 Please insert the installation CD-ROM, then boot from that
40 drive. Immediately afterwards you can choose the following menu
41 options:
43 Install Proxmox VE::
45 Start normal installation.
47 Install Proxmox VE (Debug mode)::
49 Start installation in debug mode. It opens a shell console at several
50 installation steps, so that you can debug things if something goes
51 wrong. Please press `CTRL-D` to exit those debug consoles and continue
52 installation. This option is mostly for developers and not meant for
53 general use.
55 Rescue Boot::
57 This option allows you to boot an existing installation. It searches
58 all attached hard disks, and if it finds an existing installation,
59 boots directly into that disk using the existing Linux kernel. This
60 can be useful if there are problems with the boot block (grub), or the
61 BIOS is unable to read the boot block from the disk.
63 Test Memory::
65 Runs `memtest86+`. This is useful to check if your memory if
66 functional and error free.
68 You normally select *Install Proxmox VE* to start the installation.
69 After that you get prompted to select the target hard disk(s). The
70 `Options` button lets you select the target file system, which
71 defaults to `ext4`. The installer uses LVM if you select `ext3`,
72 `ext4` or `xfs` as file system, and offers additional option to
73 restrict LVM space (see <<advanced_lvm_options,below>>)
75 If you have more than one disk, you can also use ZFS as file system.
76 ZFS supports several software RAID levels, so this is specially useful
77 if you do not have a hardware RAID controller. The `Options` button
78 lets you select the ZFS RAID level, and you can choose disks there.
80 The next pages just asks for basic configuration options like time
81 zone and keyboard layout. You also need to specify your email address
82 and select a superuser password.
84 The last step is the network configuration. Please note that you can
85 use either IPv4 or IPv6 here, but not both. If you want to configure a
86 dual stack node, you can easily do that after installation.
88 If you press `Next` now, installation starts to format disks, and
89 copies packages to the target. Please wait until that is finished,
90 then reboot the server.
92 Further configuration is done via the Proxmox web interface. Just
93 point your browser to the IP address given during installation
94 (https://youripaddress:8006). {pve} is tested for IE9, Firefox 10
95 and higher, and Google Chrome.
98 [[advanced_lvm_options]]
99 Advanced LVM Configuration Options
100 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
102 The installer creates a Volume Group (VG) called `pve`, and additional
103 Logical Volumes (LVs) called `root`, `data` and `swap`. The size of
104 those volumes can be controlled with:
106 `hdsize`::
108 Defines the total HD size to be used. This way you can save free
109 space on the HD for further partitioning (i.e. for an additional PV
110 and VG on the same hard disk that can be used for LVM storage).
112 `swapsize`::
114 To define the size of the `swap` volume. Default is the same size as
115 installed RAM, with 4GB minimum and `hdsize/8` as maximum.
117 `maxroot`::
119 The `root` volume size. The `root` volume stores the whole operation
120 system.
122 `maxvz`::
124 Define the size of the `data` volume, which is mounted at
125 `/var/lib/vz`.
127 `minfree`::
129 To define the amount of free space left in LVM volume group `pve`.
130 16GB is the default if storage available > 128GB, `hdsize/8` otherwise.
131 +
132 NOTE: LVM requires free space in the VG for snapshot creation (not
133 required for lvmthin snapshots).
136 ZFS Performance Tips
137 ^^^^^^^^^^^^^^^^^^^^
139 ZFS uses a lot of memory, so it is best to add additional 8-16GB RAM
140 if you want to use ZFS.
142 ZFS also provides the feature to use a fast SSD drive as write cache. The
143 write cache is called the ZFS Intent Log (ZIL). You can add that after
144 installation using the following command:
146 zpool add <pool-name> log </dev/path_to_fast_ssd>