From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [PATCH 10/11] VMX: work around lacking VNMI support Date: Wed, 24 Sep 2008 15:33:13 +0200 Message-ID: <48DA4199.10900@siemens.com> References: <48D74CE6.5060008@siemens.com> <200809231742.03316.sheng.yang@intel.com> <20080923094544.GE3072@minantech.com> <200809231750.49882.sheng.yang@intel.com> <48DA3532.9040306@siemens.com> <20080924125057.GF3072@minantech.com> <48DA3908.2000204@siemens.com> <20080924130236.GG3072@minantech.com> <48DA3BB4.80708@siemens.com> <20080924132412.GJ3072@minantech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "Yang, Sheng" , kvm-devel , Avi Kivity To: Gleb Natapov Return-path: Received: from lizzard.sbs.de ([194.138.37.39]:22587 "EHLO lizzard.sbs.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751151AbYIXNdf (ORCPT ); Wed, 24 Sep 2008 09:33:35 -0400 In-Reply-To: <20080924132412.GJ3072@minantech.com> Sender: kvm-owner@vger.kernel.org List-ID: Gleb Natapov wrote: > On Wed, Sep 24, 2008 at 03:08:04PM +0200, Jan Kiszka wrote: >>> It does power-off, but hands during reboot. Looking at it right now. >> After completing the RAM read-back from disk? This is where it hangs > Much earlier. BIOS hangs because CPU1 ignores SIPI. That sounds like an APIC state reset issue. BTW, I'm getting tons of Ignoring de-assert INIT to vcpu 0 Ignoring de-assert INIT to vcpu 1 Ignoring de-assert INIT to vcpu 0 Ignoring de-assert INIT to vcpu 1 Ignoring de-assert INIT to vcpu 1 SIPI to vcpu 1 vector 0x24 vcpu 1 received sipi with vector # 24 SIPI to vcpu 1 vector 0x24 SIPI to vcpu 1 vector 0x24 Ignoring de-assert INIT to vcpu 0 Ignoring de-assert INIT to vcpu 1 SIPI to vcpu 1 vector 0x24 on my box with SMP guests (Linux and Windows). Do they all point to yet incomplete emulations, or are they just far too verbose? Jan