All Virtuozzo development lists (kernel + QEMU)
 help / color / mirror / Atom feed
From: Alexey Kuznetsov <kuznet@virtuozzo.com>
To: Konstantin Khorenko <khorenko@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH vz10 v2 0/3] Restore ConnectX-3 Pro support dropped by RHEL 10
Date: Wed, 16 Sep 2026 23:58:23 +0800	[thread overview]
Message-ID: <CAMrnHh68TB2N2r5tpASPcu4ZKK0wwgkw5m0MCFELnSY-5DrMAw@mail.gmail.com> (raw)
In-Reply-To: <20260916-b4-prep-khorenko-vstor-145697-mlx4-v2-0-fe0a34255714@virtuozzo.com>

Ack to all

On Wed, Sep 16, 2026 at 11:41 PM Konstantin Khorenko
<khorenko@virtuozzo.com> wrote:
>
> RHEL 10 removed the mlx4 driver: CONFIG_MLX4_CORE is off on every
> architecture but aarch64, and the whole ConnectX-3 family sits in
> rh_disabled_pci_devices[], so local_pci_probe() answers -EACCES even
> where the driver is built. A host whose only NIC is a ConnectX-3 Pro
> cannot run a release kernel at all, which is what we hit on lab
> equipment.
>
> The removal follows NVIDIA ending vendor support for the hardware,
> not any defect: the driver is maintained upstream, Fedora builds it,
> and AlmaLinux 10 has already moved the same PCI IDs out of the
> disabled list. The history is collected in the Jira issue below.
>
> Patch 1 adds the skip_pci_blacklist option, so a host that hits the
> blacklist on some other device can still be brought up, from an IPMI
> console if need be.
>
> Patch 2 moves 15b3:1007 (ConnectX-3 Pro) from the disabled list to
> the unmaintained one, so the card is driven while the log keeps
> saying that the hardware is untested.
>
> Patch 3 builds mlx4 again, Ethernet and InfiniBand, without which the
> first two patches change nothing on x86_64.
>
> The rest of the mlx4 family and ConnectX-2 stay as RHEL left them.
>
> https://virtuozzo.atlassian.net/browse/VSTOR-145697
>
> Changes in v2:
> - split the single patch into the option, the PCI ID and the config
> - report a bypassed device as unmaintained rather than deprecated:
>   "deprecated" promises support that exists today, which is not true
>   for a device RHEL has already disabled
> - move 15b3:1007 into rh_unmaintained_pci_devices[] instead of
>   deleting it, so the card is still reported, the way AlmaLinux does
> - keep skip_pci_blacklist and its core_param() next to their only
>   user, inside #ifdef CONFIG_PCI
> - document skip_pci_blacklist in kernel-parameters.txt
> - enable CONFIG_MLX4_CORE, CONFIG_MLX4_EN and CONFIG_MLX4_INFINIBAND
>   in custom-overrides: RHEL 10 does not build mlx4 on x86_64, so v1
>   had no effect there
> - Link to v1: http://lore.virtuozzo.com/aqlsDIyP9+pTstGU@mops2
>   Message-Id: <aqlsDIyP9+pTstGU@mops2>
>   [Devel] [PATCH VZ10] core: allow to bypass rhel pci blacklist
>
> Signed-off-by: Konstantin Khorenko <khorenko@virtuozzo.com>
> ---
> Alexey Kuznetsov (2):
>       core: add skip_pci_blacklist option to probe RHEL-disabled devices
>       core: allow ConnectX-3 Pro to probe, as unmaintained hardware
>
> Konstantin Khorenko (1):
>       configs: build the mlx4 driver, Ethernet and InfiniBand
>
>  Documentation/admin-guide/kernel-parameters.txt              | 12 ++++++++++++
>  kernel/rh_messages.c                                         |  9 +++++++++
>  kernel/rh_messages.h                                         |  2 +-
>  redhat/configs/custom-overrides/generic/CONFIG_MLX4_CORE     |  1 +
>  redhat/configs/custom-overrides/generic/CONFIG_MLX4_EN       |  1 +
>  .../configs/custom-overrides/generic/CONFIG_MLX4_INFINIBAND  |  1 +
>  6 files changed, 25 insertions(+), 1 deletion(-)
> ---
> base-commit: 3fff8724d1f894459c1477990fe086c0c2573410
> change-id: 20260916-b4-prep-khorenko-vstor-145697-mlx4-7d6927d60446
>
> Best regards,
> --
> Konstantin Khorenko <khorenko@virtuozzo.com>

_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel

  parent reply	other threads:[~2026-09-16 16:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16 15:40 Konstantin Khorenko
2026-09-16 15:40 ` [Devel] [PATCH vz10 v2 1/3] core: add skip_pci_blacklist option to probe RHEL-disabled devices Konstantin Khorenko
2026-09-16 15:40 ` [Devel] [PATCH vz10 v2 2/3] core: allow ConnectX-3 Pro to probe, as unmaintained hardware Konstantin Khorenko
2026-09-16 15:40 ` [Devel] [PATCH vz10 v2 3/3] configs: build the mlx4 driver, Ethernet and InfiniBand Konstantin Khorenko
2026-09-16 15:58 ` Alexey Kuznetsov [this message]
2026-09-16 16:40 ` [Devel] [PATCH vz10 v2 0/3] Restore ConnectX-3 Pro support dropped by RHEL 10 Konstantin Khorenko

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=CAMrnHh68TB2N2r5tpASPcu4ZKK0wwgkw5m0MCFELnSY-5DrMAw@mail.gmail.com \
    --to=kuznet@virtuozzo.com \
    --cc=devel@openvz.org \
    --cc=khorenko@virtuozzo.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.