On the rhel7.1, the version of component should be as the following:

subscription-manager-1.13.5-1.el7.x86_64
python-rhsm-1.13.5-1.el7.x86_64
virt-who-0.11-2.el7.noarch
katello-headpin-1.4.3.28-1.el6sam_splice.noarch
candlepin-0.9.6.5-1.el6sam.noarch

It's a little bit more complicated now, virt-who can now has more than one backend enabled.

I would suggest following info output for each config:

Using configuration "<name>" ("<mode>" mode).

For example:
Using configuration "esx test" ("esx" mode).
Using configuration "hyperv test" ("hyperv" mode).
Using commandline or sysconfig configuration ("libvirt" mode).

Is this agreeable? Suggestions of better format welcomed :)

I agree with your idea, I think it's clear. Thanks.

Fixed in virt-who-0.11-3.el7.

Verified it on virt-who-0.11-3.el7.noarch

Verified process
1. Register system to SAM server
2. Configure virt-who run at libvirt mode
3. Check virt-who 's log , it will show virt-who run at (libvirt mode):
2014-11-12 16:45:23,914 [INFO]  @virtwho.py:453 - No configurations found, using libvirt as backend
2014-11-12 16:45:23,914 [INFO]  @virtwho.py:460 - Using configuration "virt-who" ("libvirt" mode)
2014-11-12 16:45:23,914 [DEBUG]  @virtwho.py:170 - Starting infinite loop with 5 seconds interval
2014-11-12 16:45:23,950 [DEBUG]  @libvirtd.py:95 - Starting libvirt monitoring event loop
2014-11-12 16:45:23,951 [INFO]  @libvirtd.py:187 - Using libvirt url: ""
2014-11-12 16:45:24,066 [INFO]  @subscriptionmanager.py:109 - Sending list of uuids: []
4.Configure virt-who run at esx mode.
5.Check the virt-who's log, it will show virt-who run at (esx mode):
2014-11-12 16:46:54,386 [INFO]  @virtwho.py:458 - Using commandline or sysconfig configuration ("esx" mode)
2014-11-12 16:46:54,387 [DEBUG]  @virtwho.py:170 - Starting infinite loop with 5 seconds interval

As virt-who can show the run mode in the log, verify it in this version.

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/RHSA-2015-0430.html