Date: Thu, 27 Feb 2014 08:55:24 -0500 From: John Baldwin <jhb@freebsd.org> To: freebsd-amd64@freebsd.org, "Sean M. Collins" <sean@coreitpro.com> Subject: Re: amd64/175780: Crash on KVM boot due to xsave instruction issue Message-ID: <201402270855.24619.jhb@freebsd.org> In-Reply-To: <201402262210.s1QMA11t006147@freefall.freebsd.org> References: <201402262210.s1QMA11t006147@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, February 26, 2014 5:10:01 pm Sean M. Collins wrote: > The following reply was made to PR amd64/175780; it has been noted by GNATS. > > From: "Sean M. Collins" <sean@coreitpro.com> > To: bug-followup@FreeBSD.org;, kaloqn.ganchev@gmail.com > Cc: > Subject: Re: amd64/175780: Crash on KVM boot due to xsave instruction issue > Date: Wed, 26 Feb 2014 16:37:38 -0500 > > --P9KQiUGMzYCFwWCN > Content-Type: text/plain; charset=utf-8 > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > I also recently hit this issue when trying to launch a FreeBSD > 10-RELEASE guest in an OpenStack environment, with > Ubuntu 12.04 LTS hypervisors that use KVM. > > Did a quick google, and saw this message from the LKML: > > https://lkml.org/lkml/2014/2/22/58 I don't know that that is relevant. That change effects the size of the save area returned, but it does not fix the fact that the cpuid is returning no features supported at all for xcr0. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201402270855.24619.jhb>