qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: -serial stdio broken
Date: Sun, 13 Dec 2009 09:38:45 +0000	[thread overview]
Message-ID: <f43fc5580912130138h246ced19i6d248e4ab6251b4f@mail.gmail.com> (raw)
In-Reply-To: <f43fc5580912130024o169488b6wbb9ca7e656b48975@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1857 bytes --]

On Sun, Dec 13, 2009 at 8:24 AM, Blue Swirl <blauwirbel@gmail.com> wrote:
> I guess e1c09175bc00dd8dfb2ad1b26e1858dcdc109b59 or
> 998bbd74b9d813b14a3a3b5009a5d5a48c7dce51 broke -serial stdio for all
> targets:
> qemu -serial stdio -monitor stdio
> chardev: opening backend "stdio" failed
> qemu: could not open serial device 'stdio': No such file or directory
>

e1c09175bc00dd8dfb2ad1b26e1858dcdc109b59 is first bad commit
commit e1c09175bc00dd8dfb2ad1b26e1858dcdc109b59
Author: Gerd Hoffmann <kraxel@redhat.com>
Date:   Tue Dec 8 13:11:44 2009 +0100

    zap serial_monitor_mux

    The logic in this code obviously predates the multiple monitor
    capability of qemu and looks increasingly silly these days.

    I think the intention of this piece of code is to get a reasonable
    default for the -nographic case: have monitor and serial line muxed
    on stdio.

    With the new default_serial and default_monitor variables we have now
    doing just that became much easier ;)

    Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
    Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>

:100644 100644 0d3f5e6687934a94e8586a13b2f5b7432065c430
e3e035f45349c8a2a86317dc46575c899acc8321 M      vl.c

git revert e1c09175bc00dd8dfb2ad1b26e1858dcdc109b59
Auto-merged vl.c
CONFLICT (content): Merge conflict in vl.c
Automatic revert failed.  After resolving the conflicts,
mark the corrected paths with 'git add <paths>' or 'git rm <paths>'
and commit the result.

My attempt to merge (attached) does not compile:
/src/qemu/vl.c: In function 'serial_monitor_mux':
/src/qemu/vl.c:4795: error: 'DEV_MONITOR' undeclared (first use in
this function)
/src/qemu/vl.c:4795: error: (Each undeclared identifier is reported only once
/src/qemu/vl.c:4795: error: for each function it appears in.)

Please fix ASAP, this happens to break my test setup completely.

[-- Attachment #2: 0001-Revert-zap-serial_monitor_mux.patch --]
[-- Type: application/x-patch, Size: 2453 bytes --]

  reply	other threads:[~2009-12-13  9:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-13  8:24 [Qemu-devel] -serial stdio broken Blue Swirl
2009-12-13  9:38 ` Blue Swirl [this message]
2009-12-14 10:55   ` [Qemu-devel] " Gerd Hoffmann
2009-12-14 16:50     ` Blue Swirl
2009-12-14 17:12       ` Gerd Hoffmann
2010-01-07 11:55 ` [Qemu-devel] " Richard W.M. Jones
2010-01-07 12:10   ` Richard W.M. Jones
2010-01-07 12:32     ` Gerd Hoffmann
2010-01-07 13:25       ` Richard W.M. Jones
2010-01-07 16:01         ` Anthony Liguori
2010-01-07 12:35     ` Anthony Liguori
2010-01-07 12:34   ` Anthony Liguori
2010-01-07 12:44     ` Daniel P. Berrange
2010-01-07 13:23       ` Anthony Liguori
2010-01-07 13:27       ` Richard W.M. Jones

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=f43fc5580912130138h246ced19i6d248e4ab6251b4f@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --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 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).