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 1287462 - virt-viewer will core dump with -r option via ssh when destroy the guest
Summary: virt-viewer will core dump with -r option via ssh when destroy the guest
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-viewer
Version: 6.8
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Virt Viewer Maint
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1163647 1181288
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-02 07:38 UTC by mxie@redhat.com
Modified: 2016-05-10 21:19 UTC (History)
9 users (show)

Fixed In Version: virt-viewer-2.0-8.el6
Doc Type: Bug Fix
Doc Text:
Clone Of: 1163647
Environment:
Last Closed: 2016-05-10 21:19:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0832 0 normal SHIPPED_LIVE libgovirt, spice-gtk, usbredir, and virt-viewer bug fix update 2016-05-10 22:41:23 UTC

Comment 2 Fabiano Fidêncio 2015-12-02 07:54:37 UTC 
The upstream commit that should solve this issue is:
30b7e299b09f78ace49f8802a16020b6682ecf48
Comment 4 mxie@redhat.com 2015-12-15 08:53:13 UTC 
I can reproduce the bug on spice guest with builds:
virt-viewer-2.0-7.el6.x86_64

Try to verify this bug with builds:
virt-viewer-2.0-8.el6.x86_64

Steps:
Test with spice guest

1. Prepare a running spice guest on host A

# virsh dumpxml test
...
    <graphics type='spice' port='5900' autoport='yes' listen='127.0.0.1'>
      <listen type='address' address='127.0.0.1'/>
      <image compression='off'/>
    </graphics>
...
     <video>
      <model type='qxl' ram='65536' vram='65536' heads='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>


2. On host B, use virt-viewer connect to guest on host A.
# virt-viewer -c qemu+ssh://$host_A_ip/system test -r

Result: Connect to guest on host A successfully.

3. destroy the guest on host A

# virsh destroy test
Domain test destroyed

Result: Virt-viewer window keeps on host B and showing: "Waiting for guest domain to re-start", no crash.

4. Start guest on host A again:

# virsh start test
Domain test started

Result: Virt-viewer window keeeps and reconnect to guest automatically, showing guest boot up process with no crash.


Seen above steps, move this bug from ON_QA to VERIFIED.
Comment 6 errata-xmlrpc 2016-05-10 21:19:13 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-2016-0832.html
Note You need to log in before you can comment on or make changes to this bug.