From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LiqEf-0003CD-S6
	for qemu-devel@nongnu.org; Sun, 15 Mar 2009 09:18:37 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LiqEb-00037c-Ak
	for qemu-devel@nongnu.org; Sun, 15 Mar 2009 09:18:37 -0400
Received: from [199.232.76.173] (port=53062 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LiqEb-00037Z-5N
	for qemu-devel@nongnu.org; Sun, 15 Mar 2009 09:18:33 -0400
Received: from mx2.redhat.com ([66.187.237.31]:39400)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <avi@redhat.com>) id 1LiqEa-0006MH-K7
	for qemu-devel@nongnu.org; Sun, 15 Mar 2009 09:18:32 -0400
Message-ID: <49BD0025.5070600@redhat.com>
Date: Sun, 15 Mar 2009 15:18:29 +0200
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
References: <167037245.20090312211043@uni-lueneburg.de>
In-Reply-To: <167037245.20090312211043@uni-lueneburg.de>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Re: Unable to re-establish VNC connection after some
	time
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Andreas Olsowski <andreas.olsowski@uni-lueneburg.de>
Cc: qemu-devel <qemu-devel@nongnu.org>, kvm@vger.kernel.org

Andreas Olsowski wrote:
> Hello fellow kvm users/admins,
>  im currently running kvm-84 with linux-2.6.28.4 under x86_64.
>  My  2 linux guests are basically running the same kernel (minus iscsi, multipath and
>  kvm support.
>  Another guest is a win2008 server.
>
>  All of the machines experience the same problem:
>
>  After  a  while  i can't connect via VNC, UltraVNC as well as RealVNC
>  experiencee Timeouts waiting for the server to respond.
>
>  All machines show:
>  (qemu) info vnc
>   VNC server active on: 0.0.0.0:1
>   Client connected
>
>  It  looks  like  something  has  died there ... could it be because i
>  didnt   disconnect  my  VNC Client properly?
>
>  Even (qemu) system_reset, will not bring the screen back.
>
>  I am open for suggestions.
>   

Looks like the internal vnc server deadlocked.

What does 'netstat -t' show?

Maybe the vnc gurus on qemu-devel can suggest a way to debug this further.

-- 
error compiling committee.c: too many arguments to function