Bug 499453

Summary:	add manufacturer and product name info to guest SMBIOS
Product:	Red Hat Enterprise Linux 5	Reporter:	Alan Zarembok <azarembo>
Component:	xen	Assignee:	Paolo Bonzini <pbonzini>
Status:	CLOSED ERRATA	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	high
Version:	5.4	CC:	clalance, cperry, drjones, pbonzini, riek, sghosh, xen-maint, xinsun
Target Milestone:	rc	Flags:	riek: needinfo-
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	xen-3.0.3-102.el5	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	540397 (view as bug list)		Environment:
Last Closed:	2010-03-30 08:58:26 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alan Zarembok 2009-05-06 18:03:13 UTC

Description of problem:

In order to implement RHN business rules that support our licensing model for
RHEL guests, we need a method of identifying, from within a guest, whether it
is running on a Red Hat hypervisor platform, and if so which platform (RHEV-H
or RHEL).

The goal of this is to implement a "floating" guest entitlement that allows the
customer to run a RHEL guest on top of one of our hypervisors, but to not allow
that entitlement to be used on bare metal.  We also need to have control over
whether the entitlement can be used on 3rd party hypervisor platforms.

To accomplish this please set the "Manufacturer" and "Product Name" fields in
the guests SMBIOS as follows:

Manufacturer: "Red Hat, Inc."
Product Name: "Red Hat Enterprise Linux"

This applies to both Xen and KVM guests.


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


How reproducible:
N/A

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


Expected results:


Additional info:

Comment 13 Paolo Bonzini 2009-12-29 12:07:43 UTC

See patch comment:

"This patch customizes the manufacturer and family in the guest
SMBIOS to be respectively "Red Hat" and "Red Hat Enterprise Linux".  This is not exactly what is asked for in the Bugzilla, but I chose to
match the strings and fields that KVM is already using."

Red Hat Enterprise Linux should be in the family, not in the product.

Comment 16 Paolo Bonzini 2009-12-29 19:36:55 UTC

That's on RHEV.  RHEL's kvm/bios/rombios32.c has

    load_str_field_with_default(1, manufacturer_str, "Red Hat");
    load_str_field_with_default(1, product_name_str, "KVM");
...
    load_str_field_with_default(1, family_str, "Red Hat Enterprise Linux");

So I did the same for Xen.

Comment 21 Paolo Bonzini 2010-01-02 13:19:17 UTC

I guess the "Intel" manufacturer is for the processor?  If so, that is fine.

Comment 23 XinSun 2010-01-05 06:05:28 UTC

Do follow steps to check this bug with xen-3.0.3-102.el5：
[guest]# dmidecode | grep Manufacturer
        Manufacturer: Red Hat 
        Manufacturer: Red Hat
        Manufacturer: Intel

[guest]# dmidecode | grep Family
        Family: Red Hat Enterprise Linux  

So this bug is fixed on xen-3.0.3-102.el5, change this bug's status to verified.

Comment 25 Paolo Bonzini 2010-01-05 16:39:48 UTC

> * The "Product Name" field must identify the the individual member of the
product family.
> * "Serial Number" must be a unique ID for the host
> * "UUID" must be the UUID of the individual guest

Thanks.  These parts are not implemented yet, as far as I can tell, for either Xen or KVM.  I could find no open bug.

Comment 29 errata-xmlrpc 2010-03-30 08:58:26 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2010-0294.html

Comment 30 Paolo Bonzini 2010-04-08 15:45:35 UTC

This bug was closed during 5.5 development and it's being removed from the internal tracking bugs (which are now for 5.6).