-
Bug
-
Resolution: Unresolved
-
Undefined
-
rhel-10.2
-
seabios-1.16.3-8.el10
-
None
-
Moderate
-
1
-
rhel-virt-confidential-firmware
-
15
-
17
-
2
-
False
-
False
-
-
No
-
Virt-fw-cc Sprint 14 Dec 15
-
Pass
-
New Test Coverage
-
Unspecified Release Note Type - Unknown
-
Unspecified
-
Unspecified
-
Unspecified
-
-
x86_64
-
None
What were you trying to do that didn't work?
Two customers independently got worried that the guest BIOS appeared to be very out of date. They ran dmidecode and saw something like this (I'm using Fedora as a host for my test, but the same thing happens on RHEL host):
BIOS Information Vendor: SeaBIOS Version: 1.17.0-4.fc43 Release Date: 04/01/2014
What is the impact of this issue to you?
In one case Microsoft rejected a bug report from us and told the customer they had to "update the BIOS".
In the second case, we had asked the customer to update their hardware BIOS, and they got confused by the date on the guest BIOS, and it all took a bit of explaining to sort out.
Please provide the package NVR for which the bug is seen:
All versions of seabios-bin since forever.
How reproducible is this bug?:
100%
Steps to reproduce
- Run dmidecode from inside a virtual machine.
- clones
-
RHEL-126466 [rhel-10] SeaBIOS date is "stuck" at 2014 even for recent releases
-
- Release Pending
-