I upgraded VirtualBox from 4.3.26 to 5.0.0 yesterday; I use VirtualBox to run Win7.

I use the .run from Oracle to upgrade and the Oracle download page contains a notice:
The key words in there are "and with Windows 10 guests."

5.5.0.0 works just fine with my existing Win7 and Slackware 32-bit guests on a 64-bit host.

I have virtually no interest in Win8 or Win10, virtual guest or not, and I'll wait a year or two for Win10 to get stable (and remove all the adware they've stuck in the "free" version anyway). When Service Pack 1 (or 2, or 3, or 29) rolls around maybe then but not before.

Hope this helps some.

1 members found this post helpful.

I've got VirtualBox 5.0.0 on a Slackware64-current host, and it seems to run Win10 just fine... but I'm not really doing anything with it. I installed it just for a Captain Cook.

FWIW, my findings are that there doesn't appear to be any compelling reason to use it. The Cortana spyware issue OTOH...

1 members found this post helpful.

vmware player on my windows machine is how I have been working for a few years now. Slackware is happy inside a VM and I ssh yo it. With recent windows versions I see no reason why I should dual boot. Same will go for win10 when I upgrade.

I have 10 working in VirtualBox with the Vista/7/8/8.1 settings. The system requirements are roughly the same between everything since Vista.