From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 17 19:29:26 2015 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 46076F25 for ; Tue, 17 Feb 2015 19:29:26 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1D8EC772 for ; Tue, 17 Feb 2015 19:29:26 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id F2BE1B941; Tue, 17 Feb 2015 14:29:24 -0500 (EST) From: John Baldwin To: freebsd-hackers@freebsd.org Subject: Re: Kernel Panic Date: Tue, 17 Feb 2015 13:36:27 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: <20150217085851.GS34251@kib.kiev.ua> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201502171336.27550.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 17 Feb 2015 14:29:25 -0500 (EST) Cc: Robert Simmons X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2015 19:29:26 -0000 On Tuesday, February 17, 2015 12:42:00 pm Robert Simmons wrote: > On Tue, Feb 17, 2015 at 3:58 AM, Konstantin Belousov > wrote: > > On Tue, Feb 17, 2015 at 01:27:46AM -0500, Robert Simmons wrote: > >> I'm experiencing a kernel panic on a VM: > >> panic: CPU0 does not support X87 or SSE: 0 > >> This is on OpenStack (using KVM). > >> > >> Is there a kernel option that I can set that will allow this VM to > >> boot without panic? > > The panic indicates that machine you trying to boot on is not compliant > > with the Intel specification. You may try the luck with setting > > hw.use_xsave=0 at the loader prompt, but I expect that you get other > > problems. > > Thanks! > > This works and allows the VM to boot. The problem appears to be a bug > in KVM virtualization, and it has been fixed upstream. I'm trying to > get my cloud provider to patch their stack. > > You mentioned that this may introduce other problems. How bad and what > kind of problems do you think may happen? If SSE did not actually work, then userland probably would not work. If it is just that this version of KVM doesn't handle the cpuid reporting for XSAVE correctly, tehn Konstantin's workaround should be fine. -- John Baldwin