Re: [Qemu-devel] Pipe key broken on US keyboards

2018-08-21 Thread Phillip Susi
On 8/17/2018 11:51 AM, Daniel P. Berrangé wrote: > Since you're using tightvnc on Windows, it won't be using the raw scancode > extension to RFB, so it'll be sending X keysyms across the wire eg > > "|" has X11 keysym 0x7c (XK_bar) > "\" has X11 keysym 0x5c (XK_backslash) > > First thing i

Re: [Qemu-devel] Pipe key broken on US keyboards

2018-08-20 Thread Phillip Susi
On 8/20/2018 11:07 AM, Christian Ehrhardt wrote: > What exactly would you need in Ubuntu Phillp? It *looks* like this is fixed in 2.12, but Ubuntu has 2.11. > Latest qemu would atm be on 2.12 with the git available here [1]. > Unfortunately mostly nobody cares about the git branches so I forgot t

Re: [Qemu-devel] Pipe key broken on US keyboards

2018-08-20 Thread Phillip Susi
On 8/20/2018 4:43 AM, Gerd Hoffmann wrote: > There have been fixes for that one, specifically recent qemu will look > at modifier state in addition to the keysym when looking up the keycode, > because some keymaps can generate the same keysym with different key > combinations, and most of the time

Re: [Qemu-devel] Pipe key broken on US keyboards

2018-08-17 Thread Phillip Susi
On 8/17/2018 11:05 AM, Daniel P. Berrangé wrote: > Reading again, this is a bit odd. On most keyboards, holding down shift > key generally would NOT change the scan code that is reported (there are a Right; a real keyboard won't change the scan code, but it seems that European keyboards have this

Re: [Qemu-devel] Pipe key broken on US keyboards

2018-08-17 Thread Phillip Susi
I've been reading up here: http://www.win.tue.nl/~aeb/linux/kbd/scancodes-1.html And man, what a mess keyboards are! Worse than floppy controllers. According to that site, the scan code for \ should be 0x2b, so why does xev say the keycode is 51? Is keycode something else entirely from scan code

Re: [Qemu-devel] Pipe key broken on US keyboards

2018-08-17 Thread Phillip Susi
On 8/17/2018 10:44 AM, Daniel P. Berrangé wrote: > 0x2b is 43 in hex. > > xev reports the Xorg scancode, which is the same as the XT/AT-set1 > scancodes, with an offset of 8 added > > IOW, 51 from xev does actually match 0x2b from XT scancode set Oy vey! Just for fun they decided to add 8 eh?

Re: [Qemu-devel] Pipe key broken on US keyboards

2018-08-17 Thread Phillip Susi
On 8/17/2018 9:12 AM, Daniel P. Berrangé wrote: > It depends on what the VNC client asks for too. With no '-k' arg, if the > VNC client asks for raw scancodes it'll get that, otherwise QEMU will > fallback to en-US.GTK-VNC based clients (remote-viewer, virt-viewer, > vinagre, virt-manager, GNOM

Re: [Qemu-devel] Pipe key broken on US keyboards

2018-08-17 Thread Phillip Susi
On 8/17/2018 8:58 AM, Daniel P. Berrangé wrote: > Actually for QEMU there is no default localized keymap. This is desirable > because it allows VNC to activate its raw scancode extension which is more > reliable than passing translated X11 key symbols. > > I guess there's a chance that Xen might s

Re: [Qemu-devel] Pipe key broken on US keyboards

2018-08-17 Thread Phillip Susi
On 8/17/2018 4:56 AM, Daniel P. Berrangé wrote: > Oh one other thing, is whether your QEMU process has an explicit keymap > configured (this is the -k arg to QEMU), as when that it set, it > completely changes the way keyboard input is handled in VNC. That code > has also been massively refactored

Re: [Qemu-devel] Pipe key broken on US keyboards

2018-08-16 Thread Phillip Susi
On 8/16/2018 1:27 PM, Daniel P. Berrangé wrote: > Did you actually 'git bisect' to that commit, or is that just a guess ? No, I haven't actually tried to build it from sources myself yet so I just found the source file that handles the keyboard, saw a bunch of scancode translation stuff in it, did

[Qemu-devel] Pipe key broken on US keyboards

2018-08-16 Thread Phillip Susi
Hello, I recently upgraded my Xen server from Ubuntu 16.04 to 18.04 and am no longer able to type a | over vnc to the xen vms. When I press \ it works, but when I hold down shift and press \ which should generate a |, the vm sees the scan code for some key that the keymap thinks should sit between

Re: [Qemu-devel] [Bug 1155403] Re: virtio cdrom detected as hard disk

2013-03-18 Thread Phillip Susi
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 3/18/2013 11:17 AM, Paolo Bonzini wrote: > if=virtio means virtio-blk, not virtio-something. Why do you say that? I would say that virtio means use paravirtualized IO rather than emulating some real hardware. Whether that ends up being done with

Re: [Qemu-devel] [Bug 1155403] Re: virtio cdrom detected as hard disk

2013-03-18 Thread Phillip Susi
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 3/18/2013 5:13 AM, Paolo Bonzini wrote: >> Or better yet, shouldn't it automatically use virtio-scsi >> instead? > > No, virtio-scsi is relatively new and not all distros have picked > it up yet. And not all distros ship hybrid cd images that thei

[Qemu-devel] [Bug 1155403] Re: virtio cdrom detected as hard disk

2013-03-17 Thread Phillip Susi
It seems the installer does not consider virtio devices when doing its search. It also seems the installer does not have the virtio-scsi module, and it seems a bit wasteful to go through a layer of scsi emulation. Shouldn't qemu at least warn you that the media=argument does nothing on virtio dev