Date: Mon, 8 Jan 2018 19:54:55 +0100
From: Ingo Molnar <mingo@kernel.org>
To: Christian Kujau <lists@nerdbynature.de>,
        Frank Mehnert <frank.mehnert@oracle.com>
Cc: Tom Hromatka <tom.hromatka@oracle.com>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Dhaval Giani <dhaval.giani@oracle.com>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Peter Zijlstra <peterz@infradead.org>,
        Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 4.15-rc6+ hang
Message-ID: <20180108185455.bgfrg62m44hm4mhf@gmail.com>
References: <c16b2d84-fce8-42cd-bc11-4ddb9d8957b4@oracle.com>
 <CA+55aFzFfLd-bXFb10Xk-pvzB3_ayN0qjOS_6u2Rwv=qgFJQmg@mail.gmail.com>
 <1e1b4534-b0b4-90c9-479b-29058047f1e9@oracle.com>
 <alpine.DEB.2.21.9.1801070249070.2636@trent.utfs.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <alpine.DEB.2.21.9.1801070249070.2636@trent.utfs.org>
User-Agent: NeoMutt/20170609 (1.8.3)
Sender: linux-kernel-owner@vger.kernel.org


* Christian Kujau <lists@nerdbynature.de> wrote:

> On Thu, 4 Jan 2018, Tom Hromatka wrote:
> > > > [    0.000000] ------------[ cut here ]------------
> > > > [    0.000000] XSAVE consistency problem, dumping leaves
> > > I think this is a vbox issue, with virtualbox not exposing all the
> > > xsave state, so that when the kernel adds up the xsave areas, the end
> > > result doesn't match what the total size is reported to be.
> > 
> > It seems probable that this is a VirtualBox issue.? I was
> > able to boot my exact 4.15-rc6+ kernel in qemu-kvm v1.5.3
> > just fine.
> 
> This was discussed on vbox-dev back in May 2017 (see the whole thread for 
> more details):
> 
>  https://www.virtualbox.org/pipermail/vbox-dev/2017-May/014466.html
> 
> Does that help?

So, unless I've managed to confuse myself navigating that horrible email archive 
web interface, the conclusion of that discussion appears to be a workaround: by 
adding 'nofxsave' to the guest kernel boot line the warning+boot-hang goes away?

It would be nice to root cause this bug and offer a more permanent solution. We 
can even apply VirtualBox quirks to the upstream kernel, within reason - i.e. as 
long as it does not get overly ugly and does not impact other uses.

Thanks,

	Ingo