Updating older versions of sun virtualbox
- such is the Way that Windows Works unreliable, at Best.Just a suggestion but you should post where you got the VBox package and what version you are using.Since it is now working I can't now test this solution for reproducibility. Just a suggestion but you should post where you got the VBox package and what version you are using. But after booting once then changing Paravirtualisation back to "default" prevented booting.It makes a difference: The version of VBox in the Min18 repository is: 5.0.36 The current version of VBox from Oracle is: 5.1.20Just a note, I have managed to get this working using the following config:- VBox 5.0.40 Ubuntu r115130 stage 1, create VRMachine default settings for win 10. Changing Paravirtualisation to "legacy" was successful (although booting was slow).
It is, therefore, affected by multiple vulnerabilities as noted in the January 2018 Critical Patch Update advisory.
Currently I have it set to "Default" again and Win10 boots in Virtualbox 5 OK. Host PC is as follows: Kernel: 4.8.0-53-generic x86_64 (64 bit) Desktop: Xfce 4.12.3 Distro: Linux Mint 18.2 Sonya After changing Para Virtualisation as per PCAdvisor UK, it is now all good.
In the short time since I've had to repeat this procedure once, so it may not be 100% stable. Thanks Guys fnerkyboy This happened again after the recent "Feature Update to Windows 10, version 1703" i.e. Turning Paravirtualisation to "none" allowed booting, as described in my posting above.
Try copying the (Windows 10)setting file from Windows (host) to Mint (host), this ensures you're using the same Virtual Box settings that work on the Windows host.
Maybe the problem is that there are bugs in Windows 10 1703? After Win10-1703 failed to let itself be installed in Virtualbox 5.0.40_Ubuntu-r115130 (from the official repository) I tried Win10-1607, which installed without problem.
Please consult the CVRF details for the applicable CVEs for additional information.