From: Juan Quintela <quintela@redhat.com>
To: Pierre Riteau <Pierre.Riteau@irisa.fr>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [BUG] Migration broken by "e1000: port to vmstate"
Date: Tue, 24 Nov 2009 17:46:07 +0100 [thread overview]
Message-ID: <m3fx83eur4.fsf@neno.neno> (raw)
In-Reply-To: <AB153FBE-73FF-4984-9337-C1A7C8191348@irisa.fr> (Pierre Riteau's message of "Tue, 24 Nov 2009 16:04:59 +0100")
Pierre Riteau <Pierre.Riteau@irisa.fr> wrote:
> e482dc3eaac43f88beea133843ae38c661262e97 breaks migration of a VM using an e1000 device (which is the default...).
> Origin host is Debian Lenny 32-bits, destination host is Fedora 12 32-bit. Guest is running Debian Lenny 32-bit.
> Symtoms: origin finishes migration correctly, but destination prints "load of migration failed" and the VM is stopped.
>
> This is because the origin closed the connexion, so qemu_fill_buffer reads a buffer with len == 0, which is treated as an error later (f->has_error = 1).
> Reverting e482dc3eaac43f88beea133843ae38c661262e97 fixes the problem.
Do you use --enable-kvm? That could explain it.
I will take at that two bugs this week. I tested everything on 64bit
hosts.
Later, Juan.
next prev parent reply other threads:[~2009-11-24 16:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 15:04 [Qemu-devel] [BUG] Migration broken by "e1000: port to vmstate" Pierre Riteau
2009-11-24 16:27 ` Ryan Harper
2009-11-24 17:01 ` Pierre Riteau
2009-11-24 16:46 ` Juan Quintela [this message]
2009-11-24 17:02 ` [Qemu-devel] " Pierre Riteau
2009-11-30 14:10 ` Jan Kiszka
2009-11-30 14:14 ` Jan Kiszka
2009-11-30 14:20 ` Juan Quintela
2009-12-01 13:22 ` [Qemu-devel] live migration of 64-bit kvm guest (was: [BUG] Migration broken by "e1000: port to vmstate") Jan Kiszka
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=m3fx83eur4.fsf@neno.neno \
--to=quintela@redhat.com \
--cc=Pierre.Riteau@irisa.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.