From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: kvm, hal, and evdev Date: Tue, 27 May 2008 12:59:50 -0500 Message-ID: <483C4C16.5040003@codemonkey.ws> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Alan Kennedy Return-path: Received: from qb-out-0506.google.com ([72.14.204.236]:43178 "EHLO qb-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756342AbYE0SAJ (ORCPT ); Tue, 27 May 2008 14:00:09 -0400 Received: by qb-out-0506.google.com with SMTP id q10so6256711qbq.15 for ; Tue, 27 May 2008 11:00:07 -0700 (PDT) In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: Alan Kennedy wrote: > Hi, > > When using hal to autoload the mouse and keyboard with evdev. The evdev keyboard > model does not work correctly with kvm (qemu) hosts. The arrow, home, end, > insert & delete keys are mapped incorrectly or do not work at all. > How are you interacting with the guest? via SDL? If so, do other SDL applications work correctly? Are you using evdev in the host or in the guest? Regards, Anthony Liguori > This is not unique to kvm (qemu), and also occurs with vmware. See url below for > vmware work around. Found this on the net. > > http://communities.vmware.com/message/498632 > > I suspect the problem is with evdev, but not sure. Is there any work around like > used in vmware or other solutions? > > My solution was stop using hal input autoloading with evdev, and everything is > working fine now. However, I would like to start using evdev if possible because > that is the only driver that fully supports my mouse. > > Thanks for any help with this matter. > > Alan > > System details: > > Kernel 2.6.25.4 > QEMU PC emulator version 0.9.1 (kvm-69) > > > > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >