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 1091292 - virt-manager doesn't show the right guest status when guest is pmsuspended
Summary: virt-manager doesn't show the right guest status when guest is pmsuspended
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-manager
Version: 6.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Giuseppe Scrivano
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-25 10:17 UTC by Shanzhi Yu
Modified: 2014-10-14 06:26 UTC (History)
7 users (show)

Fixed In Version: virt-manager-0.9.0-20.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-14 06:26:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1447 0 normal SHIPPED_LIVE virt-manager bug fix and enhancement update 2014-10-14 01:05:46 UTC

Description Shanzhi Yu 2014-04-25 10:17:47 UTC 
Description of problem:

virt-manager doesn't show the right guest status when guest is pmsuspended

Version-Release number of selected component (if applicable):

virt-manager-0.9.0-19.el6.x86_64
libvirt-0.10.2-33.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.424.el6.x86_64


How reproducible:
100%

Steps to Reproduce:

1.prepare an guest with confirmation as below, and install qemu-guest-agent inside guest
..
  <pm>
    <suspend-to-mem enabled='yes'/>
    <suspend-to-disk enabled='yes'/>
  </pm>
..
 <channel type='unix'>
      <source mode='bind' path='/var/lib/libvirt/qemu/guest.agent'/>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <alias name='channel0'/>
      <address type='virtio-serial' controller='0' bus='0' port='2'/>
    </channel>
..

2.login guest and start qemu-ga service

3. Do S3 and check the guest status with virt-manager

#virsh dompmsuspend rhel6 --target mem
Domain rhel6 successfully suspended

# virsh list
 Id    Name                           State
----------------------------------------------------
 13    rhel6                          pmsuspended




Actual results:

virt-manager show guest is running status

Expected results:

virt-manager should show guest is paused status

Additional info:

Traceback (most recent call last):                                                        
  File "/usr/share/virt-manager/virtManager/manager.py", line 863, in vm_status_changed  
    self.vm_resources_sampled(vm)                                                        
  File "/usr/share/virt-manager/virtManager/manager.py", line 875, in vm_resources_sampled
    row[ROW_STATUS_ICON] = vm.run_status_icon_name()                                      
  File "/usr/share/virt-manager/virtManager/domain.py", line 1450, in run_status_icon_name
    return status_icons[self.status()]                                                    
KeyError: 7                                                                              
2014-04-25 06:03:14,297 (cli:85): Traceback (most recent call last):                      
  File "/usr/share/virt-manager/virtManager/details.py", line 1354, in refresh_vm_state  
    self.vm.run_status())                                                                
TypeError: Gtk.Label.set_text() argument 1 must be string, not None                      
None
Comment 3 zhoujunqin 2014-05-05 03:01:53 UTC 
I can reproduce this with package:
virt-manager-0.9.0-19.el6.x86_64

verify with :
virt-manager-0.9.0-20.el6.x86_64

verify steps:
1.prepare an guest with configuration as below, and install qemu-guest-agent inside guest
..
  <pm>
    <suspend-to-mem enabled='yes'/>
    <suspend-to-disk enabled='yes'/>
  </pm>
..
 <channel type='unix'>
      <source mode='bind' path='/var/lib/libvirt/qemu/guest.agent'/>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <alias name='channel0'/>
      <address type='virtio-serial' controller='0' bus='0' port='2'/>
    </channel>
..

2.login guest and start qemu-ga service
# service qemu-ga start

3. Do S3 on guest
# virsh dompmsuspend rr66 --target mem
Domain rr66 successfully suspended

# virsh domstate rr66 --reason
pmsuspended (unknown)

4.From virt-manager GUI,check the status of the guest.
guest is in "Suspended" status.

And guest can be wakeup successfully.
# virsh dompmwakeup rr66
Domain rr66 successfully woken up

Refer to the above comments,move the bug to VERIFIED.
Comment 4 errata-xmlrpc 2014-10-14 06:26:35 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.

http://rhn.redhat.com/errata/RHBA-2014-1447.html
Note You need to log in before you can comment on or make changes to this bug.