Hi there.
I've haven't used my laptop in a few months and after updating everything, my virtualbox's win10 installation won't boot and dies displaing the bsod with the error code
SYSTEM SERVICE EXCEPTION.
(https://i.imgur.com/jAGIw1r.png)
I have attached the log file, which contains
GIM: HyperV: Guest indicates a fatal condition! followed by
SYSTEM_SERVICE_EXCEPTION. Unfortunately, there's no more discernable information for me to go by.
I have done the mandatory two hours of googling, have reinstalled virtualbox and have tried the virtualbox-*-dkms packages, reboots included, to no avail. At this point, I'm out of things to try being a noob in those matters. May I kindly ask for you help on how to debug this further?
Thank you.
$ pacman -Q | grep virtualbox
virtualbox 7.0.2-2.1
virtualbox-ext-vnc 7.0.2-2.1
virtualbox-guest-dkms 6.1.22-1
virtualbox-guest-iso 7.0.4-1
virtualbox-host-dkms 7.0.2-2.1
$ uname -a
Linux Berenice 6.0.7-artix1-1 #1 SMP PREEMPT_DYNAMIC Thu, 03 Nov 2022 21:10:08 +0000 x86_64 GNU/Linux
hi there,
if its in virtualbox and it boots, then i seriously doubt its anything other than the actual vm itself (its not likely to be something external like the operating system that's running an os as a vm, otherwise the error would occur before loading the .vdi file). You wouldn't happen to have a spare machine lying around would you (windows or whatever, doesn't need to be artix)? Because if so, to verify its the actual vm, you could always copy the .vdi for the 10 vm and boot it to see in another instance of virtualbox. Its worth noting your win10 does boot, but it errors after initial boot before you reach the login screen, which in itself says its a windoze error, not a virtualbox error. So I'm kind thinking maybe you spent those 2 hours assuming it was a VB error, so would be a good idea to see it as an MS error for which there'll be loads of posts (including on MS's site). Whats funny is that after 25 years of tier 1,2 and 3 MS support, the errors don't go away, they just look friendlier, go figure.
Thanks for your kind reply. I just gave up and set up a new vm from a fresh windows .iso without any problems. The problem seems to have indeed been on the windows side itself.
And the windows help is as useless as ever :-)
that was going to be the next suggestion if and when 10 still didn't play ball, a pain in the butt but good stuff, you're back up and running! Now, with such an error in 10, they can occur for many many reasons, a messed up update or more often than not for a desktop, an unscheduled power off event, such as the plug being pulled, or a hard reset had to be done because of a total system freeze etc.
In a vm scerario, that equates to either VB crashing (very rare), or when the VM is running, rather than going through the motions and shutting down the 10 VM (start - shutdown etc), the actual vm window is closed and rather than selecting "save the machine state", "power off the machine" is chosen instead which is akin to a virtual plug pulling event. |If you have a decent amount of spare drive space, or even better, a spare external drive, its a great idea to copy the 10 vm files to it, so if it happens again, you can just copy it over and "add" back into VB without having to actually reload the darn thing! It will be a big file, on mine just 10 without much added comes in at a whopping great 38Gb.
Hi, I've a W10 in virtualbox too (some months that I don't use it, so I try to start it after reading the post and all is right.
The only difference is below:
I hope that this can help.
the difference was the 10 install had the issue, nothing to do with packages. If you read the thread from top to bottom, it is self explanatory and resolved. :)
I used virtualbox als long as it exists.
But it turns out the linux kernel KVM/QEMU Libvirt setup is now A LOT faster and and thanks to the https://virt-manager.org/ as easy to manage as VirtualBox.
I can write a little KVM/QEMU & Virtual Machine Manager with Windows 11 pro (very lightweight install) How-To
if there is interest.
Andy, that sounds like genius, and would be a great thing to do, so gets my vote.
If you want to get involved in the GNU-Linux/artix community, write about what wiki articles need to be read before coming here and writing a post that goes something like this:
"I did everything right, but it doesn't work.
It's probably the kernel or pacman or grub or the init system or all of the above.
Maybe something else entirely."