Virtual Box : This Version works fine and is the revision downgraded to.
virtualbox - VirtualBox is an Emulator - 5.0.18-16.1
virtualbox-host-kmp-default - Host kernel module for VirtualBox - 5.0.18_k4.1.21_14-16.1
Distribution - openSUSE Leap 42.1
Virtual Box : This version introduces the problem identified in this post.
virtualbox - VirtualBox is an Emulator - 5.0.22-19.1
virtualbox-host-kmp-default - Host kernel module for VirtualBox - 5.0.22_k4.1.26_21-19.1
Distribution - openSUSE Leap 42.1
Hosts: Windows 10
The extension packs were matched on each install. As I’m pulling my install from the OpenSUSE repository, I’ve not yet tried version 5.0.24, so I don’t know if this has fixed the problem. However, as I’m under the gun and need my virtuals working a downgrade to the previous version has solved the problem.
I have moved this 13.2 system from VirtualBox v5.0.18 to v5.0.20.
And, the Oracle_VM_VirtualBox_Extension_Pack and VBoxGuestAdditions also.
[HR][/HR]The 13.2 Virtualisierung BuildService repository (v5.0.18) had left a load of Host and Guest Kernel Module versions on this system which I cleaned up during the upgrade to v5.0.20.
Please check for any superfluous Kernel Module versions and, also the “Extension Pack” and “Guest Additions” versions that you’re using.
[HR][/HR]The Windows 10 in the VM has now been running for more than 60 minutes – Kaspersky has been updated and has just finished a Rootkit search, Firefox has been updated, Windows 10 has searched for updates and not found any, Sigma Photo Pro v6.3.3 runs without issues – no Windows10-in-VirtualBox-v5.0.20-on-openSUSE-13.2 freezes yet.
And now I’m not so sure: on shutting the Windows 10 down (I rebooted after installing the newer “Guest Additions”) the message “Your Windows is being prepared. Do not turn off your computer.” has appeared. I’m away for a while – will leave it in that state for the next hour or so . . .
That’s likely one of my biggest Windows 10 annoyances…
Win10 downloads its updates in the background but almost never notifies the User when the system is ready to install and then requires a reboot. Instead, as the Update sits waiting to be installed, it behaves like a memory leak, the system will gradually slow down and various random things become slow or stop working altogether. <Sometimes> if you happen to click “Power…” you might see that the menu changes have changed to indicate that an Update will be installed on power down or reboot, but no always…
If your system actually freezes, then you may have to do a hard power reset, and then you may see something on boot, but of course since a Windows Update starts to install on shutdown, you’ll still need a proper shutdown and reboot to install an Update fully.
This is probably most often seen if you’re in the habit not to do a full system power down and reboot… only hibernating or going on standby daily.
I’ve seen this “memory leak” problem related to Windows Update since Vista, and it seems MS has no intention to fix it…
So, if you’re running any kind of Windows version since about 2005 when Vista is released as a Host or Guest, it’s something you need to be aware of and deal with it…
Came back after about 2 hours and, the Windows 10 Guest had shut down. Quit the VirtualBox; started the VirtualBox Host again; rebooted the Windows 10 Guest VM; waited about 10 minutes for Windows 10 to quieten down after rebooting; then “powered the Guest VM off” again; this time without having to do a “Redmond wait”.
[HR][/HR]Can’t really say if VirtualBox v5.0.20 with a Windows 10 Guest VM is really stable or not – I’m keeping the v5.0.18 Oracle_VM_VirtualBox_Extension_Pack and VBoxGuestAdditions for the moment for the case that I need to roll back.
[HR][/HR]Please be aware that I have only one Windows 10 Home Edition Guest VM.
The Thread Originator probably has multiple Windows 10 Professional/Enterprise Guest VMs running.