Note, at time of commit the Enterprise repo is not yet available, but
that should change (soon) once this is bumped, so do not bother with
a temporary note.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
not that obvious behaviour on the systemd side, and missing cert renewal can
have wide-reaching consequences.
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
Intel EMT64 is not a thing, the correct variant would be Extended
Memory 64 Technology, which is shortened to EM64T [0].
But the `Intel EM64T` term was replace a long time ago by `Intel 64`
[1], so just go with that.
[0]: https://www.intel.com/content/www/us/en/support/articles/000005898/processors.html
[1]: "[...] in March 2004 unveiled the "official" name EM64T (Extended
Memory 64 Technology). In late 2006 Intel began instead using
the name Intel 64 for its implementation [...]"
-- https://en.wikipedia.org/wiki/X86-64#Intel_64
Reported-by: Alexander P. Inzinger-Zrock
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
This entry is always present under 'Advanced Options', even if the ISO
was not prepared for an unattended installation, mainly for debug.
Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
Enabling IOMMU on the host is not a requirement for vIOMMU. It is only
a requirement for passthrough. Add a sentence to clarify the need for
a configured PCI(e) passthrough on the host for passthrough to nested
VMs.
While at it also clarify that this does not only applies to PCI but
also PCIe here.
Suggested-by: Dominik Csapak <d.csapak@proxmox.com>
Signed-off-by: Markus Frank <m.frank@proxmox.com>
[ TL: mention all changes and avoid overly long line with link ]
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
add the information that the parameter is special like other secret ones, and
add the resulting config to the example to make it even more obvious.
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
[FE: remove equals sign from config example]
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
Add a concise section about what PBS change detection mode is, where
to configure the option and what it affects, including a table with a
description of the modes.
Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
move "+" in to new line, if it set at the end of the line it will be
lost when converting to other formats. E.g. html
Signed-off-by: Mario Loderer <m.loderer@proxmox.com>
Most of the changes were done when adapting the PVE docs to
the new PBS notification system, so now we 'backport' those
improvements.
Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
This was a bit inconsistent between the different notification types:
- APT/VZDump included the domain part
- fence notifications did not
A decision has been made to unify this by removing the domain part
from APT/VZDump notifications.
Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
The effect and unit of the validation delay was unclear from our
documentation, and the link to the acme.sh documentation didn't explain
it either
Signed-off-by: Folke Gleumes <f.gleumes@proxmox.com>
[ TL: reflow to 80cc, while 100cc is fine in general, this file uses
basically only 80cc and honoring local style trumps using a more
modern line wrap width ]
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
Works the same as in our PBS documentation and is generally common for
documentations.
Very useful for linking specific sections of the documentation in other
places. Previously, this always had to be done by getting the correct
anchor from the HTML directly via e.g. browser devtools.
Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
Tested-by: Max Carrara <m.carrara@proxmox.com>
The initramfs-tools hook /usr/share/initramfs-tools/hooks/udev copies
link files from /etc/systemd/network to the initramfs, where they take
effect in early userspace. If the link files in the initramfs diverge
from the link files in the rootfs, this can lead to confusing
behavior, as reported in enterprise support. For instance:
- If an interface matches link files both in the initramfs and the
rootfs, it will be renamed twice during boot.
- A leftover link file in the initramfs renaming an interface A to a
new name X may prevent a link file in the rootfs from renaming a
different interface B to the same name X (it will fail with "File
exists").
To avoid this confusion, mention the link files are copied to the
initramfs, and suggest updating the initramfs after making changes to
the link files.
Suggested-by: Hannes Laimer <h.laimer@proxmox.com>
Signed-off-by: Friedrich Weber <f.weber@proxmox.com>
Mention that the systemd link file should contain `Type=ether` in most
setup, to make sure it only applies to Ethernet devices and does not
ever apply to e.g. bridges or bonds which inherit the MAC address of
the Ethernet device. Mention that some setups may require other
options.
Reported in the forum [0] and in #5429 [1].
[0] https://forum.proxmox.com/threads/144557/post-656188
[1] https://bugzilla.proxmox.com/show_bug.cgi?id=5429
Fixes: 96c0261 ("fix #4847: network: extend section on interface naming scheme")
Signed-off-by: Friedrich Weber <f.weber@proxmox.com>
As the job one is quite a bit crowded as is and there are some
screenshots that fit really well with some specific sections like
retention or the backup note templates.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
