Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 1052166[details]
gdb info
Description of problem:
virt-viewer window crashes after restart libvirtd in remote host
Version-Release number of selected component (if applicable):
Host A: 10.66.5.58
# rpm -qa | grep spice
spice-glib-0.26-4.el7.x86_64
spice-gtk3-0.26-4.el7.x86_64
spice-server-0.12.4-12.el7.x86_64
spice-vdagent-0.14.0-10.el7.x86_64
# rpm -q virt-viewer
virt-viewer-2.0-4.el7.x86_64
Host B: 10.66.5.44
# rpm -q libvirt
libvirt-0.10.2-54.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Config ssh( so that host A can login host B without password.)
# ssh-keygen
# ssh-copy-id .ssh/id_rsa.pub root.5.44
2. Make sure guest rhel6u7_spice is shutdown state and Run "virt-viewer -c qemu+ssh://10.66.5.44/system rhel6u7_spice --wait" on host A, and then a "Waiting for guest domain to start" window pops up.
3. Restart libvirtd on Host B. (Must only run "service libvirtd restart one time, i cannot reproduce it after restart libvirtd more than one times continuously.)
# service libvirtd restart
4. Click gnome-terminal window and wait several seconds (the virt-viewer window won't crash if do nothing after step3).
Actual results:
virt-viewer windows crashes
Expected results:
virt-viewer should not crash.
Additional info:
Moving it back to virt-viewer.
After adopting a similar approach (for handling libvirt events/mainloop integration) than the one used by libvirt-glib, xiaodwan tested http://brewweb.devel.redhat.com/brew/taskinfo?taskID=9534079 and said he was not able to reproduce the crash anymore.
Verified it with latest build:
virt-viewer-2.0-5.el7.x86_64
Steps to Reproduce:
1. Config ssh( so that host A can login host B without password.)
# ssh-keygen
# ssh-copy-id .ssh/id_rsa.pub root.5.44
2. Make sure guest rhel6u7_spice is shutdown state and Run "virt-viewer -c qemu+ssh://10.66.5.44/system rhel6u7_spice --wait" on host A, and then a "Waiting for guest domain to start" window pops up.
3. Restart libvirtd on Host B. (Must only run "service libvirtd restart one time, i cannot reproduce it after restart libvirtd more than one times continuously.)
# service libvirtd restart
4. Close the virt-viewer windown.
Actual Result:
No segment fault occurs.
So move it to verified.
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-2211.html
Created attachment 1052166 [details] gdb info Description of problem: virt-viewer window crashes after restart libvirtd in remote host Version-Release number of selected component (if applicable): Host A: 10.66.5.58 # rpm -qa | grep spice spice-glib-0.26-4.el7.x86_64 spice-gtk3-0.26-4.el7.x86_64 spice-server-0.12.4-12.el7.x86_64 spice-vdagent-0.14.0-10.el7.x86_64 # rpm -q virt-viewer virt-viewer-2.0-4.el7.x86_64 Host B: 10.66.5.44 # rpm -q libvirt libvirt-0.10.2-54.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. Config ssh( so that host A can login host B without password.) # ssh-keygen # ssh-copy-id .ssh/id_rsa.pub root.5.44 2. Make sure guest rhel6u7_spice is shutdown state and Run "virt-viewer -c qemu+ssh://10.66.5.44/system rhel6u7_spice --wait" on host A, and then a "Waiting for guest domain to start" window pops up. 3. Restart libvirtd on Host B. (Must only run "service libvirtd restart one time, i cannot reproduce it after restart libvirtd more than one times continuously.) # service libvirtd restart 4. Click gnome-terminal window and wait several seconds (the virt-viewer window won't crash if do nothing after step3). Actual results: virt-viewer windows crashes Expected results: virt-viewer should not crash. Additional info: