From: Andi Kleen Subject: Re: [PATCH 1/5] Skip timer works.patch Date: 31 Oct 2006 00:12:51 +0100 Message-ID: <20061030231251.GB98768@muc.de> References: <200610200009.k9K09MrS027558@zach-dev.vmware.com> <20061027145650.GA37582@muc.de> <45425976.3090508@vmware.com> <200610271416.12548.ak@suse.de> <4546669F.8020706@vmware.com> <20061030225016.GA95732@muc.de> <45468620.5060805@vmware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Date: Tue, 31 Oct 2006 00:12:51 +0100 Content-Disposition: inline In-Reply-To: <45468620.5060805@vmware.com> Sender: linux-kernel-owner@vger.kernel.org To: Zachary Amsden Cc: Andi Kleen , virtualization@lists.osdl.org, Andrew Morton , Chris Wright , Linux Kernel Mailing List List-Id: virtualization@lists.linuxfoundation.org > That is the one that can panic, for now. Fixing the paravirtualized > case is easy, but we can't assume paravirtualization just yet. Hmm, this means standard vmware boot is not reliable unless that magic option is set? That doesn't sound good. -Andi