From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH v2] Make VNC support optional
Date: Fri, 11 Mar 2011 16:05:21 +0100 [thread overview]
Message-ID: <4D7A3A31.2040008@redhat.com> (raw)
In-Reply-To: <4D7A37ED.7020505@codemonkey.ws>
On 03/11/11 15:55, Anthony Liguori wrote:
> On 03/11/2011 08:54 AM, Jes Sorensen wrote:
>> On 03/11/11 15:39, Anthony Liguori wrote:
>>>> +#ifdef CONFIG_VNC
>>>> /* init remote displays */
>>>> if (vnc_display) {
>>>> vnc_display_init(ds);
>>>> @@ -3088,6 +3095,7 @@ int main(int argc, char **argv, char **envp)
>>>> printf("VNC server running on `%s'\n",
>>>> vnc_display_local_addr(ds));
>>>> }
>>>> }
>>>> +#endif
>>> So what ends up being the default display if VNC and SDL are both
>>> disabled? Have you tested this?
>> Then you cry :) actually you just don't get video output, a bit like if
>> you run with -nographic, except it doesn't try to force taking over
>> stdio. This is intentional btw :)
>
> Hrm, that doesn't sound very safe to me. Forcing -nographic would be
> better IMHO.
-nographic is bad, it forces a takeover of stdio preventing you from
running the monitor on stdio in this case. Not necessarily what you
want. We could do an alternative mode for this, but -nographic is not
what we want in this case.
Cheers,
Jes
next prev parent reply other threads:[~2011-03-11 15:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 14:37 [Qemu-devel] [PATCH v2] Make VNC support optional Jes.Sorensen
2011-03-11 14:39 ` [Qemu-devel] " Anthony Liguori
2011-03-11 14:54 ` Jes Sorensen
2011-03-11 14:55 ` Anthony Liguori
2011-03-11 15:05 ` Jes Sorensen [this message]
2011-03-11 15:11 ` Peter Maydell
2011-03-11 15:50 ` Anthony Liguori
2011-03-11 16:30 ` Jes Sorensen
2011-03-11 17:09 ` Anthony Liguori
2011-03-11 16:35 ` Jan Kiszka
2011-03-14 9:35 ` Jes Sorensen
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=4D7A3A31.2040008@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=anthony@codemonkey.ws \
--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).