From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:32937)
	by lists.gnu.org with esmtp (Exim 4.71) (envelope-from <pl@kamp.de>)
	id 1WiXQQ-0006Gf-9i
	for qemu-devel@nongnu.org; Thu, 08 May 2014 19:08:35 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <pl@kamp.de>) id 1WiXQH-0006yg-8o
	for qemu-devel@nongnu.org; Thu, 08 May 2014 19:08:26 -0400
Received: from mx-v6.kamp.de ([2a02:248:0:51::16]:44647 helo=mx01.kamp.de)
	by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from <pl@kamp.de>)
	id 1WiXQG-0006xh-TO
	for qemu-devel@nongnu.org; Thu, 08 May 2014 19:08:17 -0400
Message-ID: <536C0E5A.2030703@kamp.de>
Date: Fri, 09 May 2014 01:08:10 +0200
From: Peter Lieven <pl@kamp.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Question about RAM migration flags
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Orit Wasserman <owasserm@redhat.com>, quintela@redhat.com, Stefan Hajnoczi <stefanha@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>

Hi,

while working on ram migration and reading through the code I realized that
qemu does not stop loading a saved VM or rejecting an incoming migration
if there is a flag in the stream that it does not understand. An unknown flag
is simply ignored.

In the block migration code there is a catch at the end complaining about
unknown flags, but in RAM migration there isn't.

Is this on purpose or an error?

Peter