Bug 1906077

Summary:	Q35: Use SMBIOS 3.0 Entry Point Type automatically
Product:	Red Hat Enterprise Linux 9	Reporter:	Eduardo Habkost <ehabkost>
Component:	qemu-kvm	Assignee:	Julia Suvorova <jusual>
qemu-kvm sub component:	Machine Types	QA Contact:	Xueqiang Wei <xuwei>
Status:	CLOSED MIGRATED	Docs Contact:
Severity:	medium
Priority:	medium	CC:	ailan, coli, jferlan, jinzhao, jusual, juzhang, nanliu, nilal, pmendezh, virt-maint
Version:	unspecified	Keywords:	FutureFeature, MigratedToJIRA, Reopened, Triaged
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	9.3
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-22 17:51:49 UTC	Type:	Story
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1904267, 1906076, 2091166
Bug Blocks:	1788991, 1942820

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.