VirtualBox: SMBIOS Type 3 wrong format
Posted: Wed Apr 17, 2019 1:03 am
Hello,
I'm new in this forum. Before asking my question, I must said that it's very interessting to learn how OS works.
I'm living in France and interesting by low level programming languages. Sorry by advance for my poor English.
So this is my question:
Reading SMBIOS with WMware or QEMU is OK. While reading SMBIOS with VirtualBox, at Type 3 I've this issue.
As you see SMBIOS version is 2.5 with 10 entrys. Type 0, 1, 2 have been read correctly before.
In the documentation Type 3 > 2.1, len is supposed to be 0Dh. So it's OK we have the minimum (in blue).
After (in green) the string terminated with 0 and the second 0 as expected to terminate the structure.
So after, in QEMU or WMvare, we will found type 4 (Processor Information). Here not, we have Type 126 and until end of structure other with the Type 128 that doesn't exist in documentation.
So I think that here the table is incorrect. You can see in the memory dump what I get.
What's wrong?
I'm new in this forum. Before asking my question, I must said that it's very interessting to learn how OS works.
I'm living in France and interesting by low level programming languages. Sorry by advance for my poor English.
So this is my question:
Reading SMBIOS with WMware or QEMU is OK. While reading SMBIOS with VirtualBox, at Type 3 I've this issue.
In the documentation Type 3 > 2.1, len is supposed to be 0Dh. So it's OK we have the minimum (in blue).
After (in green) the string terminated with 0 and the second 0 as expected to terminate the structure.
So after, in QEMU or WMvare, we will found type 4 (Processor Information). Here not, we have Type 126 and until end of structure other with the Type 128 that doesn't exist in documentation.
So I think that here the table is incorrect. You can see in the memory dump what I get.
What's wrong?
It's for testing my code, so I'll stop to use VirtualBox for this purpose. WMvare and QEMU works fortunally.