mirror of
https://git.proxmox.com/git/pve-docs
synced 2025-04-30 01:15:02 +00:00
pvecm: add basic next-id section
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
This commit is contained in:
parent
cbb265a3d0
commit
eee1c5de0a
20
pvecm.adoc
20
pvecm.adoc
@ -1259,6 +1259,26 @@ it is likely that some nodes will boot faster than others. Please keep in
|
|||||||
mind that guest startup is delayed until you reach quorum.
|
mind that guest startup is delayed until you reach quorum.
|
||||||
|
|
||||||
|
|
||||||
|
[[pvecm_next_id_range]]
|
||||||
|
Guest VMID Auto-Selection
|
||||||
|
------------------------
|
||||||
|
|
||||||
|
When creating new guests the web interface will ask the backend for a free VMID
|
||||||
|
automatically. The default range for searching is `100` to `1000000` (lower
|
||||||
|
than the maximal allowed VMID enforced by the schema).
|
||||||
|
|
||||||
|
Sometimes admins either want to allocate new VMIDs in a separate range, for
|
||||||
|
example to easily separate temporary VMs with ones that choose a VMID manually.
|
||||||
|
Other times its just desired to provided a stable length VMID, for which
|
||||||
|
setting the lower boundary to, for example, `100000` gives much more room for.
|
||||||
|
|
||||||
|
To accommodate this use case one can set either lower, upper or both boundaries
|
||||||
|
via the `datacenter.cfg` configuration file, which can be edited in the web
|
||||||
|
interface under 'Datacenter' -> 'Options'.
|
||||||
|
|
||||||
|
NOTE: The range is only used for the next-id API call, so it isn't a hard
|
||||||
|
limit.
|
||||||
|
|
||||||
Guest Migration
|
Guest Migration
|
||||||
---------------
|
---------------
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user