RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
http://svn.savannah.gnu.org/viewvc/?view=rev&root=qemu&revision=7163 implemented more SMBIOS information:
 -smbios type=0[,vendor=str][,version=str][,date=str][,release=%d.%d]
 -smbios type=1[,manufacturer=str][,product=str][,version=str][,serial=str]
              [,uuid=$(uuidgen)][,sku=str][,family=str]

I wonder how much of this we need:
1. For special applications that look at those fields(P2V comes to mind - some HP apps need it - we know that already)
2. For our own use (the tools within the guest can make use of this information, for example, obtain underlying KVM version
3. I'm pretty sure this is NOT needed for SVVP - at least not with WLK 1.2 - but may be with future versions - 1.4.

I think we should see that we can live without it for RHEV-1.0, and then postpone it with no regrets to future releases.

Lastly, this is on KVM for merge purposes, but once it's in the code, BZs should be opened for VDSM and RHEV-M to support it.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Related to https://bugzilla.redhat.com/show_bug.cgi?id=495842 (KVM SVVP: The SMBIOS HCT failed the SVVP testing when install windows 2008 on kvm)

*** This bug has been marked as a duplicate of bug 495844 ***