* CRIU: for live migration (planned)
-* Use latest available kernels (4.4.X)
+* Runs on modern Linux kernels
* Image based deployment (templates)
By default additional mount points besides the Root Disk mount point are not
included in backups. You can reverse this default behavior by setting the
-* Backup* option on a mount point.
+*Backup* option on a mount point.
// see PVE::VZDump::LXC::prepare()
Replication of Containers mount points
General Settings
~~~~~~~~~~~~~~~~
-[thumbnail="gui-create-ct-general.png"]
+[thumbnail="screenshot/gui-create-ct-general.png"]
General settings of a container include
CPU
~~~
-[thumbnail="gui-create-ct-cpu.png"]
+[thumbnail="screenshot/gui-create-ct-cpu.png"]
You can restrict the number of visible CPUs inside the container using
the `cores` option. This is implemented using the Linux 'cpuset'
Memory
~~~~~~
-[thumbnail="gui-create-ct-memory.png"]
+[thumbnail="screenshot/gui-create-ct-memory.png"]
Container memory is controlled using the cgroup memory controller.
Mount Points
~~~~~~~~~~~~
-[thumbnail="gui-create-ct-root-disk.png"]
+[thumbnail="screenshot/gui-create-ct-root-disk.png"]
The root mount point is configured with the `rootfs` property, and you can
configure up to 10 additional mount points. The corresponding options
Network
~~~~~~~
-[thumbnail="gui-create-ct-network.png"]
+[thumbnail="screenshot/gui-create-ct-network.png"]
You can configure up to 10 network interfaces for a single
container. The corresponding options are called `net0` to `net9`, and
.Start and Shutdown Order
// use the screenshot from qemu - its the same
-[thumbnail="gui-qemu-edit-start-order.png"]
+[thumbnail="screenshot/gui-qemu-edit-start-order.png"]
If you want to fine tune the boot order of your containers, you can use the following
parameters :
makes sense between the machines running locally on a host, and not
cluster-wide.
+Hookscripts
+~~~~~~~~~~~
+
+You can add a hook script to CTs with the config property `hookscript`.
+
+ pct set 100 -hookscript local:snippets/hookscript.pl
+
+It will be called during various phases of the guests lifetime.
+For an example and documentation see the example script under
+`/usr/share/pve-docs/examples/guest-example-hookscript.pl`.
Backup and Restore
------------------