From: Gerd Hoffmann <kraxel@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, Anthony Liguori <aliguori@amazon.com>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 04/10] vnc: switch to QemuOpts, allow multiple servers
Date: Tue, 17 Feb 2015 09:50:32 +0100 [thread overview]
Message-ID: <1424163032.6014.18.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <87k2zly8hf.fsf@blackfin.pond.sub.org>
On Fr, 2015-02-13 at 19:25 +0100, Markus Armbruster wrote:
> Gerd Hoffmann <kraxel@redhat.com> writes:
>
> > This patch switches vnc over to QemuOpts, and it (more or less
> > as side effect) allows multiple vnc server instances.
> >
> > Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
>
> I'm afraid this broke monitor command change vnc.
>
> Reproducer
>
> Terminal 1:
>
> $ qemu -nodefaults -S -display vnc=:0 -monitor stdio
> QEMU 2.2.50 monitor - type 'help' for more information
>
> Terminal 2:
>
> $ vncviewer :0
>
> Terminal 1:
>
> (qemu) change vnc :1
>
> Terminal 3:
>
> $ vncviewer :1
>
> Before this patch, vncviewer works both times. The second one kills the
> first one.
>
> After this patch, the first one still works, but the second one fails.
> netstat shows nobody's listening on the port.
Fix for this is on the list already (Gonglei) and included in the
pending vnc pull request.
> Furthermore, the conversion to QemuOpts makes VNC visible in
> -writeconfig, but if you -readconfig it back, it doesn't quite work.
>
> With -display vnc=:0, -writeconfig produces
>
> [vnc]
> vnc = ":0"
>
> If I append that to the config file I -readconfig, I a working VNC
> display on :0 (good), but I also get an SDL display (not good).
Will send a fix to the list in a moment.
cheers,
Gerd
next prev parent reply other threads:[~2015-02-17 8:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 12:53 [Qemu-devel] [PATCH 00/10] vnc: add support for multiple vnc displays Gerd Hoffmann
2015-01-12 12:53 ` [Qemu-devel] [PATCH 01/10] vnc: remove vnc_display global Gerd Hoffmann
2015-01-12 12:53 ` [Qemu-devel] [PATCH 02/10] vnc: remove unused DisplayState parameter, add id instead Gerd Hoffmann
2015-01-12 12:53 ` [Qemu-devel] [PATCH 03/10] vnc: add display id to acl names Gerd Hoffmann
2015-01-12 12:53 ` [Qemu-devel] [PATCH 04/10] vnc: switch to QemuOpts, allow multiple servers Gerd Hoffmann
2015-02-13 18:25 ` Markus Armbruster
2015-02-17 8:50 ` Gerd Hoffmann [this message]
2015-02-17 8:58 ` Gerd Hoffmann
2015-02-17 12:15 ` Markus Armbruster
2015-02-13 18:30 ` Markus Armbruster
2015-01-12 12:53 ` [Qemu-devel] [PATCH 05/10] vnc: allow binding servers to qemu consoles Gerd Hoffmann
2015-01-12 12:53 ` [Qemu-devel] [PATCH 06/10] vnc: update docs/multiseat.txt Gerd Hoffmann
2015-01-12 12:53 ` [Qemu-devel] [PATCH 07/10] vnc: track & limit connections Gerd Hoffmann
2015-01-12 12:53 ` [Qemu-devel] [PATCH 08/10] vnc: factor out qmp_query_client_list Gerd Hoffmann
2015-01-12 12:53 ` [Qemu-devel] [PATCH 09/10] monitor: add query-vnc-servers command Gerd Hoffmann
2015-02-13 19:44 ` Eric Blake
2015-01-12 12:53 ` [Qemu-devel] [PATCH 10/10] monitor: add vnc websockets Gerd Hoffmann
2015-02-13 19:45 ` Eric Blake
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=1424163032.6014.18.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=aliguori@amazon.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=pbonzini@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).