virtualbox.org

Hi Fellow Virtual box users,
I've recently updated my Linux installation from Linuxmint18.3 to Linuxmint20. I re-installed Virtualbox 6.1 and added an existing VM of Windows10 which had worked perfectly on Linuxmint18.3. On starting the guest (which seems to take longer) I now find that after about a minute the guest goes into a reboot after a very abrupt shut down. It's now impossible for the guest to stay running longer than a few moments. I attach my Virtualbox log file.

Thinking I may have made an error I repeated the LinuxMint20 clean install on another machine and imported the Windows10 guest into that system but the problem is identical. It takes a while to load and then "falls over" after about a minute.

Any help would be gratefully appreciated.

Edit: It would seem that quite a few people are experiencing this problem. Looking at the LinuxMint forum one guy is saying that VirtualBox worked OK with Linux kernel 5.4 but latest kernel 5.8 is causing the problem. That would fit in with my experience of the VM working OK with Mint 18.3 but not Mint20. Is the problem with the Linux Kernel?

The guest OS reports a BSOD:

00:01:53.661113 GIM: HyperV: Guest indicates a fatal condition! P0=0xef P1=0xffffe684269a9340 P2=0x0 P3=0x0 P4=0x0
00:01:53.661163 GIMHv: BugCheck ef {ffffe684269a9340, 0, 0, 0}

but the Virtualbox environment keeps going.

One thing I notice is that the guest runs for a minute and reports Guest Additions 6.0.4:

00:00:11.816967 VMMDev: Guest Additions information report: Version 6.0.4 r128413 '6.0.4'

Then the guest resets, probably through a reboot, and then reports GAs 6.1.16, matching the host Virtualbox:

00:01:02.772674 VMMDev: Guest Additions information report: Version 6.1.16 r140961 '6.1.16'

Did you update the Guest Additions during this run? And was the guest crashing beforehand or did it start crashing afterwards?

Hi,
Thanks for taking a look at the log file. Yes I did update the Guest Additions but it didn't make any difference, the guest still kept failing.

What I have discovered since then is that following a report on Linuxmint forum site by "Wayne" 20th October, if I turn off the WiFi Broadcom adapter on the host the guest will start and is reasonably stable in as much as I can use "Rufus" to create a bootable USB. If I try this with the host WiFi turned on, the virtualbox environment can't boot and simply collapses and tries to reboot.
I believe there is a possible conflict between the latest Linux Kernel, Virtualbox and the wifi chip.
(As an aside, I have a near identical second computer setup using the same guest cloned vdi but with an Intel WiFi chip. This is slightly more stable and will run for a few minute with the wifi turned on before crashing).

To summarise:
Turning off the host wifi allows the guest Windows 10 to run.
Turning on a Broadcom Wifi adapter definitely causes a crash.
Turning on an Intel Wifi adapter the system is slightly more tolerant but still crashes.

Thank you for your time and any conclusions.