[Qemu-devel] bug: incorrect uuid in seabios output

[Cole Robinson <crobinso@redhat.com>]

Hi,

The UUID seabios reports in its boot output doesn't match what is passed via
qemu -uuid option. An example is reported here:

https://bugzilla.redhat.com/show_bug.cgi?id=1284259

This is due to:

commit caad057bb6ce86a9cb71520af395fd0bd04a659f
Author: Eduardo Habkost <ehabkost@redhat.com>
Date:   Wed Oct 29 11:26:08 2014 -0200

    smbios: Encode UUID according to SMBIOS specification

    Differently from older versions, SMBIOS version 2.6 is explicit about
    the encoding of UUID fields:

    > Although RFC 4122 recommends network byte order for all fields, the PC
    > industry (including the ACPI, UEFI, and Microsoft specifications) has
    > consistently used little-endian byte encoding for the first three fields:
    > time_low, time_mid, time_hi_and_version. The same encoding, also known as
    > wire format, should also be used for the SMBIOS representation of the UUID.
    >
    > The UUID {00112233-4455-6677-8899-AABBCCDDEEFF} would thus be represented
    > as 33 22 11 00 55 44 77 66 88 99 AA BB CC DD EE FF.

    The dmidecode tool implements this and decodes the above "wire format"
    when SMBIOS version >= 2.6. We moved from SMBIOS version 2.4 to 2.8 when
    we started building the SMBIOS entry point inside QEMU, on commit
    c97294ec1b9e36887e119589d456557d72ab37b5.


seabios doesn't seem to handle this special UUID format when reading from smbios.

Thanks,
Cole