we have the same issue on 3 proxmox nodes.
all 3 nodes have high RAM consumtion (95% or more).
suddenly on each of 3 nodes the VM with most memory was killed due OOM
whenever it happens it is time 00:25
Is there a ZFS scrub or so?
this happens nearly every month and only on high RAM usage...
we are unclear about inception.
we use zen2 AMD cpu. are we safe?
https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7005.html is unclear
and
"These architectures do not require a microcode update since the IBPB feature introduced in 2018 to mitigate Spectre v2 already works fine...
Yes, but we can not do experiments because it is a productive environment.
so we have to wait for
https://security-tracker.debian.org/tracker/CVE-2022-40982
3.20230214.1~deb10u1 update.
welcome , no worry
0xfa i have never seen and we wonder, because we are on 0xf4 with fresh updates and reboot.
0xf4 seems not to be an old version. and if, how can we upgrade to 0xfa ?
we have /lib/firmware/intel-ucode , all file in there are from april.
intel-microcode is already the newest...
yes 8 ;), but this did not solve our problems because yet we can not update. so we do microcode updates and reboots. but we wonder, see abough.
06_9EH
D
Coffee Lake H
Coffee Lake Xeon E
Coffee Lake S
9th Generation Intel® Core™ Processor Family
Intel® Xeon® E processor family
9th...
we have no new kernel with debian 10 and proxmox 6 (yes we know, upgrade to 7, but impossible yet).
so we get
cat /sys/devices/system/cpu/vulnerabilities/gather_data_sampling
cat: /sys/devices/system/cpu/vulnerabilities/gather_data_sampling: No such file or directory
cat /proc/version
Linux...
we do: but the list from intel is not clear, is can be the last microcode, but there is no info about mitigation of this issue or about this microcode is the only last available for this cpu.
we wonder bebause on intel we get for our cpu:
"2023.3: 0xf4"
but in dmesg:
[ 0.000000] microcode...
we installed microcode and reboot. we have
[ 0.000000] microcode: microcode updated early to revision 0xf4, date = 2022-07-31
[ 1.665605] microcode: sig=0x906ed, pf=0x2, revision=0xf4
[ 1.668257] microcode: Microcode Update Driver: v2.2.
intel says...
ok thanks.
do we have any problems with 5.13 Kernel? all VMs running fine.
we have microcode updated : microcode updated early to new patch_level=0x0830107a
so we can still be on kernel 5.13 or?
we do not like to reboot our proxmox again now. many customers ;)
we have
apt update
apt upgrade
and now:
Linux 5.13.19-6-pve #1 SMP PVE 5.13.19-15 (Tue, 29 Mar 2022 15:59:50 +0200)
PVE-Manager-Version
pve-manager/7.4-16/0f39f621
seems old kernel 2022. Is there no newer?
ok, to be claear, so with Proxmox "default" it is not enough to do "apt upgrade" and reboot the proxmox host.
we first have to install the amd64-microcode package?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.