This issue has been addressed upstream and will be part of rebased virt-who package.

Fixed by rebase to virt-who-0.16-1.el6.

Verified it on virt-who-0.16-4.el6.noarch since virt-who can report guest's attribute and state on all supported hypervisors. Therefore, verify it.

Verified version:
subscription-manager-1.16.8-2.el6.x86_64
python-rhsm-1.16.6-1.el6.x86_64
virt-who-0.16-3.el6.noarch

Verified process:
1. Register to Satellite
2. Configure virt-who run at libvirt mode.restart virt-who service and track virt-who's log,it can show guest's state on the log.
2016-02-23 02:43:09,587 [virtwho.main INFO] MainProcess(10746):MainThread @subscriptionmanager.py:sendVirtGuests:147 - Sending update in guests lists for config "env/cmdline": 1 guests found
2016-02-23 02:43:09,588 [virtwho.main DEBUG] MainProcess(10746):MainThread @subscriptionmanager.py:sendVirtGuests:148 - Domain info: [
    {
        "guestId": "01ce7fd6-8d99-1ce4-39b6-2ed71ce8cd1a", 
        "state": 5, 
        "attributes": {
            "active": 0, 
            "hypervisorVersion": "0.12.1", 
            "virtWhoType": "libvirt", 
            "hypervisorType": "QEMU"
        }
    }
]
3.Configure virt-who run at esx mode.restart virt-who service and track virt-who's log,it can show guest's state on the log.
2016-02-23 02:57:16,626 [virtwho.main INFO] MainProcess(10061):MainThread @subscriptionmanager.py:hypervisorCheckIn:185 - Sending update in hosts-to-guests mapping for config "test-esx1": 8 hypervisors and 7 guests found
2016-02-23 02:57:16,628 [virtwho.main DEBUG] MainProcess(10061):MainThread @subscriptionmanager.py:hypervisorCheckIn:186 - Host-to-guest mapping: {
    "aee4ff00-8c33-11e2-994a-6c3be51d959a": [ 
        {
            "guestId": "4209a518-e1de-ecf2-6625-faacc5b052c2", 
            "state": 5, 
            "attributes": {
                "active": 0, 
                "hypervisorVersion": "6.0.0", 
                "virtWhoType": "esx", 
                "hypervisorType": "VMware ESXi"
            }
        }
    ], 
4. Configure virt-who run at rhevm mode.restart virt-who service and track virt-who's log,it can show guest's state on the log.
2016-02-22 20:39:18,870 [virtwho.main INFO] MainProcess(11365):MainThread @subscriptionmanager.py:hypervisorCheckIn:185 - Sending update in hosts-to-guests mapping for config "env/cmdline": 2 hypervisors and 1 guests found
2016-02-22 20:39:18,870 [virtwho.main DEBUG] MainProcess(11365):MainThread @subscriptionmanager.py:hypervisorCheckIn:186 - Host-to-guest mapping: {
    "5ee2a067-23e6-460d-ad7b-219af51a2aeb": [
        {
            "guestId": "c8211c02-7b29-4115-8115-72c52a8332a7",
            "state": 5,
            "attributes": {
                "active": 0,
                "hypervisorVersion": "",
                "virtWhoType": "rhevm",
                "hypervisorType": "qemu"
            }
        }
    ]
5. Configure virt-who run at hyperv mode.restart virt-who service and track virt-who's log,it can show guest's state on the log.
2016-02-23 03:00:44,968 [virtwho.main DEBUG] MainProcess(10145):MainThread @subscriptionmanager.py:hypervisorCheckIn:186 - Host-to-guest mapping: {
    "564D80F1-61F0-8510-87BF-57F9EC6122D7": [
        {
            "guestId": "8329390B-8359-F646-9176-27D738580E81", 
            "state": 1, 
            "attributes": {
                "active": 1, 
                "hypervisorVersion": "6.3.9600.16404", 
                "virtWhoType": "hyperv", 
                "hypervisorType": "hyperv"
            }
        }
    ]
}

Result:
virt-who can report guest's state and attribute on all supported hypervisor.

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/RHEA-2016-0859.html