VirtualBox

Opened 16 years ago

Last modified 16 years ago

#1298 closed defect

BIOS emulation fails for Ubuntu 7.10 guest under Open Solaris — at Version 1

Reported by: Peter Schow Owned by:
Component: other Version: VirtualBox 1.5.6
Keywords: bios dmidecode Cc: Peter.Schow@…
Guest type: other Host type: other

Description (last modified by Frank Mehnert)

When running /usr/sbin/dmidecode on an Ubuntu 7.10 guest, under Virtual Box on OpenSolaris, a BIOS structure is not being published correctly:

# /usr/sbin/dmidecode | more
# dmidecode 2.9
Legacy DMI 2.3 present.
2 structures occupying 256 bytes.
Table at 0x000E1000.

Handle 0x0000, DMI type 0, 20 bytes
BIOS Information
        Vendor: innotek GmbH
        Version: VirtualBox
        Release Date: 12/01/2006
        Address: 0xE0000
        Runtime Size: 128 kB
        ROM Size: 128 kB
        Characteristics:
                ISA is supported
                PCI is supported
                Boot from CD is supported
                Selectable boot is supported
                8042 keyboard services are supported (int 9h)
                CGA/mono video services are supported (int 10h)
                ACPI is supported

Handle 0x0001, DMI type 1, 27 bytes
System Information
        Manufacturer: innotek GmbH
        Product Name: VirtualBox
        Version: 1.2
        Serial Number: 0
        UUID: 012ADD44-8FA0-4270-5A9D-CA61EDA0FFC2
        Wake-up Type: Power Switch
        SKU Number: Not Specified
        Family: Virtual Machine

Wrong DMI structures length: 256 bytes announced, structures occupy 130 bytes.

Change History (1)

comment:1 by Frank Mehnert, 16 years ago

Description: modified (diff)

I'm are aware of this message. However, I don't see it mentioned in the ACPI spec that the size of the ACPI table (which is specified in the global ACPI header) must be exactly the size of all ACPI tables. And I don't know any which which is complaining about this. dmidecode is might be a bit too pedantic.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use