Search results

yes, i think this is a better aproach instead of struggling with local wifi adapters & issues. have a look at https://forum.proxmox.com/threads/proxmox-server-via-wifi-list-of-wifi-bridge-adapters-which-work-with-proxmox.161124/ and report your own findings/experience with different wifi...

deine beschreibung klingt etwas wirr beschreib dein setup bitte als erstes mal etwas genauer wo ist das proxmox installiert und wie genau? partitionstabelle und zpool infos wären hilfreich

>Warum setzt man ein System in der Firma auf, was man nur mit KI eingerichtet bekommen hat weil mit KI jetzt jeder alles kann

da die website im wartungsmodus ist - was kostet denn der spass?

> Given the setup and the fact that it directly impacts the Intel E810 NIC, I also suspect it’s tied to the ice driver changes introduced in those newer kernels yes, seems so: https://securityvulnerability.io/vulnerability/CVE-2025-21981...

does your system do efi boot or grub boot ? efi boot can very picky , i have a LOT more problems with efi boot then with traditional bios/grub boot

there is another caveat: https://forum.proxmox.com/threads/help-with-trim-on-virtio-scsi-single.123819/#post-542552 i.e. it appears, that subsequent fstrim runs need a reboot in between, to be effective with ext4

there are no errors/warnings visible in any of the pbs logs on the pve host where the backup had this error i find in journalctl Sep 16 12:40:33 pve2-bnkw pvedaemon[3818711]: <root@pam> starting task UPIDve2-bnkw:003C2BCF:7C760E9F:68C93EA1:vzdump:101:root@pam: Sep 16 12:40:33 pve2-bnkw...

i manually started some backup while there was some load on the pbs disks and got "corrupted double-linked list" error once on backup. the second backup run afterwards ran fine and validating the backup did not show any error should i worry ? what does this error mean ? ... NFO: 27% (452.0...

yes, i can confirm these are both upstream issues for the groff one there is an upstream bugreport at https://bugs-devel.debian.org/cgi-bin/bugreport.cgi?bug=1101827 for the apparmor one, i don't find appropriate

>and think the groff error message is a result of this wrong: https://askubuntu.com/questions/1521258/what-means-cant-resolve-man7-groff-man-7 so, we have 2 different issues here

i'm also observing this exact behaviour and think the groff error message is a result of this. that should be fixed. we should file a bugzilla ticket

what? without agenda being ready for primetime? too, i wanted to visit :(((

>Although each VM was configured with 7GB RAM, the corresponding KVM processes were using 7.02GB and 6.60GB of actual physical memory, totaling ~13.6GB, which is unexpected. why is that unexpected ?

that has been isolated as a samba problem and is resolved a while ago, see https://github.com/openzfs/zfs/issues/16490

too old, there is no binary guest agent package available for el5

thanks

>This requires the aquisition of hardware that supports WDS mode but i'm not connecting via mesh - and it just works with virtual machines!?

hello, i had some problem with a backup disk. why is this only considered to be worth a warning ? 2025-05-19T07:40:44+02:00: marked 67% (574 of 856 index files) 2025-05-19T07:40:47+02:00: marked 68% (583 of 856 index files) 2025-05-19T07:40:52+02:00: marked 69% (591 of 856 index files)...

fixed at https://lore.proxmox.com/pbs-devel/20250310111634.162156-1-c.ebner@proxmox.com/T/#m3f246b1e4acde9a66b8e165cbef4dc8270c64109