From: Jan Kiszka <jan.kiszka@siemens.com>
To: Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org, Pierre Riteau <Pierre.Riteau@irisa.fr>
Subject: [Qemu-devel] live migration of 64-bit kvm guest (was: [BUG] Migration broken by "e1000: port to vmstate")
Date: Tue, 01 Dec 2009 14:22:09 +0100 [thread overview]
Message-ID: <4B151881.6050109@siemens.com> (raw)
In-Reply-To: <m3d4303xh6.fsf@neno.neno>
Juan Quintela wrote:
> Jan Kiszka <jan.kiszka@siemens.com> wrote:
>> Juan Quintela wrote:
>>> 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.
>>>
>> Confirmed here - the hard way, ie. after debugging a while on my own
>> patches. My scenario is default command line + -enable-kvm, migration to
>> file (exec:cat), then restore from that file. Restore fails while
>> reading the e1000 state with EOF.
>>
>>> I will take at that two bugs this week. I tested everything on 64bit
>>> hosts.
>> Any news on this?
>
> nope, migration backwards took more time that I wanted.
>
> Will take a look tomorrow.
>
I'm currently pulling hair while trying to migrate a 64-bit x86 guest in
kvm mode (via exec+snapshot file, but without block migration and any of
my patches). The target crashes after taking over.
Are you aware of any 64-bit migration issues related to kvm (as you said
there are more bugs)? 32 bit works fine here.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2009-12-01 13:22 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 ` [Qemu-devel] " Juan Quintela
2009-11-24 17:02 ` 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 ` Jan Kiszka [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=4B151881.6050109@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Pierre.Riteau@irisa.fr \
--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).