[Qemu-devel] It told me to report this...

[Qemu-devel] It told me to report this...

[Warner Losh]

unknown keycodes `empty+aliases(qwerty)', please report to
qemu-devel@nongnu.org

My X server is Mac XQuartz 2.7.11. I saw this question raised several years
ago in the archives, with promises of patches, but couldn't find anything
relevant in the latest tree I grabbed from github (I saw this problem there
as well as 2.9.0 installed from FreeBSD ports).

What's my next step here?

Warner

Re: [Qemu-devel] It told me to report this...

[Dr. David Alan Gilbert]

* Warner Losh (imp@bsdimp.com) wrote:
> unknown keycodes `empty+aliases(qwerty)', please report to
> qemu-devel@nongnu.org
> 
> My X server is Mac XQuartz 2.7.11. I saw this question raised several years
> ago in the archives, with promises of patches, but couldn't find anything
> relevant in the latest tree I grabbed from github (I saw this problem there
> as well as 2.9.0 installed from FreeBSD ports).
> 
> What's my next step here?

I think that's one of Gerd's messages, so I've added him to the
email and also Daniel since he's got an interest in key mappings.

Have you any idea if it happened when you pressed a particular key?


Dave

> 
> Warner
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

Re: [Qemu-devel] It told me to report this...

[Daniel P. Berrange]

On Mon, Dec 11, 2017 at 12:29:36PM +0000, Dr. David Alan Gilbert wrote:
> * Warner Losh (imp@bsdimp.com) wrote:
> > unknown keycodes `empty+aliases(qwerty)', please report to
> > qemu-devel@nongnu.org
> > 
> > My X server is Mac XQuartz 2.7.11. I saw this question raised several years
> > ago in the archives, with promises of patches, but couldn't find anything
> > relevant in the latest tree I grabbed from github (I saw this problem there
> > as well as 2.9.0 installed from FreeBSD ports).
> > 
> > What's my next step here?
> 
> I think that's one of Gerd's messages, so I've added him to the
> email and also Daniel since he's got an interest in key mappings.
> 
> Have you any idea if it happened when you pressed a particular key?

Don't worry, this is a known limitation of the current X backend for QEMU.

It only knows how to work with Xorg on Linux with kbd or evdev. It can't
cope with OS-X or Windows  X11 servers yet. I've got patches that will
address this which i hope to finally put into 2.12 as part of the keycodemapdb
work.

In the meantime your best bet is to use the native OS-X cocoa frontend for
QEMU, or VNC.

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] It told me to report this...

[Warner Losh]

On Mon, Dec 11, 2017 at 5:33 AM, Daniel P. Berrange <berrange@redhat.com>
wrote:

> On Mon, Dec 11, 2017 at 12:29:36PM +0000, Dr. David Alan Gilbert wrote:
> > * Warner Losh (imp@bsdimp.com) wrote:
> > > unknown keycodes `empty+aliases(qwerty)', please report to
> > > qemu-devel@nongnu.org
> > >
> > > My X server is Mac XQuartz 2.7.11. I saw this question raised several
> years
> > > ago in the archives, with promises of patches, but couldn't find
> anything
> > > relevant in the latest tree I grabbed from github (I saw this problem
> there
> > > as well as 2.9.0 installed from FreeBSD ports).
> > >
> > > What's my next step here?
> >
> > I think that's one of Gerd's messages, so I've added him to the
> > email and also Daniel since he's got an interest in key mappings.
> >
> > Have you any idea if it happened when you pressed a particular key?
>
> Don't worry, this is a known limitation of the current X backend for QEMU.
>
> It only knows how to work with Xorg on Linux with kbd or evdev. It can't
> cope with OS-X or Windows  X11 servers yet. I've got patches that will
> address this which i hope to finally put into 2.12 as part of the
> keycodemapdb
> work.
>

I've built qemu many times over the years. I'd be happy to test them out to
make sure they work for me :). Also, a million years ago, I did extensive
work with X11 keymaps when I was working on the OI toolkit, so I have some
familiarity...


> In the meantime your best bet is to use the native OS-X cocoa frontend for
> QEMU, or VNC.
>

That's... awkward since it would mean copying the VM over to mac... VNC
might work though...

Warner

Re: [Qemu-devel] It told me to report this...

[Warner Losh]

On Mon, Dec 11, 2017 at 5:29 AM, Dr. David Alan Gilbert <dgilbert@redhat.com
> wrote:

> * Warner Losh (imp@bsdimp.com) wrote:
> > unknown keycodes `empty+aliases(qwerty)', please report to
> > qemu-devel@nongnu.org
> >
> > My X server is Mac XQuartz 2.7.11. I saw this question raised several
> years
> > ago in the archives, with promises of patches, but couldn't find anything
> > relevant in the latest tree I grabbed from github (I saw this problem
> there
> > as well as 2.9.0 installed from FreeBSD ports).
> >
> > What's my next step here?
>
> I think that's one of Gerd's messages, so I've added him to the
> email and also Daniel since he's got an interest in key mappings.
>
> Have you any idea if it happened when you pressed a particular key?
>

It's just once, on boot. Pressing keys, though, is an exercise in futility.
Nothing maps right at all.

Warner


>
> Dave
>
> >
> > Warner
> --
> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
>

Re: [Qemu-devel] It told me to report this...

[Daniel P. Berrange]

On Mon, Dec 11, 2017 at 08:05:29AM -0700, Warner Losh wrote:
> On Mon, Dec 11, 2017 at 5:33 AM, Daniel P. Berrange <berrange@redhat.com>
> wrote:
> 
> > On Mon, Dec 11, 2017 at 12:29:36PM +0000, Dr. David Alan Gilbert wrote:
> > > * Warner Losh (imp@bsdimp.com) wrote:
> > > > unknown keycodes `empty+aliases(qwerty)', please report to
> > > > qemu-devel@nongnu.org
> > > >
> > > > My X server is Mac XQuartz 2.7.11. I saw this question raised several
> > years
> > > > ago in the archives, with promises of patches, but couldn't find
> > anything
> > > > relevant in the latest tree I grabbed from github (I saw this problem
> > there
> > > > as well as 2.9.0 installed from FreeBSD ports).
> > > >
> > > > What's my next step here?
> > >
> > > I think that's one of Gerd's messages, so I've added him to the
> > > email and also Daniel since he's got an interest in key mappings.
> > >
> > > Have you any idea if it happened when you pressed a particular key?
> >
> > Don't worry, this is a known limitation of the current X backend for QEMU.
> >
> > It only knows how to work with Xorg on Linux with kbd or evdev. It can't
> > cope with OS-X or Windows  X11 servers yet. I've got patches that will
> > address this which i hope to finally put into 2.12 as part of the
> > keycodemapdb
> > work.
> >
> 
> I've built qemu many times over the years. I'd be happy to test them out to
> make sure they work for me :). Also, a million years ago, I did extensive
> work with X11 keymaps when I was working on the OI toolkit, so I have some
> familiarity...

I'm basically copying the same code / approach we've already done with
GTK-VNC & SPICE-GTK

I've got a patch here:

  https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg02058.html

but that almost certainly won't apply to current GIT master, so I'll be
sending updated versions soonish.

> > In the meantime your best bet is to use the native OS-X cocoa frontend for
> > QEMU, or VNC.
> >
> 
> That's... awkward since it would mean copying the VM over to mac... VNC
> might work though...

VNC would be my recommendation, or perhaps SPICE if you want some of its
extra features over VNC.

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] It told me to report this...

[Daniel P. Berrange]

On Mon, Dec 11, 2017 at 08:06:47AM -0700, Warner Losh wrote:
> On Mon, Dec 11, 2017 at 5:29 AM, Dr. David Alan Gilbert <dgilbert@redhat.com
> > wrote:
> 
> > * Warner Losh (imp@bsdimp.com) wrote:
> > > unknown keycodes `empty+aliases(qwerty)', please report to
> > > qemu-devel@nongnu.org
> > >
> > > My X server is Mac XQuartz 2.7.11. I saw this question raised several
> > years
> > > ago in the archives, with promises of patches, but couldn't find anything
> > > relevant in the latest tree I grabbed from github (I saw this problem
> > there
> > > as well as 2.9.0 installed from FreeBSD ports).
> > >
> > > What's my next step here?
> >
> > I think that's one of Gerd's messages, so I've added him to the
> > email and also Daniel since he's got an interest in key mappings.
> >
> > Have you any idea if it happened when you pressed a particular key?
> >
> 
> It's just once, on boot. Pressing keys, though, is an exercise in futility.
> Nothing maps right at all.

Yep, QEMU tries to detect if Xorg is using evdev, and if not it assumes the
legacy Linux  "kbd" driver mapping. This is unquestionably wrong for any
non-Linux  X11 server, so you'll just get complete garbage, as you found
out.

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] It told me to report this...

[Daniel P. Berrange]

On Mon, Dec 11, 2017 at 03:08:41PM +0000, Daniel P. Berrange wrote:
> On Mon, Dec 11, 2017 at 08:05:29AM -0700, Warner Losh wrote:
> > On Mon, Dec 11, 2017 at 5:33 AM, Daniel P. Berrange <berrange@redhat.com>
> > wrote:
> > 
> > > On Mon, Dec 11, 2017 at 12:29:36PM +0000, Dr. David Alan Gilbert wrote:
> > > > * Warner Losh (imp@bsdimp.com) wrote:
> > > > > unknown keycodes `empty+aliases(qwerty)', please report to
> > > > > qemu-devel@nongnu.org
> > > > >
> > > > > My X server is Mac XQuartz 2.7.11. I saw this question raised several
> > > years
> > > > > ago in the archives, with promises of patches, but couldn't find
> > > anything
> > > > > relevant in the latest tree I grabbed from github (I saw this problem
> > > there
> > > > > as well as 2.9.0 installed from FreeBSD ports).
> > > > >
> > > > > What's my next step here?
> > > >
> > > > I think that's one of Gerd's messages, so I've added him to the
> > > > email and also Daniel since he's got an interest in key mappings.
> > > >
> > > > Have you any idea if it happened when you pressed a particular key?
> > >
> > > Don't worry, this is a known limitation of the current X backend for QEMU.
> > >
> > > It only knows how to work with Xorg on Linux with kbd or evdev. It can't
> > > cope with OS-X or Windows  X11 servers yet. I've got patches that will
> > > address this which i hope to finally put into 2.12 as part of the
> > > keycodemapdb
> > > work.
> > >
> > 
> > I've built qemu many times over the years. I'd be happy to test them out to
> > make sure they work for me :). Also, a million years ago, I did extensive
> > work with X11 keymaps when I was working on the OI toolkit, so I have some
> > familiarity...
> 
> I'm basically copying the same code / approach we've already done with
> GTK-VNC & SPICE-GTK
> 
> I've got a patch here:
> 
>   https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg02058.html
> 
> but that almost certainly won't apply to current GIT master, so I'll be
> sending updated versions soonish.

If you want to test something, then I've posted new patch series with
the UI changes:

  https://lists.gnu.org/archive/html/qemu-devel/2017-12/msg01988.html

it applies to current git master, aka soon to be 2.11.

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 :|