[SOLVED] Windows Server 2019 WMI32 Bios

[DrillSgtErnst]

Hi,
I am trying to read out BIOs information via the WMI Object.
Get-WmiBiosCharacteristics

normally it should state somethin similar, to this
Win32_Bios WMI Information
Bios Characteristics
: 07-PCI is supported
: 11-BIOS is Upgradable (Flash)
: 12-BIOS shadowing is allowed
: 15-Boot from CD is supported
: 16-Selectable Boot is supported
: 17-BIOS ROM is socketed
: 19-EDD (Enhanced Disk Drive) Specification is supported
: 23-Int 13h - 5.25 /1.2MB Floppy Services are supported
: 24-Int 13h - 3.5 / 720 KB Floppy Services are supported
: 25-Int 13h - 3.5 / 2.88 MB Floppy Services are supported
: 26-Int 5h, Print Screen Service is supported
: 27-Int 9h, 8042 Keyboard services are supported
: 28-Int 14h, Serial Services are supported
: 29-Int 17h, printer services are supported
: 32-ACPI supported
: 33-USB Legacy is supported
: 40-Reserved for BIOS vendor
: 42-Reserved for BIOS vendor
: 43-Reserved for BIOS vendor
Bios Version : ALASKA - 1072
Codeset :
CurrentLanguage : en|US|iso8859-1
Description : FB
IdentificatonCode :
InstallableLanguages : 7
InstallDate :
LanguageEdition :
ListOfLanguages : en|US|iso8859-1
Manufacturer : American Megatrends Inc.
OtherTargetOS :
PrimaryBIOS : True
ReleaseDate : 20150811000000
SerialNumber : To be filled by O.E.M.
SMBIOSBIOSVersion : FB
SMBIOSMajorVersion : 2
SMBIOSMinorVersion : 7
SoftwareElementID : FB
SoftwareElementState : 3
TargetOperatingSystem : 0
Version : ALASKA - 1072


on PVE I get
03 BIOS bios characteristics not supported

and many blanks.
I have a program reading my BIOS Information and it keeps crashing on strtup 0xc0000005. Access_Violation.
And I guess it's C++. Therefore it could be an error upon reading an array with too few objects.
I run it as Admin, so there are no privilege problems.



Soo my question is: How do I manually set these BIOS Information, or make it accessible through MS?
Any thoughts?

 

[oguz]

hi,

Soo my question is: How do I manually set these BIOS Information, or make it accessible through MS?
Any thoughts?

haven't tried if this approach works for your case, but you can try setting them manually via the GUI:
Select VM -> Options -> SMBIOS settings

 

[DrillSgtErnst]

Thanks for the fast reply. While This does seem to bring me closer to the solution I did have a hard time finding, what I need to fill in.
So looking deeper into this I found following solution.
lookup the DMI Data on the Host Server via

dmidecode

Well the list is so long, my terminal couldn't handle it.

So I had to sort things.

apparently I can use

dmidecode -t N

where N is a natural number.

Well

dmidecode -t 0

was

Getting SMBIOS data from sysfs.
SMBIOS 3.2.0 present.
Handle 0x0000, DMI type 0, 26 bytes
BIOS Information
Vendor: American Megatrends Inc.
Version: 1.0
Release Date: 07/19/2019
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 32 MB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 5.14

Which is exactly, what I am looking for.

Well these are not the Details I can set via GUI. So I tried

dmidecode -t 1

and the output seemed to be what I was looking for.

System Information
Manufacturer: Supermicro
Product Name: Super Server
Version: 0123456789
Serial Number: 0123456789
UUID: 00000000-0000-0000-0000-003610abeezz (changed due to privacy reasons)
Wake-up Type: Power Switch
SKU Number: To be filled by O.E.M.
Family: To be filled by O.E.M.

I filled this input in.

While looking forward on trying if this already succeeds, here is another Post, for how I could possibly integrate even more DMI Information inside the VM. (Sorry it's german)slicewise.net

So I will try this also and let you know then.


I really hope my verbosity helps someone out sometime.


Edit #1: It works, even without the further additions. Maybe I am going to test them though and give Feedback then.
Okay looking deeper into the qm.conf I can not simply add SMBIOS 2 and 3 Tags. Soo Maybe It could be a feature request for the future, being able to set SMBIOS Information to the same or similar to the host.