From: Anthony Liguori <anthony@codemonkey.ws>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] add VNC reverse connections
Date: Wed, 16 Jan 2008 09:00:21 -0600 [thread overview]
Message-ID: <478E1C05.9050703@codemonkey.ws> (raw)
In-Reply-To: <20080116124231.GB16624@redhat.com>
Daniel P. Berrange wrote:
> On Tue, Jan 15, 2008 at 11:27:15PM -0800, Eddie Kohler wrote:
>
>> Hi all,
>>
>> This patch against current CVS adds VNC reverse connections, where the
>> server connects actively to a waiting client, as in "-vnc rev:5500" or
>> "-vnc rev:read.cs.ucla.edu:5500". This is quite useful if the user expects
>> to run QEMU many times in succession (for example, is debugging a toy OS),
>> and doesn't want to reopen a VNC client each time.
>>
>
> We already have the ability to pass multiple flags / options to the VNC
> driver as a post-fix to the host:port pair, so I'm not a fan of introducing
> a new option as a prefix. If using existing options syntax, it could look
> like:
>
> -vnc :5500,rev
> -vnc read.cs.ucla.edu:5500,rev
>
Yes, but please, let's spell out "reverse". This is a very nice patch
to have as it's another way (than -daemonize) to reliably connect to the
vnc server after launching a VM.
Regards,
Anthony Liguori
> Regards,
> Dan.
>
next prev parent reply other threads:[~2008-01-16 15:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 7:27 [Qemu-devel] [PATCH] add VNC reverse connections Eddie Kohler
2008-01-16 8:55 ` Avi Kivity
2008-01-16 12:42 ` Daniel P. Berrange
2008-01-16 15:00 ` Anthony Liguori [this message]
2008-01-16 15:09 ` Eddie Kohler
2008-01-16 16:31 ` Anthony Liguori
2008-01-16 16:35 ` Daniel P. Berrange
2008-01-17 0:04 ` Anthony Liguori
2008-01-17 0:51 ` Eddie Kohler
2008-01-17 16:29 ` Eddie Kohler
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=478E1C05.9050703@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=berrange@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).