-
Story
-
Resolution: Done-Errata
-
Normal
-
None
-
qemu-kvm-8.2.0-1.el9
-
Medium
-
rhel-sst-virtualization-hwe
-
ssg_virtualization
-
20
-
22
-
None
-
QE ack, Dev ack
-
False
-
-
None
-
None
-
Pass
-
Automated
-
Enhancement
-
-
Done
-
-
x86_64
-
None
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.
- account is impacted by
-
RHEL-21705 pc-q35-rhel9.4.0 does not provide proper computer information
- Closed
- blocks
-
RHEL-7526 SMBIOS 2.1 table limits error when booting guest with 710 vcpus and 250G memory
- Closed
- is blocked by
-
RHEL-14111 Rebase qemu-kvm to QEMU 8.2.0
- Closed
- external trackers
- links to
-
RHBA-2023:121202 qemu-kvm bug fix and enhancement update