On Thu, Jan 4, 2018 at 5:36 PM, Tom Hromatka <tom.hromatka@xxxxxxxxxx> wrote:
I am seeing a hang running kernel 4.15-rc6+ on a vanilla VirtualBox VM.Any chance of bisecting this?
(VirtualBox version 5.0.40)
I could imagine that all the stuff we now do for page table isolation
might confuse the VM.
When I boot this kernel, it hangs and falls back into dracut. Here'sSo a few questions:
the boot log immediately prior to the hang:
(a) does it work with "pti=no" on the kernel command line
(b) what was the last kernel that worked? Is 4.15-rc5 fine, for example?
[ 0.000000] ------------[ cut here ]------------I think this is a vbox issue, with virtualbox not exposing all the
[ 0.000000] XSAVE consistency problem, dumping leaves
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.
I suspect you _should_ have gotten that before too, independently of the hang.
Linus