The cause of this was that the guest was running under an older version
of VMware that didn't correctly support the new features of the
hypervisor CPU, and was passing the CPU features through to the guest.
So, when the guest tried to setup xsave/xrstor, it failed to even
initialize, even though the (emulated) cpu features reported it was
supported. The kernel didn't expect this initialization failure
(because if the cpu reports supporting the features, it must be able to
at least initialize the features), and so caused an error in the kernel,
which resulted in repeated errors every time xsave/xrstor was used
later, causing an unstable OS. Technically, the kernel could be updated
to check for xsave/xrstor initialization failure, and if detected then
just disable the use of xsave/xrstor completely (a test kernel was made
for the reporter and it did fix/workaround their problem). However,
since the real cause of this issue is a broken hypervisor (older
VMware), simple upgrading VMware fixed the problem for the reporter, and
adding error checking to the kernel seems unnecessary.
Closing this as invalid.
** Changed in: linux (Ubuntu Artful)
Status: In Progress => Invalid
** Changed in: linux (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746562
Title:
segfaults/unusable system with 4.13 kernel under VMware
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746562/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
