DMI Handle is not unique

[MattRobinson]

I have been having issues with the DMI on VirtualBox.

When I run dmidecode on Ubuntu 18.04, there are 2 entries for Handle 0x0008. When python's py-dmidecode runs, it loops through the DMI and the contents of the second entry for Handle 0x0008 replace the previous entry, causing it's output to be invalid.

I think the Handle entries should be unique.

I have attached a copy of my dmi output with the above issue (0x0008 listed twice).

[Klaus Espenlaub]

Ack. Long standing bug, introduced in 2013. The minimally invasive change is using handle 0x0004 for the DMI OEM table, because that one is unused so far. I've applied the fix to the internal dev repo already, backports to the release branches will follow. Note that this did not make it into the 7.0.12/6.1.48 releases. The ones after should have it.

[galitsyn]

Hello,

We just released VirtualBox 6.1.50 and 7.0.14. This issue should be fixed there. You can download this version from here. Closing.

[dxben]

Saw this just now running Debian 12 and Virtualbox Version 7.0.14 r161095 (Qt5.15.2)

[Klaus Espenlaub]

dxben - can you provide details (output from dmidecode showing duplicated handles)? The issue was entirely resolved in my tests. Could it be that you have a VM where the DMI information is coming from saved state? Then the safe way would be shutting it down and starting again.

[sercallegar]

Unclear to me if the matter is a duplicate header. However, I still see an "Invalid DMI Field Header" booting debian 12 in VirtualBox. Virtualbox is at 7.0.18. I think that the message has started to appear after I have installed the guest additions, but I am not 100% sure.