Hide Forgot
Description of problem: Mouse stuck after restore of PV guest but buttons are in working condition. cat /proc/interrupts - shows that vkbd receives mouse motion events but userspace test http://people.freedesktop.org/~whot/evtest.c is blocked on reading from mouse event device. So events kind of lost in PV kernel. Version-Release number of selected component (if applicable): kernel-2.6.38.2-9.fc15.x86_64 How reproducible: reproducible always. Steps to Reproduce: 1. boot PV guest to GDM login screen. 2. save the guest: virsh save guest guest.dump, then restore guest: virsh restore guest.dump. 3. put mouse pointer back to guest's vnc window and try to move mouse. 4. as result mouse doesn't move any more till the guest is rebooted Actual results: mouse doesn't move any more till the guest is rebooted Expected results: mouse move pointer after guest restore. Additional info:
Attempted to run FC13 PV guest on RHEL5. Mouse works as expected after resume. So it looks like regression.
Created attachment 492126 [details] Driver on restore should ask xen for request-abs-pointer again if it's available If driver has been configured for ABS coordinates at start it will get XENKBD_TYPE_POS events and then suddenly after restore it'll start getting XENKBD_TYPE_MOTION events, that will be dropped later and they won't get into user-space. Regression was introduced by hunk 5 and 6 of 5ea5254. Driver on restore should ask xen for request-abs-pointer again if it's available.
The upstream git commit is c36b58e8a9112017c2bcc322cc98e71241814303.
assigning to justin for integration
This is fixed in 2.6.38.5