[Qemu-devel] Unknown X11 keycode mapping report

[Qemu-devel] Unknown X11 keycode mapping report

[Jean-Louis SOLATGES]

Bonjour, par tightvnc server sur clipper depuis un linux connecté en vncviewer,

je lance :
qemu-system-x86_64 -m 16G -cpu kvm64 -accel kvm,thread=multi -smp 6,maxcpus=12 -net nic -net tap -net socket,listen=127.0.0.1:1234 -vga cirrus -boot c -hda uis1.img



root@clipper:/home/jls/data# ** (qemu-system-x86_64:16384): WARNING **: Unknown X11 keycode mapping '<null>'.
bash: syntax error near unexpected token `qemu-system-x86_64:16384'

-- 
jls** (qemu-system-x86_64:16384): WARNING **: Unknown X11 keycode mapping '<null>'.
Please report to qemu-devel@nongnu.org
including the following information:

  - Operating system
  - X11 Server
  - xprop -root
  - xdpyinfo

::::
Linux clipper 4.4.14 #2 SMP Fri Jun 24 13:38:27 CDT 2016 x86_64 Intel(R) Xeon(R) CPU           E5645  @ 2.40GHz GenuineIntel GNU/Linux



X.Org X Server 1.18.3
Release Date: 2016-04-04
X Protocol Version 11, Revision 0
Build Operating System: Slackware 14.2 Slackware Linux Project
Current Operating System: Linux clipper 4.4.14 #2 SMP Fri Jun 24 13:38:27 CDT 2016 x86_64
Kernel command line: auto BOOT_IMAGE=Linux ro root=801 vt.default_utf8=0
Build Date: 15 April 2016  11:05:21AM
 
Current version of pixman: 0.34.0
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.



root@clipper:/home/jls/data# xprop -root
CUT_BUFFER0(STRING) = "root@clipper:/home/jls/data# xprop -root\nCUT_BUFFER0(STRING) = \"root@clipper:/home/jls/data# name of display:    :1\\nbash: name: command not found\\nroot@clipper:/home/jls/data# version number:    11.0\\nbash: version: command not found\\n\""

root@clipper:/home/jls/data# xdpyinfo 
name of display:    :1
version number:    11.0
vendor string:    AT&T Laboratories Cambridge
vendor release number:    3332
maximum request size:  4194300 bytes
motion buffer size:  256
bitmap unit, bit order, padding:    32, LSBFirst, 32
image byte order:    LSBFirst
number of supported pixmap formats:    2
supported pixmap formats:supported pixmap formats:
    depth 1, bits_per_pixel 1, scanline_pad 32
    depth 24, bits_per_pixel 32, scanline_pad 32
keycode range:    minimum 8, maximum 255
focus:  PointerRoot
number of extensions:    7
    BIG-REQUESTS
    MIT-SHM
    MIT-SUNDRY-NONSTANDARD
    SHAPE
    SYNC
    XC-MISC
    XTEST
default screen number:    0
number of screens:    1

screen #0:
  dimensions:    1024x768 pixels (347x260 millimeters)
  resolution:    75x75 dots per inch
  depths (1):    24
  root window id:    0x25
  depth of root window:    24 planes
  number of colormaps:    minimum 1, maximum 1
  default colormap:    0x21
    depth 1, bits_per_pixel 1, scanline_pad 32
    depth 24, bits_per_pixel 32, scanline_pad 32
keycode range:    minimum 8, maximum 255
focus:  PointerRoot
number of extensions:    7
    BIG-REQUESTS
    MIT-SHM
    MIT-SUNDRY-NONSTANDARD
    SHAPE
    SYNC
    XC-MISC
    XTEST
default screen number:    0
number of screens:    1

screen #0:
  dimensions:    1024x768 pixels (347x260 millimeters)
  resolution:    75x75 dots per inch
  depths (1):    24
  root window id:    0x25
  depth of root window:    24 planes
  number of colormaps:    minimum 1, maximum 1
  default colormap:    0x21
 default number  default number of colormap cells:    256
  preallocated pixels:    black 0, white 16777215
  options:    backing-store YES, save-unders YES
  largest cursor:    1024x768
  current input event mask:    0x0
  number of visuals:    1
  default visual id:  0x22
  visual:
    visual id:    0x22
    class:    TrueColor
    depth:    24 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits


--------

Emulé :Linux useit1 3.16.0-0.bpo.4-amd64 #1 SMP Debian 3.16.39-1+deb8u1~bpo70+1 (2017-02-24) x86_64 GNU/Linux


X.Org X Server 1.12.4
Release Date: 2012-08-27
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
Current Operating System: Linux useit1 3.16.0-0.bpo.4-amd64 #1 SMP Debian 3.16.39-1+deb8u1~bpo70+1 (2017-02-24) x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-0.bpo.4-amd64 root=UUID=73c0ba43-33c1-42b3-9aac-45f8ad9951d0 ro quiet splash
Build Date: 09 February 2015  09:46:52AM
xorg-server 2:1.12.4-6+deb7u6 (Julien Cristau <jcristau@debian.org>) 
Current version of pixman: 0.26.0
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.

-----


Merci.

Re: [Qemu-devel] Unknown X11 keycode mapping report

[Daniel P. Berrangé]

On Tue, Apr 02, 2019 at 02:47:25PM +0200, Jean-Louis SOLATGES wrote:
> Bonjour, par tightvnc server sur clipper depuis un linux connecté en vncviewer,

Google translate doesn't do a good job here.

Is this saying that you are running QEMU from inside a TightVNC server
session running on Linux ?  IOW the X11 server would be Xvnc, not your
regular desktop Xorg server ?

> 
> je lance :
> qemu-system-x86_64 -m 16G -cpu kvm64 -accel kvm,thread=multi -smp 6,maxcpus=12 -net nic -net tap -net socket,listen=127.0.0.1:1234 -vga cirrus -boot c -hda uis1.img


Can you say what version of QEMU you are using too ?


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

Re: [Qemu-devel] Unknown X11 keycode mapping report

[Philippe Mathieu-Daudé]

On 4/2/19 3:28 PM, Daniel P. Berrangé wrote:
> On Tue, Apr 02, 2019 at 02:47:25PM +0200, Jean-Louis SOLATGES wrote:
>> Bonjour, par tightvnc server sur clipper depuis un linux connecté en vncviewer,
> 
> Google translate doesn't do a good job here.

Google isn't that wrong here, I'm also having difficulties to understand.

> 
> Is this saying that you are running QEMU from inside a TightVNC server
> session running on Linux ?  IOW the X11 server would be Xvnc, not your
> regular desktop Xorg server ?

This is what I understand indeed.

Jean-Louis uses a Linux workstation where he uses vncviewer to connect
to a tightvnc server running on the 'clipper' server (Slackware 14.2).

Within the VNC session, he runs as root the qemu-system-x86_64 command
on 'clipper'. I suppose "Linux useit1 3.16.0-0.bpo.4-amd64" is the image
he tries to run.

>>
>> je lance :
>> qemu-system-x86_64 -m 16G -cpu kvm64 -accel kvm,thread=multi -smp 6,maxcpus=12 -net nic -net tap -net socket,listen=127.0.0.1:1234 -vga cirrus -boot c -hda uis1.img
> 
> 
> Can you say what version of QEMU you are using too ?
> 
> 
> Regards,
> Daniel
> 

Re: [Qemu-devel] Unknown X11 keycode mapping report

[Daniel P. Berrangé]

On Tue, Apr 02, 2019 at 02:47:25PM +0200, Jean-Louis SOLATGES wrote:
> Bonjour, par tightvnc server sur clipper depuis un linux connecté en vncviewer,
> 
> je lance :
> qemu-system-x86_64 -m 16G -cpu kvm64 -accel kvm,thread=multi -smp 6,maxcpus=12 -net nic -net tap -net socket,listen=127.0.0.1:1234 -vga cirrus -boot c -hda uis1.img
> 
> 
> 
> root@clipper:/home/jls/data# ** (qemu-system-x86_64:16384): WARNING **: Unknown X11 keycode mapping '<null>'.
> bash: syntax error near unexpected token `qemu-system-x86_64:16384'
> 
> -- 
> jls** (qemu-system-x86_64:16384): WARNING **: Unknown X11 keycode mapping '<null>'.
> Please report to qemu-devel@nongnu.org
> including the following information:
> 
>   - Operating system
>   - X11 Server
>   - xprop -root
>   - xdpyinfo
> 
> ::::
> Linux clipper 4.4.14 #2 SMP Fri Jun 24 13:38:27 CDT 2016 x86_64 Intel(R) Xeon(R) CPU           E5645  @ 2.40GHz GenuineIntel GNU/Linux
> 
> 
> 
> X.Org X Server 1.18.3
> Release Date: 2016-04-04
> X Protocol Version 11, Revision 0
> Build Operating System: Slackware 14.2 Slackware Linux Project
> Current Operating System: Linux clipper 4.4.14 #2 SMP Fri Jun 24 13:38:27 CDT 2016 x86_64
> Kernel command line: auto BOOT_IMAGE=Linux ro root=801 vt.default_utf8=0
> Build Date: 15 April 2016  11:05:21AM
>  
> Current version of pixman: 0.34.0
>         Before reporting problems, check http://wiki.x.org
>         to make sure that you have the latest version.
> 
> 
> 
> root@clipper:/home/jls/data# xprop -root
> CUT_BUFFER0(STRING) = "root@clipper:/home/jls/data# xprop -root\nCUT_BUFFER0(STRING) = \"root@clipper:/home/jls/data# name of display:    :1\\nbash: name: command not found\\nroot@clipper:/home/jls/data# version number:    11.0\\nbash: version: command not found\\n\""


So there's no _XKB_RULES_NAMES property set which is what QEMU
wants to see.

> 
> root@clipper:/home/jls/data# xdpyinfo 
> name of display:    :1
> version number:    11.0
> vendor string:    AT&T Laboratories Cambridge
> vendor release number:    3332
> maximum request size:  4194300 bytes
> motion buffer size:  256
> bitmap unit, bit order, padding:    32, LSBFirst, 32
> image byte order:    LSBFirst
> number of supported pixmap formats:    2
> supported pixmap formats:supported pixmap formats:
>     depth 1, bits_per_pixel 1, scanline_pad 32
>     depth 24, bits_per_pixel 32, scanline_pad 32
> keycode range:    minimum 8, maximum 255
> focus:  PointerRoot
> number of extensions:    7
>     BIG-REQUESTS
>     MIT-SHM
>     MIT-SUNDRY-NONSTANDARD
>     SHAPE
>     SYNC
>     XC-MISC
>     XTEST

The  XKEYBOARD extension is missing which is why we dont' see the
XKB property above.

We have a heuristic that tries to deal with this by checking what
keycode  "XK_Page_Up" maps to, but that has failed for you too.

So I'm puzzlled what key map this X server is actually using.


I don't have SLackware handy, but can't reproduce on Fedora with
TigerVNC.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|