From mboxrd@z Thu Jan 1 00:00:00 1970 From: ebiederm@xmission.com (Eric W. Biederman) Subject: Re: [PATCH 0/2] kvm: disable virtualization on kdump Date: Mon, 27 Oct 2008 08:02:31 -0700 Message-ID: References: <20081022232824.GD5247@verge.net.au> <20081023194129.GD27959@blackpad> <20081023222906.GB10753@verge.net.au> <4904676F.3020706@redhat.com> <490487C1.1010707@redhat.com> <490582D4.9000601@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Simon Horman , Eduardo Habkost , kexec@lists.infradead.org, kvm@vger.kernel.org, Andrew Morton , Vivek Goyal , Haren Myneni To: Avi Kivity Return-path: Received: from out01.mta.xmission.com ([166.70.13.231]:46194 "EHLO out01.mta.xmission.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751480AbYJ0PEr (ORCPT ); Mon, 27 Oct 2008 11:04:47 -0400 In-Reply-To: <490582D4.9000601@redhat.com> (Avi Kivity's message of "Mon, 27 Oct 2008 10:59:00 +0200") Sender: kvm-owner@vger.kernel.org List-ID: Avi Kivity writes: > Eric W. Biederman wrote: > > We've observed on some machines that keyboard controller reset didn't work, and > that the fallback to triple-fault asserted INIT and not RESET (and that this > INIT was blocked, hanging the machine). Switching to acpi reset worked on some > machines, but not all. Either acpi reset was not implemented on the failing > machines, or it was wired to INIT and not RESET. Right. INIT does not reset things like the MTRRs, I had forgotten that distinction. Frequently the firmware when it regains control at 0xffffffff0 asserts reset, but if we can't get there. Ouch! > Since we already have NMI IPIs, we could disable vmx there. If it is done > unconditionally and without notifiers, there is no chance of having unreviewed > surprises sneaking in. Sounds good to me. Eric