Hi, I am on the current version of Tumbleweed packages and just tried to start/boot one of my Windows10 VMs I have in use for one specific application I need once a month. During boot i noticed that the machine just hangs at some point (screen freeze with last image shown). I accidentally also started an old Windows7 VM (which also worked without problems before), and again this also hangs (on the login screen).
Is there maybe a know bug with virtual box at the moment?
Are you using OpenSUSE VirtualBox or Oracles VirtualBox and what version.
Oracles is having some issues - All of OpenSUSE Virtualbox 7.0.18 have unique patches for the 6.9.4 and 6.9.5 Kernels. Previous version will not work properly. Also if you installed the guest extensions - did you install the ones for 7.0.18 - the older ones will crash the VM.
I know that saved images are not restoring from previous versions as pointers to restore points moved between new OS kernels.
I use virtualbox 7.0.18-1.1 from the openSUSE-Tumbleweed-Oss repository. And the VM worked fine for years
Try the “if all else fails” fix as root or sudo:
zypper rm virtualbox
reboot
zypper in virtualbox
and see if that fixes it.
Same here, but not 100% of the time on several TWs with win10 VB VMs.
I normally kill the window, try starting again and then usually it works.
PS: I use exclusively use “ACPI shutdown” to bring the VMs to sleep.
I turned off fastboot in windows 10 and 11 - if it is on - it is a saved image reload and depends on the VirtualBox hooks to be in the same place.
If you want the secure way to shut windows down, the fastboot off is required. There is no way to determine that between reboots that everything is where windows thinks it is -
I always use File Close save to do what fastboot did and shutdown in windows to do clean boot.
Seems to be the case for me also. At least on a second try my Windows 10 VM started and stayed stable.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.