From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka 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 , Marcelo Tosatti , kvm , qemu-devel To: unlisted-recipients:; (no To-header on input) Return-path: 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 ); Thu, 3 Dec 2009 14:23:46 -0500 In-Reply-To: <4B17DB29.9060801@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NGHHC-0003Qi-0C for qemu-devel@nongnu.org; Thu, 03 Dec 2009 14:23:42 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NGHH5-0003Kp-WC for qemu-devel@nongnu.org; Thu, 03 Dec 2009 14:23:40 -0500 Received: from [199.232.76.173] (port=39753 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NGHH5-0003KY-Hj for qemu-devel@nongnu.org; Thu, 03 Dec 2009 14:23:35 -0500 Received: from thoth.sbs.de ([192.35.17.2]:15929) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NGHH5-0001bM-Ad for qemu-devel@nongnu.org; Thu, 03 Dec 2009 14:23:35 -0500 Message-ID: <4B181033.1020804@siemens.com> Date: Thu, 03 Dec 2009 20:23:31 +0100 From: Jan Kiszka MIME-Version: 1.0 References: <4B17DB29.9060801@siemens.com> In-Reply-To: <4B17DB29.9060801@siemens.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: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Marcelo Tosatti , Avi Kivity , kvm , qemu-devel 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