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

2019-04-02 Thread 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.

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

2019-04-02 Thread 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

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

2019-04-02 Thread 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 ?

[Qemu-devel] Unknown X11 keycode mapping report

2019-04-02 Thread 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