From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] chardev's and fd's in monitors
Date: Fri, 21 Oct 2016 12:56:03 +0100 [thread overview]
Message-ID: <20161021115603.GF2039@work-vm> (raw)
In-Reply-To: <20161021093756.GC6585@redhat.com>
* Daniel P. Berrange (berrange@redhat.com) wrote:
> On Fri, Oct 21, 2016 at 11:06:21AM +0200, Markus Armbruster wrote:
> > "Dr. David Alan Gilbert" <dgilbert@redhat.com> writes:
> >
> > > * Markus Armbruster (armbru@redhat.com) wrote:
> > >> "Daniel P. Berrange" <berrange@redhat.com> writes:
> > [...]
> > >> > Realistically all the major backend subsystems (chardev, network, block,
> > >> > ui and migration) need to be converted to Error ** propagation, since
> > >> > they all ultimately call into some common code that reports Error **.
> > >>
> > >> Infrastucture generally doesn't know how it's used, which means
> > >> error_report() is generally wrong there. Sufficiently simple functions
> > >> can keep returning -errno, null, whatever, but the interesting stuff
> > >> needs to use Error.
> > >> > Very few places will end up being able to stick with -errno, or plain
> > >> > error_report in the long term.
> > >>
> > >> Not sure about "very few". Less than now. We'll see.
> > >
> > > I'd also prefer we got the very-few level; Migration used to be
> > > characterised by getting a 'load of migration failed -22' and having
> > > no clue in the logs to why; I've slowly fought back to be able
> > > to get an error from the lowest level that caused the failure.
> > > I want more of that, so that when someone gets a rare failure in the field
> > > I can see why.
> >
> > When it's about details that are only useful for debugging, logging
> > might be a practical alternative. No excuse for shoddy error reporting,
> > of course.
>
> FWIW, I would very much like it if incoming migration were able to report
> the error failing to load migration stream back via the monitor, instead
> of spitting them to stderr - the latter makes it hard for libvirt to
> provide good error report to the users.
As long as we also get them in the stderr log then that's fine.
Dave
> On the outgoing side we've now fed the errors back via the query-migrate
> command - the same approach could be used on the incoming side.
>
>
> Regards,
> Daniel
> --
> |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
> |: http://libvirt.org -o- http://virt-manager.org :|
> |: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :|
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2016-10-21 11:56 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 19:15 [Qemu-devel] chardev's and fd's in monitors Dr. David Alan Gilbert
2016-10-12 20:02 ` Marc-André Lureau
2016-10-13 15:47 ` Dr. David Alan Gilbert
2016-10-18 10:04 ` Daniel P. Berrange
2016-10-18 11:32 ` Dr. David Alan Gilbert
2016-10-18 11:41 ` Marc-André Lureau
2016-10-18 11:44 ` Marc-André Lureau
2016-10-18 12:01 ` Daniel P. Berrange
2016-10-18 13:25 ` Dr. David Alan Gilbert
2016-10-18 13:35 ` Daniel P. Berrange
2016-10-18 13:52 ` Dr. David Alan Gilbert
2016-10-18 14:01 ` Daniel P. Berrange
2016-10-18 18:53 ` Dr. David Alan Gilbert
2016-10-19 7:45 ` Daniel P. Berrange
2016-10-19 8:00 ` Markus Armbruster
2016-10-19 8:12 ` Dr. David Alan Gilbert
2016-10-19 8:42 ` Daniel P. Berrange
2016-10-19 9:48 ` Markus Armbruster
2016-10-19 10:05 ` Dr. David Alan Gilbert
2016-10-19 10:16 ` Daniel P. Berrange
2016-10-19 12:16 ` Markus Armbruster
2016-10-19 12:21 ` Daniel P. Berrange
2016-10-19 18:06 ` Dr. David Alan Gilbert
2016-10-20 8:37 ` Daniel P. Berrange
2016-10-20 8:53 ` Marc-André Lureau
2016-10-20 10:45 ` Markus Armbruster
2016-10-20 16:56 ` Paolo Bonzini
2016-10-21 9:12 ` Markus Armbruster
2016-10-21 21:06 ` Paolo Bonzini
2016-10-24 7:07 ` Markus Armbruster
2016-10-21 9:35 ` Daniel P. Berrange
2016-10-20 16:59 ` Dr. David Alan Gilbert
2016-10-20 8:55 ` Markus Armbruster
2016-10-20 9:03 ` Daniel P. Berrange
2016-10-20 9:58 ` Dr. David Alan Gilbert
2016-10-20 10:42 ` Markus Armbruster
2016-10-20 11:01 ` Dr. David Alan Gilbert
2016-10-20 11:10 ` Daniel P. Berrange
2016-10-20 11:45 ` Markus Armbruster
2016-10-20 11:08 ` Daniel P. Berrange
2016-10-20 11:57 ` Markus Armbruster
2016-10-20 17:56 ` Dr. David Alan Gilbert
2016-10-21 9:06 ` Markus Armbruster
2016-10-21 9:37 ` Daniel P. Berrange
2016-10-21 11:56 ` Dr. David Alan Gilbert [this message]
2016-10-21 9:45 ` Dr. David Alan Gilbert
2016-10-19 12:26 ` Paolo Bonzini
2016-10-19 17:01 ` Dr. David Alan Gilbert
2016-10-19 20:51 ` Paolo Bonzini
2016-10-20 8:34 ` Daniel P. Berrange
2016-10-18 12:08 ` Markus Armbruster
2016-10-18 12:13 ` Daniel P. Berrange
2016-10-18 12:43 ` Dr. David Alan Gilbert
2016-10-18 10:06 ` Daniel P. Berrange
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=20161021115603.GF2039@work-vm \
--to=dgilbert@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@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).