Skip to main content

Fixing Openstack Cirros VM : atkbd serio0: Use setkeycodes 00 error


When a Cirros VM is launched in Openstack Newton using the latest branch code you may encounter an error which prevents you from logging into VM's console. As soon as you start typing the username 'cirros' you may find the following error message getting printed on the console:

atkbd serio0: Unknown key released (translates Set 2, ................)
atkbd serio0: Use 'setkeycodes 00 ' to make it known

This is a known issue and is tracked @ https://bugs.launchpad.net/devstack/+bug/1619554

I had tough time finding a solution to this problem and the solution turns out to be quite a simple one. This issue is occurring due to a bug in the latest noVNC code and is tracked @ https://bugs.launchpad.net/horizon/+bug/1622684

This problem can be solved in two ways (as a workaround):

1. Set NOVNC_BRANCH=v0.6.0 in your local.conf file and restack
2. cd /opt/stack/noVNC
    git checkout v0.6.0
    Now go to your VM console and refresh it. It should start working.


Labels:

Comments

Post a Comment

Popular posts from this blog

Solved: Fix for Git clone failure due to GnuTLS recv error (-9)

My devstack installation was failing with an error reported by the GnuTLS module as shown below: $ git clone https://github.com/openstack/horizon.git /opt/stack/horizon --branch master Cloning into '/opt/stack/horizon'... remote: Counting objects: 154213, done. remote: Compressing objects: 100% (11/11), done. error: RPC failed; curl 56 GnuTLS recv error (-9): A TLS packet with unexpected length was received. fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed The following Git config changes fixed the issue for me. Am hoping it will be useful for someone out there: $ git config http.sslVerify false $ git config --global http.postBuffer 1048576000
14 comments
Read more

QuickBite: Tap Vs Veth

Linux supports virtual networking via various artifacts such as: Soft Switches (Linux Bridge, OpenVSwitch) Virtual Network Adapters (tun, tap, veth and a few more) In this blog, we will look at the virtual network adapters tap and veth. From a practical view point, both seem to be having the same functionality and its a bit confusing as to where to use what. A quick definition of tap/veth is as follows: TAP A TAP is a simulated interface which exists only in the kernel and has no physical component associated with it. It can be viewed as a simple Point-to-Point or Ethernet device, which instead of receiving packets from a physical media, receives them from user space program and instead of sending packets via physical media writes them to the user space program. When a user space program (in our case the VM) gets attached to the tap interface it gets hold of a file descriptor, reading from which gives it the data being sent on the tap interface. Writing to the file descri...
5 comments
Read more

[Solved] Fixing ping: ***** : Name or service not known issue

I have a Virtualbox VM running Ubuntu 19.05 Desktop version and the network is managed by NetworkManager. It has two interfaces attached to NAT and HostOnly networks. Due to some reason, I was not able to ping my office site and when I looked up in resolv.conf I see that its a symbolic link auto generated by systemd-resolve. One thing that caught my attention was that the name server was set as below: nameserver 127.0.0.53 The following sequence of steps helped me in resolving this issue: UI NetworkManager --> IPV4 --> Set DNS to Manual and add 1.1.1.1, 8.8.8.8 for dns. Then run the below command sudo dhclient Hope this helps someone out there.
1 comment
Read more