From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mihail Panev Subject: Re: kvm-84: Nested virtualization, crashes, and kvm binary name Date: Fri, 10 Apr 2009 20:25:54 +0200 Message-ID: <49DF8F32.3040707@hm.edu> References: <49DE7BBF.7080004@hm.edu> <49DF7D14.6010005@hm.edu> <59abf66e0904101023l2229d852w45c8581a17dc358e@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Alexander Graf , kvm@vger.kernel.org To: =?ISO-8859-1?Q?Jorge_Luc=E1ngeli_Obes?= Return-path: Received: from mailrelay2.lrz-muenchen.de ([129.187.254.102]:38721 "EHLO mailrelay2.lrz-muenchen.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1763771AbZDJSYD (ORCPT ); Fri, 10 Apr 2009 14:24:03 -0400 In-Reply-To: <59abf66e0904101023l2229d852w45c8581a17dc358e@mail.gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: Jorge Luc=E1ngeli Obes wrote: > Try specifying '-usbdevice tablet' in the KVM command line. Regular > mice report relative coordinates, and that supposedly messes up with > VNC. Tablet devices report absolute coordinates so they work well wit= h > VNC. Yeah, I read that too and tried it out, but it somehow brought no change. The exact same behavior as before. But I'll try it out again on Tuesday. Besides, what's the problem with relative coordinates? When I connect to a normal X session via VNC, they're relative too, and I have no problems. There's actually no black dot per default, I must enable it explicitly, and even then the remote mouse pointer moves quite simultaneously with the dot (maybe 50-100 ms lag?). With KVM, I cannot disable the dot at all (which would itself be already a big improvement= ). Thanks for your hints, Mike