| Summary: | using qemu/kvm with spice, mouse doesn't work after saving and restoring | ||
|---|---|---|---|
| Product: | Spice | Reporter: | Brian J. Murrell <brian> |
| Component: | spicec (deprecated) | Assignee: | Spice Bug List <spice-bugs> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | major | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Brian J. Murrell
2013-03-05 12:53:05 UTC
Have you installed some specific drivers in the guest? If so, which version? (In reply to comment #1) > Have you installed some specific drivers in the guest? Drivers for what? I have done nothing except install Windows. I am sure that this save/resume has resulted in a working mouse in the past but that might have been before I switched to spice. I have not added any new drivers to my Win7 since I installed it so it's the same now as it was when I recall this having worked. Is there any tests I can carry out to help diagnose? (In reply to comment #2) > (In reply to comment #1) > > Have you installed some specific drivers in the guest? > > Drivers for what? I have done nothing except install Windows. Virtio drivers, qxl drivers, ... but it seems you don't have that. So yeah. Just did a test. Removed the SPICE display and created a VNC display. The mouse cursor survives the save/resume cycle. But wow. I'm remembering now why I switched to spice. The VNC display is yukky. :-/ (In reply to comment #3) > (In reply to comment #2) > > (In reply to comment #1) > > > Have you installed some specific drivers in the guest? > > > > Drivers for what? I have done nothing except install Windows. > > Virtio drivers, qxl drivers, ... but it seems you don't have that. Ahhh. I understand what you mean now. So yes, I do have some guest drivers installed: Red Hat QXL GPU: 05/10/2011 6.1.0.10012 Red Hat VirtIO Ethernet Adapter: 03/07/2012 61.63.103.3000 Red Hat VirtIO SCSI Disk Device: 12/06/2006 6.1.7600.16385 (In reply to comment #5) > (In reply to comment #3) > > (In reply to comment #2) > > > (In reply to comment #1) > > > > Have you installed some specific drivers in the guest? > > > > > > Drivers for what? I have done nothing except install Windows. > > > > Virtio drivers, qxl drivers, ... but it seems you don't have that. > > Ahhh. I understand what you mean now. So yes, I do have some guest drivers > installed: > > Red Hat QXL GPU: 05/10/2011 6.1.0.10012 > Red Hat VirtIO Ethernet Adapter: 03/07/2012 61.63.103.3000 > Red Hat VirtIO SCSI Disk Device: 12/06/2006 6.1.7600.16385 No vioserial driver? They seem to be fairly old versions, can you try to update them? OK. Updated to spice-guest-tools-0.52.exe. That updated the installed drivers to: Red Hat QXL GPU: 15/10/2012 6.1.0.10016 Red Hat VirtIO Ethernet Adapter: 22/01/2013 61.64.104.5200 Red Hat VirtIO SCSI Disk Device: 21/06/2006 6.1.7600.16385 Red Hat VirtIO SCSI controller: 22/01/2013 61.64.104.5200 I rebooted and then tried to save/resume again. Sadly, no change. I was not holding my breath given the very small delta of the QXL GPU driver update. That's a one year delta, not too bad ;) Once again, do you have a vioserial driver? (In reply to comment #8) > That's a one year delta, not too bad ;) Yeah. I was more looking at the version number bump which looked pretty minor. > Once again, do you have a vioserial driver? Ahhh. Sorry. I didn't realize you were looking for that specifically and thought you were just using it as a measure of how old my driver package was in general. But no, I don't see any virtioserial driver, assuming I am looking in the correct place. I have opened the device manager and am looking at the tree of hardware/drivers. There does appear to be a Communications Port (COM1) but it has a Microsoft COM1 driver attached, not a virtioserial. (In reply to comment #9) > But no, I don't see any virtioserial driver, assuming I am looking in the > correct place. I have opened the device manager and am looking at the tree > of hardware/drivers. There does appear to be a Communications Port (COM1) > but it has a Microsoft COM1 driver attached, not a virtioserial. virtioserial appears in the device manager as a 'system device' (rough translation from French) and is called VirtIO-Serial driver. It's not listed as a serial and communication port. Ahhh. So yes, then I do have: VirtIO-Serial Driver, 22/01/2013 61.64.104.5200 Any more ideas/thoughts on what the problem could be? I'd try uninstalling the vioserial driver (will break copy&paste), this may help (at least we will know what's broken). spicec is deprecated. If you hit this bug, we highly recommended virt-viewer http://virt-manager.org/download/ http://www.spice-space.org/download.html |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.