From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MbfLs-0000zv-TB
	for qemu-devel@nongnu.org; Thu, 13 Aug 2009 14:48:40 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MbfLo-0000vj-8K
	for qemu-devel@nongnu.org; Thu, 13 Aug 2009 14:48:40 -0400
Received: from [199.232.76.173] (port=41738 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MbfLo-0000va-1E
	for qemu-devel@nongnu.org; Thu, 13 Aug 2009 14:48:36 -0400
Date: Thu, 13 Aug 2009 15:48:27 -0300
From: Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] save/restore broken?
Message-ID: <20090813154827.409ed832@doriath>
In-Reply-To: <h5s6sk$ema$1@ger.gmane.org>
References: <h5s6sk$ema$1@ger.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: qemu-devel@nongnu.org, gleb@redhat.com

On Tue, 11 Aug 2009 18:39:47 +0200
Paolo Bonzini <bonzini@gnu.org> wrote:

> Hi all,
> 
> if I try to save and restore an image using current qemu and current 
> libvirt, the load fails.

 Yes, it's broken. I'm unable to loadvm and to migrate.

 According to git bisect the problem was introduced by:

"""
commit 93c8cfd9e67a62711b86f4c93747566885eb7928
Author: Gleb Natapov <gleb@redhat.com>
Date:   Sun Aug 2 11:36:47 2009 +0300

    make windows notice media change
"""

 Indeed, reverting this fixes it for me.

 When I try to loadvm I get this error:

"""
Unknown savevm section type 255
Error -22 while loading VM state
"""

 The migration symptoms are different. Sometimes it
prints the same message, sometimes it kind of works
but gets strange behaviors.