From: Avi Kivity <avi@redhat.com>
To: Andreas Olsowski <andreas.olsowski@uni-lueneburg.de>
Cc: kvm@vger.kernel.org, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Unable to re-establish VNC connection after some time
Date: Sun, 15 Mar 2009 15:18:29 +0200 [thread overview]
Message-ID: <49BD0025.5070600@redhat.com> (raw)
In-Reply-To: <167037245.20090312211043@uni-lueneburg.de>
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
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Andreas Olsowski <andreas.olsowski@uni-lueneburg.de>
Cc: qemu-devel <qemu-devel@nongnu.org>, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: Unable to re-establish VNC connection after some time
Date: Sun, 15 Mar 2009 15:18:29 +0200 [thread overview]
Message-ID: <49BD0025.5070600@redhat.com> (raw)
In-Reply-To: <167037245.20090312211043@uni-lueneburg.de>
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
next prev parent reply other threads:[~2009-03-15 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 20:10 Unable to re-establish VNC connection after some time Andreas Olsowski
2009-03-15 13:18 ` Avi Kivity [this message]
2009-03-15 13:18 ` [Qemu-devel] " Avi Kivity
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=49BD0025.5070600@redhat.com \
--to=avi@redhat.com \
--cc=andreas.olsowski@uni-lueneburg.de \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.