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:
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.
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.
I guess the "Intel" manufacturer is for the processor? If so, that is fine.
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.
> * 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.
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
This bug was closed during 5.5 development and it's being removed from the internal tracking bugs (which are now for 5.6).