From: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
To: "pve-user@lists.proxmox.com" <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Kernel panics when using OpenVSwitch bridges (Proxmox VE 7.3)
Date: Wed, 31 May 2023 14:14:01 +0000 [thread overview]
Message-ID: <e1ea81fd567b1913bec72be060cc573e3968b22f.camel@groupe-cyllene.com> (raw)
In-Reply-To: <CAD=jCXP3x_PrZRx_kSXQy7_YMTwsD3H0_Ja8s3C3J+h3GHSmrg@mail.gmail.com>
bridge performance is same (without the bugs).
The only was to have better performance with ovs, is to implemented
dpdk + vhost-user nic, and it's not implemented in proxmox currently.
Le mercredi 31 mai 2023 à 14:28 +0200, Benjamin Hofer a écrit :
> Hello community,
>
> we're using OpenVSwitch bridges on a productive Proxxmox 7.3 cluster
> with 4
> nodes (different hardware). Some weeks ago, a sudden reboot happened
> on one
> of the cluster nodes. Further analysis showed that we had kernel
> panics /
> CPU stalls which seem to be related to OpenVSwitch. After more
> analysis, we
> found out that we're able to reliably reproduce the OVS related
> kernel
> panic jst by restarting running LXC containers with network
> interfaces. The
> behaviour could be reproduced on all our nodes. As these nodes are
> quite
> different in their hardware specifications, we assume that it's
> caused by
> some software-related (OVS) bug.
>
> The kernel panics do NOT occur when switching to linux bridged on a
> node.
>
> See kernel log extract attached.
>
> Did someone have a similar behaviour?
> What experiences do you have with linux bridges compared to OVS
> bridges
> regarding network performance?
>
> We could do without OVS features but must rely on good enough
> performance.
>
> System:
> pveversion: pve-manager/7.3-6/723bb6ec (running kernel: 5.15.102-1-
> pve)
> OVS 2.15.0
>
> Thank you in advance.
>
> All the best
> Benjamin
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
prev parent reply other threads:[~2023-05-31 14:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 12:28 Benjamin Hofer
2023-05-31 14:14 ` DERUMIER, Alexandre [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e1ea81fd567b1913bec72be060cc573e3968b22f.camel@groupe-cyllene.com \
--to=alexandre.derumier@groupe-cyllene.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal