I installed keymaps on the box with stock Xen 4.1
in expected by xen location /usr/share/qemu/keymaps

root@boris-P5Q-E:/usr/share/qemu-linaro/keymaps# ls
ar      de     en-us  fi  fr-be  hr  it  lv         nl     pl     ru  th
common  de-ch  es     fo  fr-ca  hu  ja  mk         nl-be  pt     sl  tr
da      en-gb  et     fr  fr-ch  is  lt  modifiers  no     pt-br  sv
root@boris-P5Q-E:/usr/share/qemu-linaro/keymaps# cd ../../
root@boris-P5Q-E:/usr/share# mkdir qemu
root@boris-P5Q-E:/usr/share# cd qemu

**********************************
Create directory as required by Xen
**********************************

root@boris-P5Q-E:/usr/share/qemu# mkdir keymaps
root@boris-P5Q-E:/usr/share/qemu# cd keymaps
root@boris-P5Q-E:/usr/share/qemu/keymaps# pwd
/usr/share/qemu/keymaps
root@boris-P5Q-E:/usr/share/qemu/keymaps# cp /usr/share/qemu-linaro/keymaps/* .

Not sure it was quite correct action, but it changes "xl" behavior
HVM - log file follows bellow

*************************************************************
1. Attempt to start HVM report ( submitted to Stefano Stabelini)
*************************************************************

Keymaps installed

Now:

root@boris-P5Q-E:~/vms/natty# xl create f14.hvm
Parsing config file f14.hvm
xc: info: VIRTUAL MEMORY ARRANGEMENT:
  Loader:        0000000000100000->000000000017b150
  TOTAL:         0000000000000000->000000007f800000
  ENTRY ADDRESS: 0000000000101580
xc: info: PHYSICAL MEMORY ALLOCATION:
  4KB PAGES: 0x0000000000000200
  2MB PAGES: 0x00000000000003fb
  1GB PAGES: 0x0000000000000000
Daemon running with PID 32668
root@boris-P5Q-E:~/vms/natty# vncviewer localhost:0

VNC Viewer Free Edition 4.1.1 for X - built Apr  9 2010 18:41:55
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.

Mon Jul 18 17:36:33 2011
 main:        unable to connect to host: Connection refused (111)

LOG FILE :-


root@boris-P5Q-E:/var/log/xen# cat qemu-dm-F14HVM.log
domid: 236
-videoram option does not work with cirrus vga device model. Videoram set to 4M.
Using file /dev/sda5 in read-write mode
Using file /dev/loop0 in read-only mode
Watching /local/domain/0/device-model/236/logdirty/cmd
Watching /local/domain/0/device-model/236/command
Watching /local/domain/236/cpu
char device redirected to /dev/pts/3
qemu_map_cache_init nr_buckets = 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = b5a57be5-1097-4021-b3a7-56133c229c16
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
xs_read(/local/domain/0/device-model/236/xen_extended_power_mgmt): read error
xs_read(): vncpasswd get error. /vm/b5a57be5-1097-4021-b3a7-56133c229c16/vncpasswd.
medium change watch on `hdc' (index: 1): /dev/loop0
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
Log-dirty: no command yet.
vcpu-set: watch node error.
xs_read(/local/domain/236/log-throttling): read error
qemu: ignoring not-understood drive `/local/domain/236/log-throttling'
medium change watch on `/local/domain/236/log-throttling' - unknown device, ignored

******************************************************************
2. VFB appears to work with same issues as  under Xen 4.2 Unstable 
*******************************************************************
Yes , install keymaps brings VFB
But, attempt to install F15 PV domU gives just a part of required screen VFB window
with alive mouse pointer,  for  F14 PV install - VFB  window is good. But mouse pointer is dead.