From: "Daniel P. Berrange" <berrange@redhat.com>
To: risc@volumehost.com
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] bdrv_flush error handling
Date: Thu, 21 Feb 2008 18:24:14 +0000 [thread overview]
Message-ID: <20080221182414.GO15883@redhat.com> (raw)
In-Reply-To: <20080221172823.GD14090@volumehost.com>
On Thu, Feb 21, 2008 at 11:28:23AM -0600, risc@volumehost.com wrote:
> On Thu, Feb 21, 2008 at 05:24:10PM +0000, Daniel P. Berrange wrote:
> > On Thu, Feb 21, 2008 at 12:19:22PM -0500, Ben Taylor wrote:
> > > > > Also, in block-raw-posix.c, raw_pwrite et al seem to return -1 on
> > > > > error (the return value from write) whereas the other block read/write
> > > > > methods return errno values. This is a mistake, surely ? -1 would be
> > > > > -EPERM. If any of the callers did anything with these return values
> > > > > you'd get incorrect error indications.
> > > > >
> > > > >
> > > > > Finally, it would perhaps be best if the block device emulators wrote
> > > > > to the qemu console to complain if they give write errors. Otherwise
> > > > > the errno value and other important information will be lost, which
> > > > > makes debugging hard.
> > > >
> > > > If by 'qemu console' you mean stderr, then fine, but please don't
> > > > spew log messages to the monitor console, because that'll make it
> > > > very hard to interact with reliably from management tools.
> > >
> > > Would it make sense to have a log messages screen associated with
> > > the monitor (like Ctrl-Alt-7) to deal with those sorts of things?
> >
> > Why invent a new special QEMU log screen, when stderr works just fine. If an
> > app wants to capture log messages they just capture stderr and persist it.
> > We already capture stderr for exactly this reason in libvirt when managing
> > QEMU instances.
>
> Please excuse my intrusion in this thread, but I'm a user of the new
> ncurses user interface. when ssh'd in, running qemu, I don't believe
> having messages pop out of stderr and over the current screen contents is
> the appropriate behavior, as it sounds to me like it would cause redraw
> defects in the normal text console (via ncurses)
So just redirect stderr to a logfile, or /dev/null, etc, etc
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
next prev parent reply other threads:[~2008-02-21 18:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 15:53 [Qemu-devel] [PATCH] bdrv_flush error handling Ian Jackson
2008-02-20 16:04 ` Daniel P. Berrange
2008-02-20 16:13 ` Ian Jackson
2008-02-20 16:19 ` Paul Brook
2008-02-20 16:23 ` Avi Kivity
2008-02-20 16:37 ` Ian Jackson
2008-02-20 16:46 ` Paul Brook
2008-02-20 16:53 ` Ian Jackson
2008-02-20 16:31 ` Jamie Lokier
2008-02-20 18:17 ` Paul Brook
2008-02-20 16:38 ` Jamie Lokier
2008-02-20 18:22 ` Daniel P. Berrange
2008-02-20 19:01 ` Anthony Liguori
2008-02-20 19:55 ` Rick Vernam
2008-02-21 7:10 ` Thomas Irlet
2008-02-21 17:19 ` Ben Taylor
2008-02-21 17:24 ` Daniel P. Berrange
2008-02-21 17:28 ` risc
2008-02-21 18:24 ` Daniel P. Berrange [this message]
2008-03-28 17:19 ` [Qemu-devel] " Ian Jackson
2008-04-26 15:15 ` andrzej zaborowski
2008-04-29 16:27 ` Ian Jackson
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=20080221182414.GO15883@redhat.com \
--to=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=risc@volumehost.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 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).