virtualbox.org

Hi Team,

As a maintainer at The Odin Project (new account, no links apparently?) we recommend our users install VirtualBox along with a Ubuntu 20.04 or Xubuntu 20.04 as part of the setup for our course. Recently, many of our users have run into an issue with a large amount of notification spam in the guest OS similar to the following:

• Code: Select all

  VBoxClient: Failure waiting...

  Code: Select all

  VBoxClient: VbglR3InitUser...

So far the only fix we have is to get them to roll back to VirtualBox 6.1.30, however that seems like a workaround more than anything. Is this a known issue with newer than 6.1.30 versions? Is there anything we can recommend *instead* of just rolling back?

Okay, turns out they are running Windows 10 Home, so it's not Hyper-V. I guess it must be that Virtualisation is not turned on.

Logs seem to suggest as much as well:

Hyper-v is enabled.

00:00:01.824400 HM: HMR3Init: Attempting fall back to NEM: AMD-V is not available
00:00:01.849306 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

Windows 10 Home does have Hyper-v, at least it has the underlying mechanism which can still be turned on by various features. The only thing you don't have is the superficial ability to create actual VMs.

See HMR3Init: Attempting fall back to NEM (Hyper-V is active).

Yea, after checking with the user they confirmed that Virtualisation was turned on, so we'll check out how that how-to you linked worked.

Thanks!

mdfr4nk wrote:Yea, after checking with the user they confirmed that Virtualisation was turned on

I'm not entirely sure what that means. If this refers to the virtualization feature in the host BIOS then it needs to remain turned on, because both VirtualBox and Hyper-v want to use that - indeed that is the source of the conflict between the two.