Search results

Thanks. We hope mlx5 is the only one. because we have one Proxmox VE we can not reboot yet.

is proxmox is affacted? we have KVM VMs on it. many thanks

Sehen wir auch so. Der user hat ja keine möglichkeit eine qcow2 zu laden (zb als disk) in seine VM um so auf dem Host Daten lesen/schreiben zu können über die Lücke Danke soweit.

ist proxmox betroffen? https://access.redhat.com/security/cve/cve-2024-4467 welche auswirkungen hat dies? kann dies AUS einem Container (LXC) oder einer VM heraus genutzt werden? oder von einem User per GUI (user hat nur PVEVMUser permissions)? danke.

many thanks. 50% is a lot. we have other proxmox nodes with 80% memory consumtion, without problems.

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...

Thanks. No we only use Proxmox GUI to set VMs.

Is the CVE-2023-40360 a problem to Proxmox? Proxmox using KVM for virtual machines. Many thanks.

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...

any news? safe to upgrade ?

today new microcode was published for buster. now we are on 0xfa and happy

Thanks, yes we are on 3.2-5 all 3 fixes?

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...

CVE-2022-31358 and CVE-2022-35508 and CVE-2022-35507 are fixed in 6.4-15 , right?

What says cat /pro/cpuinfo as your microcode? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041863