Red Hat Bugzilla – Bug 1247926
Guest's "active" status is 0 when suspend guest
Last modified: 2016-11-30 19:33:59 EST
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:
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?
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
Actually,In RHEL5.11, it also show active:1 when guest is suspend
Fixed in virt-who-0.14-4.el7.
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.
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