Bug 1906077 - Q35: Use SMBIOS 3.0 Entry Point Type automatically
Summary: Q35: Use SMBIOS 3.0 Entry Point Type automatically
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: qemu-kvm
Version: unspecified
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: rc
: 9.3
Assignee: Julia Suvorova
QA Contact: Xueqiang Wei
URL:
Whiteboard:
Depends On: 1904267 1906076 2091166
Blocks: 1788991 1942820
TreeView+ depends on / blocked
 
Reported: 2020-12-09 16:08 UTC by Eduardo Habkost
Modified: 2023-07-18 12:27 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Feature Request
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Eduardo Habkost 2020-12-09 16:08:57 UTC
This bug was initially created as a copy of Bug #1904267

I am copying this bug because: 
Once we support SMBIOS 3.0, we want it to be enabled automatically when necessary.  This can be done in two different ways:
- Automatically enable SMBIOS 3.0 when the tables can't fit in a SMBIOS 2.1 entry point.  This keeps gust ABI compatibility and doesn't require a new machine type).
- Enable SMBIOS 3.0 by default on all VMs.  This changes guest ABI and can be done only on new machine types.


A VM with more than ~720 VCPUs can hit the 65535 bytes limit on SMBIOS tables.  edk2, however, supports SMBIOS 3.0 Entry Points.

We need to support SMBIOS 3.0 entry points on Q35, probably through a new command line option.

Comment 1 John Ferlan 2021-09-09 12:08:01 UTC
Bulk update: Move RHEL-AV bugs to RHEL9. If necessary to resolve in RHEL8, then clone to the current RHEL8 release.

Comment 2 Eduardo Habkost 2021-11-10 22:08:31 UTC
Moving back to virt-maint.  For a discussion around the steps necessary to move the default to SMBIOS 3.0, see:
https://lore.kernel.org/qemu-devel/20211110220632.xaazf2s647r63qm7@habkost.net/

Comment 5 Nitesh Narayan Lal 2022-06-01 16:43:07 UTC
Bumping up the stale date.
This BZ is still relevant for the HPE large VM work so we have to keep it open.
It is not urgent because there is a manual workaround, however, it is necessary from a usability perspective.

Comment 6 John Ferlan 2022-10-16 12:50:24 UTC
Let's plan to resolve this for RHEL 9.2, setting ITR

Comment 7 John Ferlan 2022-10-17 19:40:20 UTC
Igor - feel free to reassign to Julia if necessary. Since it seems bug 2091166 will be resolve, let's get this taken care of too.

Comment 11 Nitesh Narayan Lal 2023-01-09 22:35:05 UTC
Based on Julia's comment, moving this to 9.3, re-setting ITR and bumping up the stale date.


Note You need to log in before you can comment on or make changes to this bug.