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:
From rhnreg.py, get_virt_info():

  1.  Check /proc/xen/xsd_port.  If exists, we know the system is a
      host; exit.
  2.  Check /sys/hypervisor/uuid.  If exists and is non-zero, we know
      the system is a para-virt guest; exit.
  3.  Check SMBIOS.  If vendor='Xen' and UUID is non-zero, we know the
      system is a fully-virt guest; exit.
  4.  If non of the above checks worked; we know we have a
      non-xen-enabled system; exit.

The above logic works fine for RHEL-5 guests (Xen FV / PV, KVM), but will
not work 100% correctly for RHEL-6 FV Xen guests.

RHEL-6 fully virtualized Xen guests do have /sys/hypervisor/uuid file,
which the above logic will incorrectly recognize as paravirtualized
guests.

The simple fix for this problem would be to flip steps 2 and 3.

Version-Release number of selected component (if applicable):
rhn-client-tools-1.0.0-36.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Install RHEL-6 FV Xen guest (on a RHEL-5 Xen host)
2. Register the system to RHN / RHN Satellite
3. Note the virtualization type
  
Actual results:
Paravirtualized guest

Expected results:
Fully virtualized guest

Additional info:
N/A

spacewalk.git master: 2bfb9b5eb73289b2af0e7a843c97677330ff95f1
satellite.git CLIENT-RHEL-6: 248b9672cac4c2ea0d7ddbc55aa04a2b2d9c4967

Verified in rhn-client-tools-1.0.0-48.el6.noarch

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-2011-0565.html