From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: Bugs in kvm guest migration
Date: Thu, 03 Dec 2009 20:23:31 +0100
Message-ID: <4B181033.1020804@siemens.com>
References: <4B17DB29.9060801@siemens.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
Cc: Avi Kivity <avi@redhat.com>, Marcelo Tosatti <mtosatti@redhat.com>,
	kvm <kvm@vger.kernel.org>, qemu-devel <qemu-devel@nongnu.org>
To: unlisted-recipients:; (no To-header on input)
Return-path: <kvm-owner@vger.kernel.org>
Received: from thoth.sbs.de ([192.35.17.2]:15954 "EHLO thoth.sbs.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1755680AbZLCTXq (ORCPT <rfc822;kvm@vger.kernel.org>);
	Thu, 3 Dec 2009 14:23:46 -0500
In-Reply-To: <4B17DB29.9060801@siemens.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Jan Kiszka wrote:
> Problem 2
> ---------
> Setup: qemu head with vmstate fixes. kvm-kmod master, 64-bit host & guest.
> Effect: The migration target either locks up or reboots immediately.
> I've nailed this down to 84d0b66c778d881eafca2a5d0d66678211c4e861. Every
> kvm module build before that works, everything including and after
> 26ede77f536d1bb369527a96c7fe7fdc8ba2f890 shows the effect (everything in
> between crashes the host for known reasons). It's still unclear if this
> is an kvm-kmod wrapping issue of the user-space return notifiers. Will
> check once problem #1 is understood.

It is kernel-related, using kvm.git as host kernel makes no difference.

This may now mean that kvm is buggy or that it triggers some msr
save/restore related issues in qemu. Digging even deeper...

Jan