From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NFSgO-0002DK-71 for qemu-devel@nongnu.org; Tue, 01 Dec 2009 08:22:20 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NFSgJ-00026f-6N for qemu-devel@nongnu.org; Tue, 01 Dec 2009 08:22:19 -0500 Received: from [199.232.76.173] (port=40450 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NFSgI-00026P-Mh for qemu-devel@nongnu.org; Tue, 01 Dec 2009 08:22:14 -0500 Received: from david.siemens.de ([192.35.17.14]:18433) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NFSgH-0007ja-Lx for qemu-devel@nongnu.org; Tue, 01 Dec 2009 08:22:14 -0500 Message-ID: <4B151881.6050109@siemens.com> Date: Tue, 01 Dec 2009 14:22:09 +0100 From: Jan Kiszka MIME-Version: 1.0 References: <4B13D24C.3090802@siemens.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] live migration of 64-bit kvm guest (was: [BUG] Migration broken by "e1000: port to vmstate") List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Juan Quintela Cc: qemu-devel@nongnu.org, Pierre Riteau Juan Quintela wrote: > Jan Kiszka wrote: >> Juan Quintela wrote: >>> Pierre Riteau 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