From: Anthony Liguori <anthony@codemonkey.ws>
To: Alan Kennedy <alphahere@comcast.net>
Cc: kvm@vger.kernel.org
Subject: Re: kvm, hal, and evdev
Date: Tue, 27 May 2008 12:59:50 -0500 [thread overview]
Message-ID: <483C4C16.5040003@codemonkey.ws> (raw)
In-Reply-To: <loom.20080526T222510-507@post.gmane.org>
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
>
next prev parent reply other threads:[~2008-05-27 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 22:58 kvm, hal, and evdev Alan Kennedy
2008-05-27 17:59 ` Anthony Liguori [this message]
2008-05-28 13:15 ` Alan Kennedy
2008-06-03 3:30 ` Anthony Liguori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=483C4C16.5040003@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=alphahere@comcast.net \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox