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.
Bug 1056419 - Support reporting state of virtual machines on all known hypervisors
Summary: Support reporting state of virtual machines on all known hypervisors
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-who
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Radek Novacek
QA Contact: gaoshang
URL:
Whiteboard:
Depends On:
Blocks: 1231065
TreeView+ depends on / blocked
 
Reported: 2014-01-22 08:00 UTC by Radek Novacek
Modified: 2016-12-01 00:33 UTC (History)
5 users (show)

Fixed In Version: virt-who-0.14-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1231065 (view as bug list)
Environment:
Last Closed: 2015-11-19 11:55:45 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2370 0 normal SHIPPED_LIVE virt-who bug fix and enhancement update 2015-11-19 10:39:27 UTC

Description Radek Novacek 2014-01-22 08:00:16 UTC
virt-who should be able to report which virtual guests are active. The support for this on local libvirt is already in virt-who but it would be nice if virt-who can report it for all known hypervisors.

See related bug 1048954 that requests libvirt support for this feature.

Comment 1 Radek Novacek 2014-09-02 14:21:39 UTC
This feature is quite complex and needs more time to do it for all the backends in virt-who, moving to 7.2.

Comment 3 Radek Novacek 2015-06-18 12:20:54 UTC
There is now support for reporting state of guests for all hypervisors in the upstream repository. It will be part of virt-who rebase in RHEL-7.2.

Comment 4 Radek Novacek 2015-06-23 13:31:49 UTC
Fixed in virt-who-0.14-1.el7.

Comment 6 Liushihui 2015-07-16 02:50:36 UTC
verified it on virt-who-0.14-1.el7.noarch since virt-who can report guest's attribute and state on all supported hypervisors. Therefore, verify it.

Verified version:
virt-who-0.14-1.el7.noarch
subscription-manager-1.15.5-1.el7.x86_64
python-rhsm-1.15.3-1.el7.x86_64

Verify process:
1. Register to Satellite
2. 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.

2015-07-16 10:35:52,317 [INFO]  @subscriptionmanager.py:146 - Sending update in hosts-to-guests mapping: {
    "564d9e7a-4128-92b6-7284-6335f6b399be": [], 
    "aee4ff00-8c33-11e2-994a-6c3be51d959a": [
        {
            "attributes": {
                "active": 0, 
                "virtWhoType": "esx"
            }, 
            "guestId": "564dab7d-3b72-51a1-eeda-586036106892", 
            "state": 5
        }, 

3. 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.
2015-07-16 10:22:18,769 [INFO]  @subscriptionmanager.py:135 - Sending domain info: [
    {
        "attributes": {
            "active": 0, 
            "hypervisorType": "QEMU", 
            "virtWhoType": "libvirt"
        }, 
        "guestId": "0d6a7081-5175-4fd5-98ae-1ddb9c7a9c65", 
        "state": 5
    }, 

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.
2015-07-16 10:38:37,533 [INFO]  @subscriptionmanager.py:146 - Sending update in hosts-to-guests mapping: {
    "a5b6966e-b192-4029-92af-3498f59aabb5": [
        {
            "attributes": {
                "active": 0, 
                "virtWhoType": "rhevm"
            }, 
            "guestId": "2d3cd78f-0e3d-49fe-8d38-a4b13596628e", 
            "state": 3
        }
    ], 
    "c1323f29-1ab2-4633-8c7d-2d7713df316c": []
}

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.
2015-07-16 10:46:01,412 [INFO]  @subscriptionmanager.py:146 - Sending update in hosts-to-guests mapping: {
    "60527517-6284-7593-6AAB-75BF2A6375EF": [
        {
            "attributes": {
                "active": 0, 
                "virtWhoType": "hyperv"
            }, 
            "guestId": "E2EC00E1-5022-2341-93FF-CD68A7BF0324", 
            "state": 5
        }, 

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

Comment 7 errata-xmlrpc 2015-11-19 11:55:45 UTC
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-2370.html


Note You need to log in before you can comment on or make changes to this bug.