[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Testing of russian keymap (was Re: [Qemu-devel] [PATCH] fix '/' and

From: Oleg Sadov
Subject: Re: Testing of russian keymap (was Re: [Qemu-devel] [PATCH] fix '/' and '|' on russian keymap)
Date: Tue, 19 Oct 2010 18:16:06 +0400

19/10/2010 10:32 +0100, Daniel P. Berrange wrote:
> On Mon, Oct 18, 2010 at 01:59:15PM -0500, Anthony Liguori wrote:
> > On 10/18/2010 12:30 PM, Oleg Sadov wrote:
> > >I don't understand reasons for such locale-default keyboard settings for
> > >qemu too, but may be it's useful for someone...
> > >   
> > 
> > -k only exists to deal with crappy VNC clients.
> > 
> > If you use a good VNC client (like vinagre or virt-viewer) then you 
> > don't have to use -k.
> Indeed you must *NOT* use -k then, because that disables the extension
> that vinagre/virt-viewer rely on for sane keyboard handling.

I don't use '-k' option directly -- in my RHEL-based system it's
automagically appended to qemu-kvm by libvirt. KVM XML-description,
created by standard virt-manager GUI-interface (package
virt-manager-0.6.1-12.el5.x86_64), has a 'keymap' attribute of
'graphics' tag, despite that configurator don't have any controls for
'keymap' setting.

As I understand, 'default_keymap' function from util.py (package
python-virtinst-0.400.3-9.el5.noarch) got information
from /etc/sysconfig/keyboard, then keymap searched in 'keytable'
dictionary from keytable.py and automatically placed to 'keymap'
attribute of 'graphics' tag in virtual-machine XML-description.

In our system we have a russian keyboard settings => we've got a XML
description like this:

 <graphics type='vnc' port='-1' autoport='yes' keymap='ru'/>

and, as a consequence, qemu-kvm running with '-k ru' option.

> Regards,
> Daniel


reply via email to

[Prev in Thread] Current Thread [Next in Thread]