Bug 688572

Summary: spice-server does not switch back to server mouse mode if guest spice-agent dies.
Product: Red Hat Enterprise Linux 6 Reporter: Hans de Goede <hdegoede>
Component: qemu-kvmAssignee: Hans de Goede <hdegoede>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1CC: alevy, dblechte, ehabkost, juzhang, mkenneth, mkrcmari, spice-qe-bugs, tburke, virt-maint
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: qemu-kvm-0.12.1.2-2.153.el6 Doc Type: Bug Fix
Doc Text:
Cause: spice-server no longer switched back to server mouse mode if the guest spice-agent died. Consequence: non functional mouse if the guest spice-agent dies. Fix: made virtio-console notify spice-chardev of guest open / close. Consequence: mouse is functional even if spice-agent is stopped in the guest.
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-19 11:21:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Hans de Goede 2011-03-17 11:44:30 UTC
The spice-server no longer switches back to server mouse mode if the guest spice-agent dies. This leads to a non functional mouse if the guest spice-agent dies.

Comment 2 Marian Krcmarik 2011-03-17 15:47:45 UTC
I was able to reproduce with Windows7 guest. After windows agent process got stuck mouse mode wasn't switched to server mode and It was not able to click with mouse.

Comment 3 Hans de Goede 2011-03-18 15:02:37 UTC
We've a fix for this, adding devel ack.

Comment 4 Hans de Goede 2011-03-22 13:46:15 UTC
This actual cause of this problem is inside of qemu, not spice-server. Patches have been posted to rhvirt-patches, changing component.

Comment 9 juzhang 2011-04-10 07:50:42 UTC
Reproduced with qemu-kvm-tools-0.12.1.2-2.152.el6.x86_64.

steps:
1. /usr/libexec/qemu-kvm -m 2G -smp 4 -drive
file=/root/zhangjunyi/rhel6.1-64.qcow2,if=none,id=test,cache=none,format=qcow2,werror=stop,rerror=stop
-device virtio-blk-pci,drive=test -cpu qemu64,+sse2,+x2apic -boot c -netdev
tap,id=hostnet0,vhost=on -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=22:11:22:45:66:94 -spice
port=5930,disable-ticketing -vga qxl -serial stdio -qmp
tcp:0:4444,server,nowait -usb -device virtio-serial-pci,id=virtio-serial1
-chardev spicevmc,id=charchannel0,name=vdagent -device
virtserialport,bus=virtio-serial1.0,nr=3,chardev=charchannel0,id=channel0,name=com.redhat.spice.0
-soundhw ac97

2. in guest.
#stop spice-vdagentd service

Results:
mouse lost.

Verified with qemu-kvm-tools-0.12.1.2-2.156.el6.x86_64.

Resutls:
After step2,mouse works well.

Comment 10 juzhang 2011-04-10 07:51:27 UTC
According to comment9,set this issue status as verified.

Comment 11 Eduardo Habkost 2011-05-03 19:06:09 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause: spice-server no longer switched back to server mouse mode if the guest spice-agent died.

Consequence: non functional mouse if the guest spice-agent dies.

Fix: made virtio-console notify spice-chardev of guest open / close.

Consequence: mouse is functional even if spice-agent is stopped in the guest.

Comment 12 errata-xmlrpc 2011-05-19 11:21:02 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2011-0534.html

Comment 13 errata-xmlrpc 2011-05-19 13:02:26 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2011-0534.html