VNC console keeps reporting "setkeycodes 00" exception

Sounds like a problem with the image you're using, not with nova, see something like this:

http://old-list-archives.xenproject.org/xen-users/2007-07/msg00839.html

The image is the default image being uploaded by stack setup, which is working last week. There should be some changes in either nova or novnc which causes this issue.

That sounds a guest problem that could be due to either KVM or noVnc because when looking at Google, I can find multiple bugreports related to some flooding in non-supported keymaps :

https://bugzilla.redhat.com/show_bug.cgi?id=868237
https://www.centos.org/forums/viewtopic.php?t=1236

Either way, all of that seems very unrelated to Nova. Leaving the bug as Invalid.

Either way, could you please let us know the guest image OS ? It seems some bug is hitting cirros, I try to understand what could have changed.

I tried both cirros-0.3.3-x86_64 and cirros-0.3.4-x86_64 and they both had this issue.

I can confirm that I can reproduce this with the same cirros image that is working fine on older installations. Failure happens on Xenial with devstack from master. So if there isn't something changed in nova (maybe related to serial console support?), then it would be a change in the virtualization environment, kvm, qemu, libvirt, vnc.

Thanks Jens for the confirmation. I also tried with deibian image. It doesn't report such keymap error, but instead doesn't respond to any key press.

As a side note that I did an experiment with virt-manager, and the consoles work fine on all VMs.

To clarify, could you please use latest devstack with an old cirros image (not the one provided by devstack) so we could be sure that the problem is related to the guest OS?

Nevermind my previous question, it seems you checked an old cirros image too.
Would it be possible you use like a serial console instead of NoVNC to see if it would be related to only novnc (either in Nova or NoVnc directly) ?

http://docs.openstack.org/developer/nova/testing/serial-console.html for testing serial console.

Hi Sylvain,

I tested with serial console, and everything works fine without such annoying issue.

Thanks,
Tong

Hi Tong,

Nova shares the same code for both serial and novnc consoles by only providing a base proxy that would run a websockify bridge for doing TCP connections thru websockets. Beyond that point, it becomes unrelated to Nova.

That said, I just saw a 0.6.1 release of novnc that has been published early July.
https://github.com/kanaka/noVNC/releases

It would be worth a try to verify the novnc version and downgrade it to 0.5.1 for testing if the issue is still there.