Hi everybody,
I'm facing an annoying problem. I installed Windows 8.1 in VB 4.3 last year and I'm now on the current stable version of VB on MacOS Yosemite and everything works just fine until a few weeks back, it started to get stuck and the disk-activity-led in the VB windows is just red and windows does not respond anymore. The VirtualBox host process the vm is running in is not responding according to 'Force Quit Applications'. I had to kill the window by hard.
The log output is attached. You can see that the AHCI controller got reset somehow.
Best,
Andreas
Windows 8.1 getting stuck
-
LnxBil
- Posts: 3
- Joined: 14. Mar 2011, 17:31
- Primary OS: Debian other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Windows 8.1 getting stuck
- Attachments
-
VBox-Crash-Log.txt- VBox.log
- (84.66 KiB) Downloaded 4 times
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Windows 8.1 getting stuck
Thanks for posting the relevant log (a rare pleasure to see), but it would be even better if you compressed it too.
Looking at it, the first thing that springs out is that it doesn't say Windows 8.1, it says Windows 8. I don't see how a Win8.1 VM ever worked with a Win8 profile - MS made a significant change, despite the minor version increment.
You have also assigned all (both) of your host cores to the VM, which is not a good idea either, since the host will find it hard to run without one. Note that threads are not cores - I'm aware that your CPU has 4 threads. Many of the messages near the end of the log have to with multiprocessing support (or so I believe).
Looking at it, the first thing that springs out is that it doesn't say Windows 8.1, it says Windows 8. I don't see how a Win8.1 VM ever worked with a Win8 profile - MS made a significant change, despite the minor version increment.
You have also assigned all (both) of your host cores to the VM, which is not a good idea either, since the host will find it hard to run without one. Note that threads are not cores - I'm aware that your CPU has 4 threads. Many of the messages near the end of the log have to with multiprocessing support (or so I believe).