23.3. SMBIOS System Information
Some hypervisors allow control over what system information is presented to the guest virtual machine (for example, SMBIOS fields can be populated by a hypervisor and inspected using the
dmidecodecommand in the guest virtual machine). The optional
sysinfoelement covers all such categories of information.
... <os> <smbios mode='sysinfo'/> ... </os> <sysinfo type='smbios'> <bios> <entry name='vendor'>LENOVO</entry> </bios> <system> <entry name='manufacturer'>Fedora</entry> <entry name='vendor'>Virt-Manager</entry> </system> </sysinfo> ...
Figure 23.5. SMBIOS system information
<sysinfo>element has a mandatory attribute
typethat determines the layout of sub-elements, and may be defined as follows:
<smbios>- Sub-elements call out specific SMBIOS values, which will affect the guest virtual machine if used in conjunction with the
smbiossub-element of the
<os>element. Each sub-element of
<sysinfo>names a SMBIOS block, and within those elements can be a list of entry elements that describe a field within the block. The following blocks and entries are recognized:
<bios>- This is block 0 of SMBIOS, with entry names drawn from
<system>- This is block 1 of SMBIOS, with entry names drawn from
family. If a
uuidentry is provided alongside a top-level
uuidelement, the two values must match.