From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NGYAH-0005Zo-Mv
	for qemu-devel@nongnu.org; Fri, 04 Dec 2009 08:25:41 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NGYAA-0005Xk-DR
	for qemu-devel@nongnu.org; Fri, 04 Dec 2009 08:25:39 -0500
Received: from [199.232.76.173] (port=33452 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NGYA8-0005XM-Dn
	for qemu-devel@nongnu.org; Fri, 04 Dec 2009 08:25:32 -0500
Received: from thoth.sbs.de ([192.35.17.2]:20963)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <jan.kiszka@siemens.com>) id 1NGYA8-00014W-3l
	for qemu-devel@nongnu.org; Fri, 04 Dec 2009 08:25:32 -0500
Message-ID: <4B190DC8.60005@siemens.com>
Date: Fri, 04 Dec 2009 14:25:28 +0100
From: Jan Kiszka <jan.kiszka@siemens.com>
MIME-Version: 1.0
References: <4B17DB29.9060801@siemens.com> <4B181033.1020804@siemens.com>
	<4B18C176.7050105@redhat.com>
In-Reply-To: <4B18C176.7050105@redhat.com>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Re: Bugs in kvm guest migration
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: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>

Avi Kivity wrote:
> On 12/03/2009 09:23 PM, Jan Kiszka wrote:
>> 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...
>>    
> 
> Does calling drop_user_return_notifiers() (static in x86.c, will need 
> exporting) in vmx_load_host_state() within the preempt-disable region help?
> 

Nope.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux