From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:44159) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1URiiM-0008A4-Nx for qemu-devel@nongnu.org; Mon, 15 Apr 2013 08:40:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1URiiH-0002U6-VS for qemu-devel@nongnu.org; Mon, 15 Apr 2013 08:40:54 -0400 Received: from mx1.redhat.com ([209.132.183.28]:17804) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1URiiH-0002Tu-Ni for qemu-devel@nongnu.org; Mon, 15 Apr 2013 08:40:49 -0400 Message-ID: <516BF534.3000909@redhat.com> Date: Mon, 15 Apr 2013 14:40:20 +0200 From: Gerd Hoffmann MIME-Version: 1.0 References: <1365426454-6723-1-git-send-email-lilei@linux.vnet.ibm.com> In-Reply-To: <1365426454-6723-1-git-send-email-lilei@linux.vnet.ibm.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Support for VNC LED state extension proposal List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Lei Li Cc: lagarcia@br.ibm.com, aliguori@us.ibm.com, qemu-devel@nongnu.org Hi, > When access a guest by console through VNC, there might be > mismatch between the lock keys notification LED on the computer > running the VNC client session and the current status of the lock > keys on the guest machine. This happens because the VNC protocol > does not have any support to deal with setting led state. What is the exact issue you are trying to fix here? The vnc server code in qemu already tracks the keyboard led state and will insert synthetic key events if needed to make sure vnc client and guest machine stay in sync. cheers, Gerd