virtualbox.org

My company has an Ubuntu VM image that we have imported successfully on dozens of Windows systems. We are currently using VBox 6.1.10

On one client's system (Win 10 Pro), the VM freezes partway through the boot:
I've attached the logfiles - I'm not very familiar with VBox logs and haven't been able to find anything that seems relevant.
I have confirmed that Virtualization is enabled in the computer's BIOS. No Hyper-V or Hypervisor features are enabled. I ran a chkdsk which returned no issues. Her computer has 16GB of RAM and is using a AMD Ryzen 5 3400G processor, which seems to work fine with VBox based on my research.

I tried installing an older version of VBox (5.2.32) and got the same behaviour. She was running Sophos Anti-virus, but we tried disabling that and no luck. I believe the computer was rebooted after disabling the anti-virus. There are a few other programs running on her machine - I should have taken a screenshot but it slipped my mind. I'll try to get my hands on a list of programs.

Has anyone seen these symptoms before? I'm having a hard time narrowing this down so any suggestions would be greatly appreciated!

There is nothing in the vbox.log indicating why the guest OS stops there.

There are hardening catches of the Teamviewer dll:

00:00:13.591924 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_SUP_VP_NOT_OWNED_BY_TRUSTED_INSTALLER fImage=1 fProtect=0x0 fAccess=0x0 cHits=1024 \Device\HarddiskVolume4\Users\KCarter\AppData\Local\Temp\TeamViewer\tv_x64.dll

Hardening catches in the vbox.log are usually indications of when the guest could reject the DLL and keep going, but that doesn't always work.

I have Teamviewer on my Virtualbox host and do not get hardening catches on Teamviewer. Sounds like you might need a new version?

Ubuntu might need or like more regular and video memory:

00:00:13.577081 Host RAM: 14284MB (13.9GB) total, 8534MB (8.3GB) available
00:00:13.696826 RamSize <integer> = 0x0000000040000000 (1 073 741 824, 1 024 MB)
00:00:13.697028 VRamSize <integer> = 0x0000000002100000 (34 603 008, 33 MB)

You might also give the guest two processors, modern OS's like that:

Host CPU status:
00:00:14.142503 CPUM: Logical host processors: 8 present, 8 max, 8 online, online mask: 00000000000000ff
00:00:14.142504 CPUM: Physical host cores: 4
Guest CPU settings:
00:00:13.696824 NumCPUs <integer> = 0x0000000000000001 (1)

Finally, when the Virtualbox guest window stays open and the guest OS displays errors that the OS might display on a real PC, the OS needs to be troubleshot directly as if it was on a real PC, using the OS's help channels.

Thanks for your response! I was able to resolve the issue by going from 1GB RAM/1CPU to 2GB RAM/2CPU

I'm not sure why that was necessary - our default install has 1GB/1CPU and we've never had this issue in the past. I'm guessing it has something to do with her specific processor but I'm out of my league here.

Thanks for pointing me in the right direction!