From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: ???? <chenliang0016@icloud.com>
Cc: armbru@redhat.com, qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 1/1] Make qemu_peek_buffer loop until it gets it's data
Date: Wed, 9 Apr 2014 13:59:19 +0100 [thread overview]
Message-ID: <20140409125918.GE2584@work-vm> (raw)
In-Reply-To: <6E9C1B08-A777-43F8-9D31-9ACA633E689B@icloud.com>
* ???? (chenliang0016@icloud.com) wrote:
>
> > * ???? (chenliang0016@icloud.com) wrote:
> >>
> >>> * ???? (chenliang0016@icloud.com) wrote:
> >>>>
> >>>> ?? 2014??4??8????????10:29??Dr. David Alan Gilbert (git) <dgilbert@redhat.com> ??????
> >>>>
> >>>>> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> >>>>>
> >>>>> Make qemu_peek_buffer repeatedly call fill_buffer until it gets
> >>>>> all the data it requires, or until there is an error.
> >>>>>
> >>>>> At the moment, qemu_peek_buffer will try one qemu_fill_buffer if there
> >>>>> isn't enough data waiting, however the kernel is entitled to return
> >>>>> just a few bytes, and still leave qemu_peek_buffer with less bytes
> >>>>> than it needed. I've seen this fail in a dev world, and I think it
> >>>>> could theoretically fail in the peeking of the subsection headers in
> >>>>> the current world.
> >>>> hmm, I also have got some errors(infrequently). Maybe It is one point.
> >>>> Could you show some messages about the error?
> >>>
> >>> I've only seen the errors in my visitor/ber world where I use the peek_buffer
> >>> a lot more; but the one place it is used in the existing code is in
> >>> the code to check if we have the start of a subsection; if that goes wrong
> >>> I'm not sure what error would be produced.
> >>>
> >>> Dave
> >> In my observation, error is more likely to happen if migration thread is blocked too long.
> >> BTW, xbzrle and auto convergence are disable.
> >
> > What error do you see?
> >
> > Dave
> It likes section id 1 load failed at dest side.
Our migration errors aren't particularly descriptive :-(
However, try it with this patch - I'd be interested if it makes
your problem go away.
Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
prev parent reply other threads:[~2014-04-09 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 14:29 [Qemu-devel] [PATCH v4 1/1] Make qemu_peek_buffer loop until it gets it's data Dr. David Alan Gilbert (git)
[not found] ` <E8EF2F0B-69B0-4AD0-BC79-4AAD5EA6921C@icloud.com>
2014-04-08 16:08 ` Dr. David Alan Gilbert
2014-04-09 11:56 ` 陈梁
2014-04-09 11:58 ` Dr. David Alan Gilbert
2014-04-09 12:00 ` 陈梁
2014-04-09 12:59 ` Dr. David Alan Gilbert [this message]
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=20140409125918.GE2584@work-vm \
--to=dgilbert@redhat.com \
--cc=armbru@redhat.com \
--cc=chenliang0016@icloud.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).