Description of problem: Using qxl in virt-manager, the mouse cursor is not displayed in KDE in Fedora 17 Beta RC3. However, once one logs out of the KDE session, the cursor appears and is visible from that point also after logging into the KDE session again. Version-Release number of selected component (if applicable): 0.0.22-0.fc17.x86_64 How reproducible: Always Steps to Reproduce: 1. Choose qxl in virt-manager 2. Boot and log into KDE 3. Actual results: The mouse cursor is not visible Expected results: The mouse cursor is visible Additional info:
Proposing as F17 Beta blocker, since it makes KDE desktop unusable.
I can't reproduce it as my virt-manager does not want to grab mouse - any hint here?
I can't reproduce with qxl/spice, works fine. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
reproduced with qxl/vnc, which is never a default config.
Updating topic with info provided by bcl. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
> reproduced with qxl/vnc, which is never a default config. We can't assume that in general - since qxl provides basic VGA capabilities when used without SPICE, it is perfectly reasonable to use QXL + VNC. So while virt-manager doesn't do this by default, it is acceptable for apps to enable QXL by default.
Mentioned by adamw in IRC, upstream patch here: http://patchwork.freedesktop.org/patch/9198/
Changing to QEMU on basis of Cole's URL
dberrange: as far as blocker status goes, we mostly consider fedora's 'supported vm stack', which is taken to be virt-manager / libvirt / qemu / kvm. Discussed at 2012-04-05 go/no-go meeting - http://meetbot.fedoraproject.org/fedora-meeting-1/2012-04-05/gono-go_continuation_f17_beta_rc3_part_two_or_three.2012-04-05-15.00.html . We agreed that as the qxl/vnc combination has never been default in the supported stack (see above), it's easy to 'work around' this bug by switching to cirrus/vnc or qxl/spice, and the bug is not in the guest but the host (and so we don't gain much by fixing it in the release images) this bug is rejected as a blocker. It is not accepted as NTH, for the reason that fixing it in the images doesn't actually change much. Anyone running a host can be expected to have the latest updates on the host. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
qemu-1.0-15.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/qemu-1.0-15.fc17
Package qemu-1.0-15.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing qemu-1.0-15.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-6290/qemu-1.0-15.fc17 then log in and leave karma (feedback).
qemu-1.0-17.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/qemu-1.0-17.fc17
Seems to be fixed, can't reproduced it anymore (yum update with updates-testing on, F17 host).
qemu-1.0-17.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.