Closed philmmanjaro closed 7 years ago
Issue seems to be known and should be fixed with v5.1.23. Might be a new issue with updated toolchain.
We will see. In any case the guy had the same error message. although it seems he was using regular linux412, so not sure if the issue might be created by one of our patches...
The change was introduced on the regular source: https://github.com/torvalds/linux/commit/a9ebf306f52c756c4f9e50ee9a60cd6389d71344 I checked the Intel-Patch-Set and couldn't find anything there causing that issue.
Solved with virtualbox 5.1.24 👍
We get following error:
This got introduced with https://github.com/torvalds/linux/commit/a9ebf306f52c756c4f9e50ee9a60cd6389d71344.