This feature has been implemented upstream:

https://github.com/virt-who/virt-who/commit/f6bed0f683c287c6cbea262978db74c9875bc840

*** Bug 1097580 has been marked as a duplicate of this bug. ***

*** Bug 1171895 has been marked as a duplicate of this bug. ***

Fixed in virt-who-0.12-2.el6.

How to test:

set 'hypervisor_id = hostname' in config file in /etc/virt-who.d/* and ensure that hostname appears in the UI instead of UUID of the hypervisor.

Verified it on virt-who-0.12-2.el6

Verified version:
virt-who-0.12-2.el6.noarch
subscription-manager-1.14.1-1.el6.x86_64
python-rhsm-1.14.1-1.el6.x86_64
candlepin-0.9.6.5-1.el6sam.noarch
katello-headpin-1.4.3.28-1.el6sam_splice.noarch

Verified process:
1. Register system to SAM/Satellite server.
2. Configure virt-who run at esx mode and send the hostname to SAM/Satellite 
server.then restart virt-who service
[root@hp-z220-03 ~]# cat /etc/virt-who.d/virt
[test-esx1]
type=esx
server=10.66.79.68
username=Administrator
password=qwer1234P!
owner=ACME_Corporation
env=Library
hypervisor_id=hostname
[root@hp-z220-03 ~]# service virt-who restart
Stopping virt-who:                                         [FAILED]
Starting virt-who:                                         [  OK  ]
3. Check the virt-who's log,
# tail -f /var/log/rhsm/rhsm.log
2015-04-14 17:11:50,156 [DEBUG]  @virtwho.py:84 - Using config named 'test-esx1'
2015-04-14 17:11:50,157 [INFO]  @virtwho.py:475 - Using configuration "test-esx1" ("esx" mode)
2015-04-14 17:11:50,157 [DEBUG]  @virtwho.py:131 - Starting infinite loop with 5 seconds interval
2015-04-14 17:11:50,306 [DEBUG]  @esx.py:51 - Log into ESX
2015-04-14 17:11:51,475 [DEBUG]  @esx.py:54 - Creating ESX event filter
2015-04-14 17:11:51,796 [DEBUG]  @esx.py:113 - Waiting for ESX changes
2015-04-14 17:11:51,813 [INFO]  @subscriptionmanager.py:124 - Sending update in hosts-to-guests mapping: {10.66.128.77: [4224a77f-1c50-42cb-3507-2b68b447ed60, 4224e5d2-4fcf-2bc2-2559-5846035d3a78], 10.66.128.10: []}
2015-04-14 17:11:51,814 [DEBUG]  @subscriptionmanager.py:76 - Authenticating with certificate: /etc/pki/consumer/cert.pem
2015-04-14 17:11:52,943 [INFO]  @virtwho.py:127 - Created host: 9f52c393-9b5b-447b-8787-4c6ace333c7d with guests: [4224a77f-1c50-42cb-3507-2b68b447ed60, 4224e5d2-4fcf-2bc2-2559-5846035d3a78]
2015-04-14 17:11:52,944 [INFO]  @virtwho.py:127 - Created host: 0371e977-2433-4bb4-9d8b-e5a10e2b194c with guests: []
4. Check the SAM/Satellite web UI, It will show esx hostname instead of uuid on it.

Result:According to the result on step3 and step4, virt-who can send the hostname instead of uuid to server, therefor, verify it.

Dear all,

we have tested it on Satellite 6 with RHEL6. We wanted to test with RHEL7 which provides 0.13-1.el7sat, but this doesn't have the required support for hypervisor_id.

Does a version for RHEL7 exist?

It will be in RHEL-7.2 once it's released. It the meantime I can provide you testing rpm if you're interested.

Hi Radek,

we'd be interested in testing rpms for RHEL7 and RHEL6 and we'd also like to take this up for GSS (which is off-topic for this bugzilla). Let me PM you on details.

Thanks!

Yes, there will be new configuration option `hypervisor_id` and if set to `hostname`, the hypervisor will be identified using hostname instead of uuid. Please note that if this options is changed after initial run, it will create duplicated hypervisor entries (because the only identification will change and the server can't match those two entries toghether).

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-1377.html

*** Bug 1065465 has been marked as a duplicate of this bug. ***