there's not really any proper documentation yet, but it boils down toThe release note mentions a custom cpu configuration file for qemu. I'm looking for a sample file or documentation on that feature.
cpu-model: aes flags +aes reported-model host
qm set XXX -cpu custom-aes
ovs_options tag=10works but I can't find any explanation as to why ovs_options are broken in this version.
Unfortunately I have had a pretty horrendous experience running an "apt dist-upgrade" that moved my system from 6.1 to 6.2 :-(
The update included a new ifupdown2 package. This turned out to not be compatible with my existing /etc/network/interfaces file, as it had separately defined network, subnet and broadcast fields rather than using CIDR notation. The result was that I lost all networking and had to access via IPMI. Identifying the problem was not easy as the error messages were rather cryptic.
The system is a Supermicro AS-1114S-WTRT with an AMD EPYC 7402p processor.
Has anyone else experienced these issues?
Opening a new thread here is often a good idea, often then one (after confirmation of the issue) is asked to please open a to make a new entry over at https://bugzilla.proxmox.com/ to track the issue.Is there somewhere specific I should report this?
You can either just use theFinally, is there a recommended way to apply important software updates but hold back on packages such as new kernels?
apt install package-1 package-2 ...if this is just for a one time "only upgrade a specific set of available updates now" situation.
/etc/apt/preferences.d/directory, for example:
Package: pve-kernel-5.4.44-* Pin: release * Pin-Priority: -1