From mboxrd@z Thu Jan  1 00:00:00 1970
From: Olaf Hering <olaf@aepfle.de>
Subject: global keymap= option not recognized
Date: Wed, 8 Jan 2014 17:46:17 +0100
Message-ID: <20140108164617.GA20476@aepfle.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: xen-devel@lists.xen.org
List-Id: xen-devel@lists.xenproject.org

With xm it was possible to have a global keymap="de" to map the physical
keybard correctly. Now with xl this fails, at least in xen-4.3.
xl create -d shows keymap:NULL in the vfb part.
Only moving keymap= into vfb=[] fixes it for me.

xl.cfg(5) indicates that keymap= can be specified as global option (just
like vnc=) as well as suboption for vbf=[]. 

Was this already fixed in xen-unstable? git log shows not keymap related
changes.

Olaf