This appears to be fixed, somehow, despite the fact that virtualbox hasn't been updated since I reported the issue.
There was a kernel update on 2019-03-31 (from 5.0.0.7.8 to 5.0.0.8.9), maybe related?
Closing for now, will re-open if the issue surfaces again.
This appears to be fixed, somehow, despite the fact that virtualbox hasn't been updated since I reported the issue.
There was a kernel update on 2019-03-31 (from 5.0.0.7.8 to 5.0.0.8.9), maybe related?
Closing for now, will re-open if the issue surfaces again.