From: Chris Lalancette <clalance@redhat.com>
To: Daniel Hasler <daniel.hasler@hasware.ch>
Cc: kvm@vger.kernel.org
Subject: Re: Live Migration fails
Date: Wed, 30 Jul 2008 09:11:16 +0200 [thread overview]
Message-ID: <48901414.6050603@redhat.com> (raw)
In-Reply-To: <488F88BE.1090504@hasware.ch>
Daniel Hasler wrote:
> After a while, on host B (the target), I see the following error:
> >migration: wait_for_go: read error len=0 (Interrupted system call)
> >Migration failed rc=210
>
> while on host A, I read following error message:
> >WAIT FOR ACK: timeout reached
> >Migration failed! ret=0 error=13
No, this is a bug I just fixed yesterday in Qemu proper. The next time that Avi
rebases KVM to Qemu (which he said he would do as soon as the fix went into
Qemu), then this should be fixed.
FYI, the problem is basically that the i2c restore on the destination side was
expecting 4 bytes, while the i2c save on the sending side was only sending 1
byte, so they eventually timed out while waiting for each other.
Chris Lalancette
next prev parent reply other threads:[~2008-07-30 7:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 21:16 Live Migration fails Daniel Hasler
2008-07-30 7:11 ` Chris Lalancette [this message]
2008-07-30 14:36 ` Anthony Liguori
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=48901414.6050603@redhat.com \
--to=clalance@redhat.com \
--cc=daniel.hasler@hasware.ch \
--cc=kvm@vger.kernel.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