From: Avi Kivity <avi@redhat.com>
To: qemu-devel <qemu-devel@nongnu.org>,
KVM list <kvm@vger.kernel.org>,
Juan Quintela <quintela@redhat.com>
Subject: Re: Migration issues in qemu.git
Date: Mon, 02 Aug 2010 16:15:53 +0300 [thread overview]
Message-ID: <4C56C509.8040907@redhat.com> (raw)
In-Reply-To: <4C568A85.9040500@redhat.com>
On 08/02/2010 12:06 PM, Avi Kivity wrote:
>
> 2. Intermittent migration failures
>
> Likely suspect is the IDE migration fixes. A merge of the commit just
> before these changes passes the test, I'm now testing the commit
> immediately after the changes.
>
Looks like this was a byproduct of the first problem - my disks filled
up, or became extra slow during the core dump, and caused the failures.
Seems to not to happen now.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-08-02 13:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 9:06 Migration issues in qemu.git Avi Kivity
2010-08-02 9:42 ` Avi Kivity
2010-08-02 13:12 ` Alex Williamson
2010-08-02 13:15 ` Avi Kivity
2010-08-02 13:15 ` Avi Kivity [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=4C56C509.8040907@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--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