expanding from the two currently existing sentences. In the first one, a
typo VMs -> VM's is fixed. In the second one, "one wants to" is changed
to "you want to", because the sentence already starts with "You can" and
it's active voice.
Adds information about the machine version, rationale behind the
defaults for it and what to do for deprecated versions.
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
The header part of the gui did change already a few releases ago.
The user name was moved into a menu button, which now contains more
user specific actions.
So, update the section to document the current layout and ui elements
again correctly.
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
Chapter "Firmware Updates":
* improve the structure and clarity of information provided
* mention which update methods are when available/recommended
* add information about the already pre-installed pve-firmware package
* emphasise the importance of CPU microcode updates, how to interpret
versions and how to recover a possibly unbootable system
* move info about non-free-firmware repo to "Package Repositories"
Chapter "Package Repositories":
* add new section "Debian Firmware Repository"
Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
This was a bit complex while leaving out some key info, like that
HA groups also play into the target selection, not only CRS.
Try to improve on that.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
For those that jump directly to this part of the docs without seeing
the extra section first.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
The ZIL section was copied over from the cache one, but not fully
adapted, so it wrongly talked about cache devices, as recently
reported by a user.
Improve on that and expand those sections in general.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
and adapt the one from Proxmox VE 6 to what was the effective date
when we stopped providing updates.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
A little update to the PCI(e) docs. The PCI wiki article has been
reworked as well, in line with changes from this patch.
Along some minor grammar fixes added:
* how to check if kernel modules are being loaded
* how to check which drivers to blacklist
* how to add softdeps for module loading
* where to find kernel params
Signed-off-by: Noel Ullreich <n.ullreich@proxmox.com>
[ TL: squash in dropping two trailing whitespace errors ]
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
Use Wikipedia, as it seems CentOS cannot be bothered to create a sane
supported releases + EOL dates table themselves anymore..
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
Firmware updates are important, their existence should not be checked
only when there are already noticeable problems.
Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
Reviewed-by: Dominik Csapak <d.csapak@proxmox.com>
configuring pbs-entries-max can avoid failing backups due to a high
amount of files in folders where a folder exclusion is not possible
Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
This was actually just some POC that got committed by accident and
broke build to to getting a title where not expecting it as there
where two (relatively seen) top-level titles in the calendar events
page.
Fix that by declaring an actual level-0 heading (i.e., title) in the
wiki context.
This then should also fix a dangling link to the calendar-events wiki
page for the docs-in-wiki stuff, e.g., "calendar events" in backup
chapter [0] pointint to 404 [1], that Fiona reported a few weeks ago.
[0]: https://pve.proxmox.com/wiki/Backup_and_Restore#vzdump_jobs
[1]: https://pve.proxmox.com/wiki/Schedule_Format#chapter_calendar_events
Fixes: a90b75d ("package repos: add Ceph 18.2 Reef repos")
Reported-by: Lukas Wagner <l.wagner@proxmox.com>
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
During the redesign of www.proxmox.com the menu structure and therefore
some url changed. Update the external link in order to avoid an
unneccessary redirect.
Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
They are underdocumented and finding information is not that easy.
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
[TL: break footnote with long link over multiple lines ]
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
As there its really common to do things case insensitive a docs note
should help users to discover that Proxmox VE allows one to configure
and LDAP/AD realm to also work case insensitive.
While the UI option got added only recently in pve-manager's commit
c34c5418 ("ui: active directory realm: expose case-sensitive option")
mention it already, as there's a good chance that manager gets bumped
sooner than docs.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
There is an error in this example. The .conf has to be moved in the
quemu-server folder of the new node for the migration to work.
Signed-off-by: Philipp Hufnagl <p.hufnagl@proxmox.com>
The thumbnail attribute is our preferred way to include those
screenshots, but it requires to be inside a paragraph to be replaced, and
having an admonition directly below the attribute doesn't makes it
part of a paragraph.
So, add a bit of text, which was warranted anyway, allowing us to use
the thumbnail attr again.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
They are images after all and should thus be treated as blobs. git does
not do that by default, probably because they have a text header.
Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
While the '--linkX' paramter works with one dash too, let's use two so
we are in line with the man page and other uses of named parameters.
Since we are at it, prepend the command with '#' as we do throughout
this section.
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
As commit 5832a54 ("fix running a2x under new package structure") in
the upstream asciidoc-py repo broke overriding the backend with our
own config for the docbook target, which broke our thumbnail
attribute for paragraphs for the PDF output (HTML is done directly by
asciidoc, and there overriding the config still worked).
Reported upstream [0] and workarounded with the proposed fix applied
to an asciidoc package re-build that got uploaded to our devel repo
for bookworm, so ensure that builds are done with a new enough
version.
[0]: https://github.com/asciidoc-py/asciidoc-py/issues/266
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
