From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fiona Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH v2 qemu] fix #4507: add patch to automatically increase NOFILE soft limit
Date: Tue, 6 Feb 2024 10:34:23 +0100 [thread overview]
Message-ID: <b9b17e29-bf04-47ea-b26d-9fa4f936228d@proxmox.com> (raw)
In-Reply-To: <20240205131317.111771-1-f.ebner@proxmox.com>
Am 05/02/2024 um 14:13 schrieb Fiona Ebner:
> In many configurations, e.g. multiple vNICs with multiple queues or
> with many Ceph OSDs, the default soft limit of 1024 is not enough.
> QEMU is supposed to work fine with file descriptors >= 1024 and does
> not use select() on POSIX. Bump the soft limit to the allowed hard
> limit to avoid issues with the aforementioned configurations.
>
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
>
> Changes in v2:
> * pick v2 that was accepted upstream:
> https://lore.kernel.org/qemu-devel/ZcC3-G_COqbk8SxX@redhat.com/
> * because of that, put it into the extra/ folder rather than pve/
>
> ...-increase-NOFILE-soft-limit-on-POSIX.patch | 119 ++++++++++++++++++
> ...async-for-background-state-snapshots.patch | 4 +-
> ...-Add-dummy-id-command-line-parameter.patch | 4 +-
> ...E-Allow-version-code-in-machine-type.patch | 4 +-
> ...ct-stderr-to-journal-when-daemonized.patch | 6 +-
> debian/patches/series | 1 +
> 6 files changed, 129 insertions(+), 9 deletions(-)
> create mode 100644 debian/patches/extra/0012-qemu_init-increase-NOFILE-soft-limit-on-POSIX.patch
>
>
applied, thanks!
prev parent reply other threads:[~2024-02-06 9:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 13:13 [pve-devel] " Fiona Ebner
2024-02-06 9:34 ` Thomas Lamprecht [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=b9b17e29-bf04-47ea-b26d-9fa4f936228d@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@proxmox.com \
--cc=pve-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox