Hi,
You may want to do something similar to this for vbox upstream:
https://github.com/jwrdegoede/vboxguest/commit/8a79961c661e3fba88c0e50447b2344e0c811d1a
Note in my tree this applies on top of:
https://github.com/jwrdegoede/vboxguest/commit/8c232c972f7b2dfbfc863a1aaeb0b44fdfcf82d0
Which I
Returning VERR_* style vbox-runtime codes as positive values is an ugly
hack and unlike any other ioctl call on Linux, breaking standard
expectations of ioctls.
All Guest Additions user-space code calls the ioctl through the
vbglR3DoIOCtl wrapper, which calls on RTErrConvertFromErrno on negative
Some VERR_ codes require special error handling in userspace, make
sure that these survive being converted to an errno and back again.
Specifically this commit adds support for the following VERR_ codes:
VERR_NOT_FOUND
VERR_HGCM_SERVICE_NOT_FOUND
VERR_BUFFER_OVERFLOW
VERR_OUT_OF_RANGE
To
Hi Hans,
It's a really good question why that message is printed at all. As Frank
pointed out, the apic_check_deadline_errata() function only goes by the CPU
model and does not check whether the feature is available.
It is generally bad form to assume specific CPU features based solely