What makes Windows 10, 11, 2025 Server VMs all fail in VirtualBox with numerous weird bug checks (IRQL_NOT_LESS_OR_EQUAL, KERNEL_SECURITY_CHECK_FAILURE, PROCESS1_INITIALIZATION_FAILED)?
For posterity, the directly involved package versions were: virtualbox (7.2.4-1), linux617-virtualbox-host-modules (7.2.4-12), linux617 (6.17.13-1).
Prelude
NB: Skip this section if you don’t care about how I ended up with VirtualBox in the first place! TL;DR at the bottom.
After migrating away from Ubuntu quite some time ago, I took the plunge and tried Manjaro Linux. I’m happy with it still. It feels more stable than what I have seen of Arch, yet more up-to-date than Debian and derivatives. I still run a few machines with Debian, Ubuntu/Kubuntu and Mint, but may main workstation has been on Manjaro for a while now.
Originally I used VMware Workstation for virtualization needs. I had paid and upgraded across several major versions. As readers of this blog will know, I mourned the discontinuation of the Replay Debugging feature. My first VMware version was 2.x for Linux, btw.
Anyway, with Ubuntu this sort of worked. The VMware kernel modules sort of built fine and integrated fine with Ubuntu. However, if you dared upgrading the point releases 1 and updated the kernel to one of the HWE kernels, things would start falling apart.
Obviously Manjaro’s kernel version — at the time I switched — was way ahead of Ubuntu’s. Consequently VMware Workstation was no longer an option. Even Broadcom changing the licensing making VMware Workstation more or less free to use for private and commercial settings makes no difference in this scenario. Because VMware was at the time really bad regarding its kernel modules getting updated 2.
So I ended up migrating to Qemu/KVM first. However, this was merely an interlude, because the user experience was IMO quite shoddy. No matter the UI frontend, none played nicely with a multi-monitor setup. And Remmina as a frontend was also a disappointment … perhaps in this case Wayland was in part to blame.
Either way, I am a private user, so VirtualBox — on account of its licensing — was an option. This is where I ended up. I have to say the user experience is almost on par with that of VMware Workstation for most workflows.
Since I came from Qemu/KVM, the road to VirtualBox had a few bumps. Hardware-assisted hypervisors are like The Highlander: there can be only one. And throughout the kernel versions that I experienced with Manjaro, the behavior of the KVM kernel modules also changed (ticket). However, I never really experienced much friction on account of KVM and VirtualBox kernel modules clashing.
New year starts: … so does the weirdness
Alright, so after new years, I decided to clean up the system a little. I got rid of a few orphaned packages. Initially inspecting what would be the list of orphans with pacman -Qtd then accepting its output with: sudo pacman -Rns $(pacman -Qtdq).
Good riddance, orphaned packages.
Continue reading
