From: Arjen via pve-user <pve-user@lists.proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Cc: Arjen <leesteken+proxmox@pm.me>
Subject: Re: [PVE-User] Dell PowerEdge T140, megaraid, BIOS Boot...
Date: Wed, 14 May 2025 20:46:36 +0000 [thread overview]
Message-ID: <mailman.423.1747256171.394.pve-user@lists.proxmox.com> (raw)
In-Reply-To: <aCT_V2BS6oiB63WY@sv.lnf.it>
[-- Attachment #1: Type: message/rfc822, Size: 4575 bytes --]
From: Arjen <leesteken+proxmox@pm.me>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Dell PowerEdge T140, megaraid, BIOS Boot...
Date: Wed, 14 May 2025 20:46:36 +0000
Message-ID: <oj5gf2D_oUcP0yEhjWbdHZXjiz6ULD0wSK9pbeUseDy663MWkg2MIClfGGzZFoAfO4XahMOmIQ78iYDJoBKRMYb6Bf6LjAlk8ECZD1Q6xlk=@pm.me>
On Wednesday, 14 May 2025 at 22:40, Marco Gaiarin <gaio@lilliput.linux.it> wrote:
> But is really strange... most of our T140 (ALL boot in BIOS mode) work
> without 'intel_iommu=off', but three server need it to boot. All get upgaded
> to the latest BIOS revision.
Maybe those three have VT-d (or IOMMU) enabled in the motherboard BIOS? intel_iommu=on became the default in kernel version 6.8.
Unless VT-d is enabled in the motherboard BIOS settings, intel_iommu=off does nothing (as it is disabled in the motherboard BIOS).
kind regards
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2025-05-14 20:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 15:21 Marco Gaiarin
2025-05-02 17:03 ` RolandK via pve-user
[not found] ` <b7165214-1db9-46a8-8d9d-2e8cb5cd1c6c@web.de>
2025-05-14 20:38 ` Marco Gaiarin
2025-05-14 20:46 ` Arjen via pve-user [this message]
2025-05-16 13:43 ` Marco Gaiarin
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=mailman.423.1747256171.394.pve-user@lists.proxmox.com \
--to=pve-user@lists.proxmox.com \
--cc=leesteken+proxmox@pm.me \
/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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal