Xen devel - Jul 2007 - [PATCH] [IOEMU] Fix shift key for graphical vnc display

Hi All,

There is a problem in the input of the key in the VNC connection on the HVM
domain.
When client''s keyboard is not the same as the kind of the keyboard of
qemu-dm
and GuestOS, it is not possible to input it correctly.

   VNC client     qemu-dm & GuestOS
--------------+-----------------------
    ja             en-us               ==> NG
    en-us          en-us               ==> OK

Originally, the same keysym-code between client and qemu-dm is transmitted.
However, even if it is the same character, the state of shift is different
according to the kind of keyboard.

ex.
   "=" charactor
---------------------
en-us :  "="
ja    :  shift + "-"

Therefore, it is necessary to handle the state of the shift by setting
qemu-dm and GuestOS. There is information on whether shift is necessary
for each key for the keymap of qemu-dm.

ex.
 VNC client        : ja
 qemu-dm & GuestOS : en-us
 input key         : "="
 event client to qemu-dm :
  shift(push) >> "="(push) >> "="(release)
>> shift(release)
 event qemu-dm to guest :
  shift(push) >> shift(release) >> "="(push) >>
"="(release) >> shift(push) >>
shift(release)

This patch handled the state of shift from the set keymap.
When client''s keyboard is not same as the kind of qemu-dm/GuestOS,
it is possible to input it correctly.
It was confirmed to input it correctly mutually with this patch between en-us 
and ja.

Signed-off-by: Takanori Kasai <kasai.takanori@jp.fujitsu.com>

Best Regards,

--
Takanori Kasai


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On Fri, Jul 20, 2007 at 06:45:35PM +0900, Kasai Takanori
wrote:
> Hi All,
> 
> There is a problem in the input of the key in the VNC connection on the HVM
> domain.
> When client''s keyboard is not the same as the kind of the keyboard
of
> qemu-dm
> and GuestOS, it is not possible to input it correctly.
> 
>   VNC client     qemu-dm & GuestOS
> --------------+-----------------------
>    ja             en-us               ==> NG
>    en-us          en-us               ==> OK
I thought the idea of the ''keymap'' entry in the vfb config was
that
you would setup  ''qemu-dm'' & the GuestOS to be
''ja''  too. Trying to
make the ''ja'' -> ''en-us''  conversion work
doesn''t sound like the kind
of thing that would ever work in the general case. Does the
''ja'' -> ''ja''
case currently work ?

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Hi Daniel,

Thank you for reply.
> I thought the idea of the ''keymap'' entry in the vfb
config was that
> you would setup  ''qemu-dm'' & the GuestOS to be
''ja''  too. Trying to
> make the ''ja'' -> ''en-us''  conversion
work doesn''t sound like the kind
> of thing that would ever work in the general case. Does the
''ja'' -> ''ja''
> case currently work ?
This problem occurs when the keyboard on the VNCClient is different.

The keyboard is different when connecting it usually via VNCServer of Dom0.
The VNCClient is transmitted to qemu-dm in the state of shift of en-us.
It is necessary to convert it from en-us to ja.

The keyboard cannot be correctly input with virt-manager of RHEL5.
Because even if everything is set to Japanese keyboard,
the VNCClient of Dom0 inputs it with en-us.

 Client Machine    Dom0        Dom0         Dom0      HVM
  (VNCClient)    (VNCServer)  (VNCClient)   qemu-dm   GuestOS
---------------+------------+------------+----------+-----------
    ja              ja          en-us        ja        ja
                                          (keymap=ja)

Therefore, it is usual that the keyboard of VNCClient and qemu-dm is different.
We are very embarrassed being not able to do a correct input by this problem.

Best Regards,

--
Takanori Kasai



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel