I've tried a FreeBSD guest using the XENHVM kernel (release 9.1), and I've found that when using the XENHVM kernel the keyboard input form the vnc client stops working (output to the vnc seems to be ok thought), so I have to set up a serial port before switching to XENHVM or there's no way to interact with the guest (apart from ssh of course). HEAD also seems to be experiencing the same issue. Is this expected/know? I'm using Xen unstable and the device model is Qemu-upstream. Fix: The problem is that we set all devices in xenstore that we don't know how to handle to state '6' (closed), which is not right. We should not mess with the state of devices that we cannot handle. The following patch fixes the problem by probing the devices first, and only try to attach the ones that we can handle. --- From: Roger Pau Monne <roger.pau@citrix.com> Date: Thu, 31 Jan 2013 17:24:48 +0000 Subject: [PATCH] xenbus: fix device detection Devices that cannot be handled should not be closed, instead leave them as is. This prevents closing the vkbd device, which has the effect of making Qemu stop sending keys to the guest. Tested with qemu-xen-traditional, qemu-xen and qemu stubdomains, all working as expected. --- sys/xen/xenbus/xenbusb.c | 19 ++++++++++++++++++- 1 files changed, 18 insertions(+), 1 deletions(-) How-To-Repeat: Install a FeeeBSD guest in Xen and switch to the XENHVM kernel, the keyboard on the VNC stops sending keys to the guest.
Responsible Changed From-To: freebsd-bugs->freebsd-xen Over to maintainer(s).
Patch has been committed.