qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug 1826200] Re: RFE: populate "OEM Strings" (type 11) SMBIOS table str


From: Laszlo Ersek (Red Hat)
Subject: [Bug 1826200] Re: RFE: populate "OEM Strings" (type 11) SMBIOS table strings from regular files
Date: Wed, 12 Aug 2020 11:51:54 -0000

We'll probably never have resources for this -- nice to have feature,
but has not become critical in ~1.5 years. LP doesn't allow me to close
the ticket as "Won't Fix", so I'll have to go with "Invalid". (The
report is not invalid at all, but the ticket status should *somehow*
reflect that we have no resources for working on this.)

** Changed in: qemu
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1826200

Title:
  RFE: populate "OEM Strings" (type 11) SMBIOS table strings from
  regular files

Status in QEMU:
  Invalid

Bug description:
  The feature added in

  
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=2d6dcbf93fb01b4a7f45a93d276d4d74b16392dd

  and exposed by libvirt as

    https://libvirt.org/formatdomain.html#elementsSysinfo

  allows the user to specify up to 255 strings in the unofmatted area of
  the Type 11 SMBIOS table, where each string may be of arbitrary
  length. This feature is useful for exposing arbitrary text to
  arbitrary guest components (in particular when strings are prefixed
  with "application identifiers").

  Right now, strings can only be specified on the QEMU command line,
  which limits the amount of data that can be passed. Please enable
  users to pass data from regular files too.

  For example:

    $QEMU -smbios
  type=11,value=Hello,txtfile=file1.txt,txtfile=file2.txt

  where "file1.txt" and "file2.txt" could be text files containing ASCII
  application prefixes, followed by base64-encoded binary data.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1826200/+subscriptions



reply via email to

[Prev in Thread] Current Thread [Next in Thread]