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 1247926 - Guest's "active" status is 0 when suspend guest
Summary: Guest's "active" status is 0 when suspend guest
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-who
Version: 7.2
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Radek Novacek
QA Contact: xingge
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-29 09:15 UTC by Liushihui
Modified: 2016-12-01 00:33 UTC (History)
6 users (show)

Fixed In Version: virt-who-0.14-4.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 11:57:37 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 Liushihui 2015-07-29 09:15:29 UTC 
Description of problem:
When suspend guest, check the guest's active status, it's ""active": 0"

Version-Release number of selected component (if applicable):
virt-who-0.14-2.el7.noarch
subscription-manager-1.15.6-1.el7.x86_64
python-rhsm-1.15.3-1.el7.x86_64
Satellite-6.1.0-RHEL-7-20150721.7

How reproducible:
Always

Steps to Reproduce:
1.Register system to satellite, start guest.
2.Configure virt-who run at kvm mode and restart virt-who service
3.Check virt-who's log
2015-07-27 10:35:06,150 [INFO]  @subscriptionmanager.py:136 - Sending domain info: [
    {
        "guestId": "2c8198c2-8e26-4d70-89fb-9eaaf67aaf47", 
        "state": 1, 
        "attributes": {
            "active": 1, 
            "virtWhoType": "libvirt", 
            "hypervisorType": "QEMU"
        }
    }]
4. Suspend guest, then check virt-who service

Actual results:
2015-07-27 10:35:06,150 [INFO]  @subscriptionmanager.py:136 - Sending domain info: [
    {
        "guestId": "2c8198c2-8e26-4d70-89fb-9eaaf67aaf47", 
        "state": 3, 
        "attributes": {
            "active": 0, ====================================it should be "1"
            "virtWhoType": "libvirt", 
            "hypervisorType": "QEMU"
        }
    }]

Expected results:
Guest's active status should be "1" after suspend it.

Additional info:
Comment 1 Radek Novacek 2015-08-04 13:03:24 UTC 
Why do you think that the active status of suspended guest should be "1"?

There might be two points of view that can affect perception of this:

* I'm concerned about what's running on that VM (a service), in that case I consider only the state `RUNNING` as `active`. That's current virt-who behaviour

* I'm concerned about the system where is the VM running, meaning that the suspended machine is `active` because it consumes resources of given system (at least RAM).

Both of them are valid but I don't know to what group we should put virt-who. Do you know if this information is used anywhere?
Comment 2 Liushihui 2015-08-13 02:37:20 UTC 
Radek, I'm sorry I haven't found doc about this function. and I agree with you that both of them are valid. However, I think it should be better to set active:1 when guest in suspend status. Since if we try to start guest when it in suspend status, it will remind info "error: Domain is already active". is that acceptable?

[root@ibm-x3250m4-03 ~]# virsh suspend 6.5_Server_x86_64
Domain 6.5_Server_x86_64 suspended

[root@ibm-x3250m4-03 ~]# virsh start 6.5_Server_x86_64
error: Domain is already active
Comment 3 Liushihui 2015-08-13 02:43:34 UTC 
Actually,In RHEL5.11, it also show active:1 when guest is suspend
Comment 4 Radek Novacek 2015-08-18 15:56:27 UTC 
Fixed in virt-who-0.14-4.el7.
Comment 6 Liushihui 2015-08-24 05:55:49 UTC 
Verified it on virt-who-0.14-4.el7.noarch since guest show active:1 when guest is suspend.

Verified version
virt-who-0.14-4.el7.noarch
subscription-manager-1.15.9-6.el7.x86_64
python-rhsm-1.15.4-2.el7.x86_64

Verified process:
1.Register system to satellite, start guest.
2.Configure virt-who run at kvm mode and restart virt-who service
3.Suspend guest, then check virt-wh's log
    {
        "guestId": "6641c133-ebfa-4ca7-8ddb-f9100a6b02fa", 
        "state": 3, 
        "attributes": {
            "active": 1, 
            "virtWhoType": "libvirt", 
            "hypervisorType": "QEMU"
        }
    }

Result:
Guest's active status is "1" after suspend it.
Comment 7 errata-xmlrpc 2015-11-19 11:57:37 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.