29.10.2017 18:54, Michael Gold wrote: [] > CPU type/count, etc. Is any workaround for this known? And does the -k > option have any effect now? My preference is to have it work as before; > but if it will have no effect, it should raise an error or be removed.
For all modern UI types (introduced in upstream qemu in recent years), -k option is ignored because the way qemu now handles key mapping is entirely different, it is like bypass mechanism, and the upstream says it is THE ONLY sane way to handle this, so no workaround is intended. For multiple years they've been telling us users to stop using -k. I for one never used it at all so I've no idea, but each time I tried to reproduce various bugreports with context of keyboard handling, there has always been a solution - removing -k helped. Yes I agree, usage of -k with UI types which does not support it should give a warning (definitely not an error but that's just my opinion). /mjt
