NetworkManager, by default, uses a connection ID and a per-host random
and secret key to generate `stable` MAC addresses. The intention is to
keep a connection's MAC address stable indefinitely but for it to be
different on every host.
The current instruction mention that "`stable` generates a random
address that persists for each boot session". This is indeed true for
AppVMs using stock TemplateVMs. The reason is that the secret key doesn't
exist in the template and thus is only created when the AppVM starts.
This, however, may not be true for other VMs.
In order to ensure that MACs are always only `stable` during one boot
session, `stable-id`, which is used to generate MACs, can be adjusted.
NetworkManager's documentation suggests to use `${CONNECTION}/${BOOT}`
to ensure generated MACs are unique to a boot session and connection [1].
[1]: https://developer.gnome.org/NetworkManager/stable/nm-settings.html
Reviewing the HCL a lot of reporters had to install in legacy mode because UEFI mode would fail. For various reports, they used custom kernel parameters by changing the grub entry. This is frequent for recent hardware or some configurations (dual gpu,...).
With this procedure a user can perform UEFI install with custom kernel parameters
The minimal template upgrade instructions still included the
`qvm-trim-template` command, which only works in R3.2. I've moved those
instructions into the R3.2 section and added new instructions using the
`fstrim` command in the R4.0 section.
I've also removed the section on differences between the standard and
minimal upgrade procedures, since the second point is no longer accurate
(e.g., `sudo` is installed by default in the minimal template on R3.2),
and the first point is not significant enough to merit keeping the
section.
https://github.com/QubesOS/qubes-doc/pull/505https://github.com/QubesOS/qubes-issues/issues/3429
