The new Subscription Management tooling allows users to understand the specific products which have been installed on their machines, and the specific subscriptions which their machines are consuming.
For virtual guests, the Subscription Manager daemons use dmidecode to read the System Management BIOS (SMBIOS), which is used to retrieve the guest UUID. On 64-bit Intel architecture, the SMBIOS information is controlled by the Intel firmware and stored in a read-only binary entry. Therefore, it is not possible to retrieve the UUID or set a new and readable UUID. Because the guest UUID is unreadable, running the
facts command on the guest system shows a value of
Unknown in the
virt.facts file for the system (
virt.uuid: Unknown). This means that the guest does not have any association with the host machine and, therefore, does not inherit some subscriptions. The facts used by Subscription Manager can be edited manually to add the UUID:
Obtain the guest name or guest ID.
On the virtual host, use virsh to retrieve the guest UUID. For example, for a guest named 'rhel5server_virt1':
virsh domuuid rhel5server_virt1
On the guest, manually create a facts file:
Add a line which contains the given UUID.
facts file and inserting the proper UUID means that Subscription Manager properly identifies the guest rather than using an
Japanese SCIM input-method editor cannot be activated and cannot input locale string in the data field for non-root users. To work around this problem, follow these steps:
Log in to the system as a non-root user.
As root, run the following commands:
~]# export GTK_IM_MODULE=scim-bridge
Using Subscription Manager in the following use case fails: a user installs Red Hat Enterprise Linux Desktop from a Red Hat Enterprise Linux 5.7 Client CD/DVD without an installation number. A user uses Subscription Manager, which finds one Red Hat Enterprise Linux Desktop product ID to subscribe to a Red Hat Enterprise Linux Workstation subscription. A user downloads content from a Workstation repository.
The use case scenario described above fails because the rhel-workstation repositories require the rhel-5-workstation product tag in the product certification beforehand in order to view them.
To work around this issue, follow these steps:
Install a rhel-5-client system.
Mount the ISO to your file system.
<path_to_ISO>/Workstation/repodata/productid to the
/etc/pki/product/ directory, making sure that the file copied ends with
.pem (for example,
Subscribe to a Workstation subscription.
Install a package from a Workstation repository.