3 ms·
If you've recently upgraded to VirtualBox 5.0.18 you might try downgrading to 5.0.16 as I had a similar issue earlier this week.
by alyandon 11y ago
If you've recently upgraded to VirtualBox 5.0.18 you might try downgrading to 5.0.16 as I had a similar issue earlier this week.
- therealmarv 11y agoI've updated to the VirtualBox 5.0.19 test build which also fixes that. Bad timing for Ubuntu: https://www.virtualbox.org/wiki/Testbuilds https://www.virtualbox.org/wiki/Testbuilds