Search results

it's not yet ready, prelimary patches has been sent to the dev mailing list.

what is your hardware ?

Hi, I had 2 crash in 24h with kernel 6.8 on 2 differents servers (same generation, same hardware): no kernel panic, server freeezed system installed on lvm nic: mellanox ConnectX-4 Lx Edit: The 2 crashing servers also have local encrypted ceph osd nvme drives. (The 20 other servers not...

Hi, I had 2 crash in 24h with kernel 6.8 on 2 differents servers (same generation, same hardware): no kernel panic, server freeezed edit : difference , crashing servers have ceph osd running with crypted osd. They other servers don't have any osd or storage for vm. server: System...

I'll be hard to add this this yourself. ask this feature on bugzilla.proxmox.com (the new nftables implementation is currently in developpement, so it's a good time to ask for it)

proxmox kernel 6.8 is based from ubuntu kernel lts, and ubuntu is supporting zfs officially.

hi, I'll work on it soon https://bugzilla.proxmox.com/show_bug.cgi?id=4300

"apt upgrade" is the problem, not "apt update" apt update is to update th packages list apt upgrade, upgrade only installed packages but don't install newer dependencies apt dist-upgrade|full-upgrade upgrade installed packages and install newer dependencies. if you are not sure,you can...

yes. (1450 should be enough with vxlan.) another way : you need to increase your physical network and hypervisor nics with minimum 1550 mtu. vxlan need 50 more bytes for tunneling

kenrel 6.8.4, ksm enabled + numa balancing=1 : no problem after 1 week, tested on 16 nodes with 1500vms

your config is ok, maybe try to change bridge-vids 2-4094 with bridge-vids 2504 Some nic model don't support too much vlan (like 256max number of differents vlan).

you can add in /etc/network/interfaces iface <vnetname> address 192.168.20.21/24

http or https ? if it's only ssh/https or other ssl protocol, it could be a mtu problem with fragmentation. (try mtu 1400 in your vm nic config for example)

This is simply the virtualisation of iops, this add latency. (Look at your vm cpu on the host, maybe you'll have 1 vmcore at 100%) do you have really have applications doing more than 16000 4k sync write with iodepth=1 ? of course, It'll increase with parrallel write. and generally...

maybe try the new 6.8 kernel (apt install proxmox-kernel-6.8). It's resolving some freeze with numa && ksm, maybe it could be related to your case too.

do you have tried through esx directly ? going through vcenter is known to be slow.

Hi, no problem since 3 days now. I'm going to upgrade all my clusters to kernel 6.8.

nftables is coming soon, and it should avoid extra fwbrX bridge, so it should work with fragmentation. But try to avoid fragmentation please ...lower your mtu ..

I have upgrade 1 server to 6.8 for testing, no problem (lag/freeze) with numa && ksm enabled since 24h ! I'll recheck monday

it should be resolved on 6.8 only.