From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomasz Chmielewski Subject: Re: vncviewer and broken mouse behaviour - is there a fix? Date: Thu, 26 Feb 2009 13:45:03 +0100 Message-ID: <49A68ECF.2050809@wpkg.org> References: <49A6772F.7070803@wpkg.org> <49A686FF.6070503@redhat.com> <49A68C3B.1050002@wpkg.org> <7B7881568CF40E4388B615CD06F87B98098B4A@clara.maurer-it.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Avi Kivity , kvm@vger.kernel.org To: Dietmar Maurer Return-path: Received: from mx03.syneticon.net ([78.111.66.105]:36251 "EHLO mx03.syneticon.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753048AbZBZMok (ORCPT ); Thu, 26 Feb 2009 07:44:40 -0500 In-Reply-To: <7B7881568CF40E4388B615CD06F87B98098B4A@clara.maurer-it.com> Sender: kvm-owner@vger.kernel.org List-ID: Dietmar Maurer schrieb: > use the vmmouse driver (instead of mouse) for X Assuming it'll work, what about console? Well, I guess I could live with it. But what about Windows guests? I've heard unconfirmed rumours that Windows doesn't run X (and have no console mode, either). >> Do I have to configure something special on the quest? >> On my guests, "vnc mouse pointer" moves much faster than the real one - >> both when X is started, but also in console, with gpm started. -- Tomasz Chmielewski http://wpkg.org