From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NrcuD-0005oT-E4 for qemu-devel@nongnu.org; Tue, 16 Mar 2010 15:58:21 -0400 Received: from [199.232.76.173] (port=48134 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NrcuC-0005o3-T7 for qemu-devel@nongnu.org; Tue, 16 Mar 2010 15:58:20 -0400 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1NrcuC-0003xR-2b for qemu-devel@nongnu.org; Tue, 16 Mar 2010 15:58:20 -0400 Received: from mh2.mail.rice.edu ([128.42.201.21]:35800) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NrcuB-0003vf-QR for qemu-devel@nongnu.org; Tue, 16 Mar 2010 15:58:19 -0400 Received: from mh2.mail.rice.edu (localhost.localdomain [127.0.0.1]) by mh2.mail.rice.edu (Postfix) with ESMTP id C6C88CC00C for ; Tue, 16 Mar 2010 14:57:54 -0500 (CDT) Received: from mh2.mail.rice.edu ([127.0.0.1]) by mh2.mail.rice.edu (mh2.mail.rice.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kdzhhcltd0iS for ; Tue, 16 Mar 2010 14:57:54 -0500 (CDT) Received: from localhost (localhost.localdomain [127.0.0.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jz4) by mh2.mail.rice.edu (Postfix) with ESMTPSA id 8FA7CCC001 for ; Tue, 16 Mar 2010 14:57:54 -0500 (CDT) Message-ID: <20100316145754.17202atrkf8w4udc@webmail.rice.edu> Date: Tue, 16 Mar 2010 14:57:54 -0500 From: jz4@rice.edu Subject: Re: [Qemu-devel] [PATCH 0/3 v5] Live migration without shared storage MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org [Qemu-devel] [PATCH 0/3 v5] Live migration without shared storage I tested the live migration without shared storage for the patch of =20 the block migration. It succeeds for several times but sometimes it =20 fails. I used the qemu-kvm-0.12.3 and the kvm 2.6.33 module on the =20 ubuntu latest version. In the failure case, i can see the shell on the destination site =20 showed the correct content for the migrated VM, but it just hanged =20 there without any response to the mouse and the keyboard. I can see it =20 prints "migration completes" twice. Is it a bug or did I do anything =20 wrong? Another question is about the command line for the destination site. =20 For memory migration, i will start the vm based on the shared image. For block =20 migration, there is no shared image. What i did is creating an empty =20 image with the same format (e.g. raw or qcow2) as the source migrated =20 VM. Is it correct or it doesn't matter which format it is in the =20 destination site? For the memory migration, it emphasizes that the path for the VM =20 should be the same as the source path. But for the block migration, i =20 change the destination path to a different one and it also works. Does =20 that mean path is not important now? The command line must be "migrate -d -b ..". If it is "-b -d", the =20 qemu-monitor doesn't understand. Does that intend to be designed like =20 this or will it be modified in the future? Thanks! -Jie