From: Michael Tokarev <mjt@tls.msk.ru>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Hitoshi Mitake <h.mitake@gmail.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@gmail.com>
Subject: Re: [Qemu-devel] [PATCH v2] stop using stdio for monitor/serial/etc with -daemonize
Date: Wed, 26 Sep 2012 11:09:00 +0400 [thread overview]
Message-ID: <5062AA0C.60303@msgid.tls.msk.ru> (raw)
In-Reply-To: <876271ol4w.fsf@codemonkey.ws>
On 26.09.2012 01:19, Anthony Liguori wrote:
> Combining -nographic and -daemonize don't make sense. I'd rather error
> out with this combination.
>
> I think what the user is after is -daemonize -vga none OR -daemonize
> -display none.
So what's the difference?
I know lots of people use -nographic -daemonize to run headless
guests in background (like, for example, a router). I guess it
come way before -vga option has been introduced, but at least I
know about -vga (but not about -vga none). For one, I never saw
-display before. And it looks like -nographic is a synonym for
-display none, and -curses is a synonym for -display curses.
It looks like we have way too many confusing options doing the
same thing. And I think they should be consistent, at least
when they SMELL like they do the same thing, instead of forbidding
one or another in some situations.
Besides, the patch which I based my change on, "curses: don't initialize
curses when qemu is daemonized", probably makes no sense too, since
it is a situation with -curses -daemonize (or, -- is there a difference? --
-display curses -daemonize). That situation is better be errored
out than worked around, I think. (You just pulled that patch from
Stefanha).
Thanks,
/mjt
next prev parent reply other threads:[~2012-09-26 7:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 14:48 [Qemu-devel] [PATCH v2] stop using stdio for monitor/serial/etc with -daemonize Michael Tokarev
2012-09-25 21:19 ` Anthony Liguori
2012-09-26 7:09 ` Michael Tokarev [this message]
2012-09-26 8:00 ` Peter Maydell
2012-09-26 8:17 ` Michael Tokarev
2012-09-26 8:43 ` Peter Maydell
2012-09-26 13:46 ` Anthony Liguori
2012-09-26 14:56 ` Michael Tokarev
2012-10-27 11:23 ` Michael Tokarev
2012-10-27 11:33 ` Peter Maydell
2012-10-27 12:15 ` Michael Tokarev
2012-10-27 12:48 ` Blue Swirl
2012-10-27 12:55 ` Michael Tokarev
2012-10-27 13:11 ` Michael Tokarev
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=5062AA0C.60303@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=anthony@codemonkey.ws \
--cc=h.mitake@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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.