proxmox-mirrors/pve-docs
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-docs synced 2025-08-05 23:15:27 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

pvecm.adoc: minor cleanups

Browse Source
This commit is contained in:
Dietmar Maurer 2016-11-30 09:01:32 +01:00
parent d63be10bc0
commit b174347352
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
pvecm.adoc
View File

@ -897,9 +897,9 @@ Migration Type
The migration type defines if the migration data should be sent over a The migration type defines if the migration data should be sent over a
encrypted (`secure`) channel or an unencrypted (`insecure`) one. encrypted (`secure`) channel or an unencrypted (`insecure`) one.
Setting the migration type to insecure means that the RAM content of a Setting the migration type to insecure means that the RAM content of a
Virtual Guest gets also transfered unencrypted, which can lead to virtual guest gets also transfered unencrypted, which can lead to
information disclosure of critical data from inside the guest for information disclosure of critical data from inside the guest (for
example passwords or encryption keys. example passwords or encryption keys).
Therefore, we strongly recommend using the secure channel if you do Therefore, we strongly recommend using the secure channel if you do
not have full control over the network and can not guarantee that no not have full control over the network and can not guarantee that no
@ -911,8 +911,8 @@ always sends the storage content over a secure channel.
Encryption requires a lot of computing power, so this setting is often Encryption requires a lot of computing power, so this setting is often
changed to "unsafe" to achieve better performance. The impact on changed to "unsafe" to achieve better performance. The impact on
modern systems is lower because they implement AES encryption in modern systems is lower because they implement AES encryption in
hardware. But the influence is greater on fast networks, where you can hardware. The performance impact is particularly evident in fast
transfer 10Gbps or more. networks where you can transfer 10 Gbps or more.
Migration Network Migration Network
@ -970,18 +970,18 @@ iface eth2 inet static
# [...] # [...]
---- ----
Here we want to use the 10.1.2.1/24 network as migration network. Here we want to use the 10.1.2.0/24 network as migration network.
For a single migration you can achieve this by using the 'migration_network' For a single migration you can achieve this by using the 'migration_network'
parameter: parameter:
---- ----
# qm migrate 106 tre --online --migration_network 10.1.2.1/24 # qm migrate 106 tre --online --migration_network 10.1.2.0/24
---- ----
To set this up as default network for all migrations cluster wide you can use To set this up as default network for all migrations cluster wide you can use
the migration property in '/etc/pve/datacenter.cfg': the migration property in '/etc/pve/datacenter.cfg':
---- ----
# [...] # [...]
migration: secure,network=10.1.2.1/24 migration: secure,network=10.1.2.0/24
---- ----
Note that the migration type must be always set if the network gets set. Note that the migration type must be always set if the network gets set.