This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1906077 - Q35: Use SMBIOS 3.0 Entry Point Type automatically
Summary: Q35: Use SMBIOS 3.0 Entry Point Type automatically
Keywords:
Status: CLOSED MIGRATED
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-10-23 11:48 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-22 17:51:49 UTC
Type: Story
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-7527 0 None Migrated None 2023-10-23 11:48:16 UTC

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.
Comment 15 RHEL Program Management 2023-08-27 07:28:09 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 19 Xueqiang Wei 2023-09-11 09:09:14 UTC 
Tested with qemu-kvm-8.1.0-1.el9, the default value was still SMBIOS 2.8. The commit bf376f3020d should not be in it.

Versions:
kernel-5.14.0-362.el9.x86_64
qemu-kvm-8.1.0-1.el9
edk2-ovmf-20230524-3.el9.noarch


1. boot a guest with edk2. (don't add smbios-entry-point-type=64 into qemu command lines), check smbios Entry Point Type in the guest.
2. boot a guest with edk2. (add smbios-entry-point-type=64 into qemu command lines), check smbios Entry Point Type in the guest.

After step 1:
# dmidecode 
# dmidecode 3.5
Getting SMBIOS data from sysfs.
SMBIOS 2.8 present.

After step 2:
# dmidecode 
# dmidecode 3.5
Getting SMBIOS data from sysfs.
SMBIOS 3.0.0 present.
Table at 0x7E9D1000.


Hi Julia,

Could you please help add the DTM? Many Thanks.
Comment 20 RHEL Program Management 2023-09-22 17:50:43 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 21 RHEL Program Management 2023-09-22 17:51:49 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Comment 22 Julia Suvorova 2023-10-23 11:48:17 UTC 
(In reply to Xueqiang Wei from comment #19)
> Tested with qemu-kvm-8.1.0-1.el9, the default value was still SMBIOS 2.8.
> The commit bf376f3020d should not be in it.
> 
> Versions:
> kernel-5.14.0-362.el9.x86_64
> qemu-kvm-8.1.0-1.el9
> edk2-ovmf-20230524-3.el9.noarch
> 
> 
> 1. boot a guest with edk2. (don't add smbios-entry-point-type=64 into qemu
> command lines), check smbios Entry Point Type in the guest.
> 2. boot a guest with edk2. (add smbios-entry-point-type=64 into qemu command
> lines), check smbios Entry Point Type in the guest.
> 
> After step 1:
> # dmidecode 
> # dmidecode 3.5
> Getting SMBIOS data from sysfs.
> SMBIOS 2.8 present.
> 
> After step 2:
> # dmidecode 
> # dmidecode 3.5
> Getting SMBIOS data from sysfs.
> SMBIOS 3.0.0 present.
> Table at 0x7E9D1000.
> 
> 
> Hi Julia,
> 
> Could you please help add the DTM? Many Thanks.

I've set it in Jira.
Note You need to log in before you can comment on or make changes to this bug.