From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/3] sockets: switch vnc to new code, support vnc port auto-allocation.
Date: Tue, 11 Nov 2008 14:52:22 -0600 [thread overview]
Message-ID: <4919F086.2050509@codemonkey.ws> (raw)
In-Reply-To: <1225730550-31941-3-git-send-email-kraxel@redhat.com>
Gerd Hoffmann wrote:
> This patch switches the vnc code ofer to the new socket helper
> functions.
>
> It adds support IPv6 support and for automatically allocating an unused
> vnc display port. The latter is handled ising a to= option, specifying
> the upper limit for the display number to try. Scanning is started at
> the display number given in the display specification, i.e. this command
> line:
>
> -vnc localhost:7,to=11
>
> will try displays 7 to 11 (inclusive).
>
> There are also new "ipv4" and "ipv6" options to make qemu try only
> the specified internet protocol version.
>
> The display actually allocated can be queried using the "info vnc"
> monitor command.
>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Applied. Thanks.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2008-11-11 20:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 16:42 [Qemu-devel] [PATCH v3 0/3] ipv6 and autoport patches Gerd Hoffmann
2008-11-03 16:42 ` [Qemu-devel] [PATCH 1/3] sockets: helper functions for qemu Gerd Hoffmann
2008-11-04 12:42 ` [Qemu-devel] " Gerd Hoffmann
2008-11-11 20:41 ` [Qemu-devel] " Anthony Liguori
2008-11-11 21:14 ` Gerd Hoffmann
2008-11-11 20:47 ` Anthony Liguori
2008-11-03 16:42 ` [Qemu-devel] [PATCH 2/3] sockets: switch vnc to new code, support vnc port auto-allocation Gerd Hoffmann
2008-11-11 20:52 ` Anthony Liguori [this message]
2008-11-26 23:25 ` Ryan Harper
2008-11-27 9:11 ` Gerd Hoffmann
2008-11-03 16:42 ` [Qemu-devel] [PATCH 3/3] sockets: switch over tcp/telnet/unix serial line to new helper functions Gerd Hoffmann
2008-11-11 20:54 ` Anthony Liguori
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=4919F086.2050509@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=kraxel@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 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.