Reporting that KB5013943 Update for Windows 11 broke my VirtualBox

[Pagafantas]

My Ubuntu VMs (Windows 11 host) returned error ''End kernel panic - not syncing: attempted to kill the idle task'' ... Removing the Windows update fixed the issue for me. This does not seem to be a common problem. Perhaps I have some odd settings or configs. For what it is worth.

[scottgus1]

Interesting! Thanks for the info, Pagafantas! If you'd like, a VM log while the update is not installed and the VM works, and another log after the update is installed and the VM has trouble, might help the forum gurus or the devs figure out if anything in Virtualbox needs to be fixed.

If you want to provide the logs, please follow this procedure:

Start the VM from full normal shutdown, not save-state. Run until you see the condition you want logged, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.

Right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.

[Pagafantas]

Ok, reapplying the update recreated the problem. File attached.

[Thyfos]

Same Problem here,

after Update Windows to KB5013943, my virtual Machine crach with Kernelproblems (Kernalpanic).

Windows 11 (KB5013943)
Virtual Box: 6.1.34
Virtual Software BS. Oracle Linux 7.9

Absolutly a nogo Oracle!!! Please fix the Problem fast.

[scottgus1]

Thyfos, have you asked Microsoft to fix it too? Their update up-ended working systems, after all...

Pagafantas, thanks very much for the log, and taking time to re-apply the update to get it!
If you could also provide a log with the update not applied and the VM working, that could really help the devs.

One thing I do see in this log is that Hyper-V is enabled on the host:

00:00:07.682898 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available

If the no-update log also contains this line, then Hyper-V might not be the problem. Or the update may be changing things in a way that Virtualbox has to account for.

[Thyfos]

@scottgus1

you are of course right. Yesterday i was totally frustrated. Sorry

[scottgus1]

No problem, Thyfos! Been there done that myself

If you'd like to provide update-blocks-VM and no-update-working-VM logs, too, I'm sure the devs could use them.

[Thyfos]

in the appendix my log

[Pagafantas]

Thanks for all your help, but you might want to tell your devs to stand down on this specific issue. You write:

One thing I do see in this log is that Hyper-V is enabled on the host

which reminded me that I might have had the ''Virtual Machine Platform'' setting ticked. Indeed, I did. Unchecking it lets my VirtualBox run normally again with the MS update.

On Windows 11 Home I was playing with Docker and Linux terminal WSL2 so these needed '''VPM'' enabled. I soon learned that switching between the two virtual systems was burdensome and focused mainly on VBox. But at some point, I toggled on the ''VMP'' setting to go into the terminal, forgot about it, and somehow with one or another of the VBox updates, both systems ran. So the recent Windows Update exposed this situation, and I suppose that now the mystery becomes why did VBox ever work with the ''Virtual Machine Platform'' setting enabled? Above my pay grade.

All in all this learning experience was a somewhat triggering event: ''Panic : attempting to kill the idle'' fired up visions of two ex-wives packing heat. But I practiced my breathing and all is well.

[Thyfos]

Any news for us?

[scottgus1]

Not yet, this will take time.

[pehobt]

Hi all,

I have the similar trouble, almost all my virtual machines (Ubuntu 20.04, Debian 11, Debian 10) are not able to start with VirtualBox VM 6.1.34 r150636 win.amd64 (Mar 23 2022 00:36:21) on my PC with Win11.

After some searching (googling) I have found that when Win11 has disabled the following settings related to hypervisor, the virtual machines are again able to work

Clipboarder.2022.05.20.png (68.07 KiB) Viewed 5288 times

Sorry, the picture is from Czech Win11, the section is Control Panel - Programs - Turn Windows features On or Off

Hope it will help to anybody

For sure this is not final solution and I hope Microsoft or Oracle will found the real solution soon

Best Regards.

[Thyfos]

Hi all,

I have the similar trouble, almost all my virtual machines (Ubuntu 20.04, Debian 11, Debian 10) are not able to start with VirtualBox VM 6.1.34 r150636 win.amd64 (Mar 23 2022 00:36:21) on my PC with Win11.

After some searching (googling) I have found that when Win11 has disabled the following settings related to hypervisor, the virtual machines are again able to work

The attachment Clipboarder.2022.05.20.png is no longer available

Sorry, the picture is from Czech Win11, the section is Control Panel - Programs - Turn Windows features On or Off

Hope it will help to anybody

For sure this is not final solution and I hope Microsoft or Oracle will found the real solution soon

Best Regards.

thank you for the information. On my system (Windows 11 home) hypervisor is disabled by default, but i have the crashes. In The Attechment my Screenshot (in German)

How to get the WIndow? Open DOS window as administrator and enter Appwiz.cpl

c:\> Appwiz.cpl

[pehobt]

Try to disable also your "Plattform fur virtuelle Computer" (at the top of your picture). I have also this disabled on my PC.

Just to try

[Thyfos]

Try to disable also your "Plattform fur virtuelle Computer" (at the top of your picture). I have also this disabled on my PC.

Just to try

Thanks for the note , I had forgotten about it.

After deselecting and restarting the host (Windows PC) there is no change. But it was a good idea