Bug 636907
| Summary: | virt-install should not add vnc keymaps (<graphics ... keymap='...'>) to guests | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Richard W.M. Jones <rjones> | ||||
| Component: | python-virtinst | Assignee: | Cole Robinson <crobinso> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 14 | CC: | berrange, crobinso, jforbes, virt-maint | ||||
| Target Milestone: | --- | Keywords: | Reopened | ||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | python-virtinst-0.500.6-1.fc14 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-04-16 20:55:53 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: | |||||||
| Attachments: |
|
||||||
|
Description
Richard W.M. Jones
2010-09-23 16:19:48 UTC
What keyboard driver is in use for the X11 server in the broken guests ? Are they using 'evdev' or 'kbd', and is this any different from the guests which are working correctly ? Also does the XML for the guest have any explicit keymap set on the <graphics> tag ? Created attachment 463473 [details]
Xorg.0.log from guest
The XML has:
<graphics type='vnc' port='5901' autoport='yes' keymap='de'/>
For a working guest:
<graphics type='vnc' port='5900' autoport='yes' keymap='en-gb'/>
Changing the keymap in the libvirt XML fixed the problem.
This is a trap. Shouldn't VNC take the keymap from the host's
keyboard configuration (or VNC client's configuration)?
The host keyboard config is not involved in VNC at all. The only ones that matter are the VNC client and guest OS. If specifying a keymap to QEMU, it must match the VNC client's keymap. The QEMU VNC server, however, supports a mode where raw keycodes are sent over the wire instead of keysyms. If the 'keymap' is not specified, then this extension is activated. Thus you should just delete the keymap attribute from the XML, unless you have a need to use a non-GTK-VNC based client. virt-manager/virt-install should not be adding any keymap for new guests anymore. (In reply to comment #4) > virt-manager/virt-install should not be adding any keymap for new guests > anymore. In that case there is a bug here. I created all, or virtually all, of these guests using virt-install on the command line, and it has added a keymap to virtually every one of them. CentOS5x64 <graphics type='vnc' port='-1' autoport='yes' keymap='en-gb'/> Debian5x64 <graphics type='vnc' port='-1' autoport='yes' keymap='en-gb'/> F12x64 <graphics type='vnc' port='-1' autoport='yes' keymap='en-gb'/> F13x32 <graphics type='vnc' port='-1' autoport='yes' keymap='en-gb'/> F13x64 <graphics type='vnc' port='-1' autoport='yes' keymap='en-gb'/> F14Watchdogx64 <graphics type='vnc' port='-1' autoport='yes' keymap='de'/> F14x64 <graphics type='vnc' port='-1' autoport='yes' keymap='de'/> FedoraRawhidex64 <graphics type='vnc' port='-1' autoport='yes' keymap='de'/> FreeBSD8x64 <graphics type='vnc' port='-1' autoport='yes' keymap='en-gb'/> MeeGo11x32 <graphics type='vnc' port='-1' autoport='yes' keymap='en-gb'/> Minix3x32 <graphics type='vnc' port='-1' autoport='yes' keymap='en-gb'/> OpenSUSE11x64 <graphics type='vnc' port='-1' autoport='yes' keymap='en-gb'/> RHEL3x64 <graphics type='vnc' port='-1' autoport='yes' keymap='en-gb'/> RHEL4x64 <graphics type='vnc' port='-1' autoport='yes' keymap='en-gb'/> RHEL5brewx64 <graphics type='vnc' port='-1' autoport='yes' keymap='en-gb'/> RHEL5EPELx64 <graphics type='vnc' port='-1' autoport='yes' keymap='en-gb'/> RHEL5Xenbrewx64 <graphics type='vnc' port='-1' autoport='yes' keymap='en-gb'/> RHEL6brewx64 <graphics type='vnc' port='-1' autoport='yes' keymap='en-gb'/> TwentyDisks <graphics type='vnc' port='-1' autoport='yes' keymap='en-gb'/> TwoDisks <graphics type='vnc' port='-1' autoport='yes' keymap='en-gb'/> Ubuntu1010x64 <graphics type='vnc' port='-1' autoport='yes' keymap='en-gb'/> VBox <graphics type='vnc' port='-1' autoport='yes' keymap='de'/> Win7x32 <graphics type='vnc' port='-1' autoport='yes' keymap='en-gb'/> Yeah virt-install was buggy here, though virt-manager does the right thing. Fixed upstream: http://hg.fedorahosted.org/hg/python-virtinst/rev/2bde513dcd9e python-virtinst-0.500.6-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/python-virtinst-0.500.6-1.fc14 python-virtinst-0.500.4-2.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/python-virtinst-0.500.4-2.fc13 Package python-virtinst-0.500.4-2.fc13: * should fix your issue, * was pushed to the Fedora 13 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing python-virtinst-0.500.4-2.fc13' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/python-virtinst-0.500.4-2.fc13 then log in and leave karma (feedback). python-virtinst-0.500.4-2.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. python-virtinst-0.500.6-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. |