virtualbox.org

Hi,

I am fairly new to VirtualBox so please don't be too harsh.

I am running Ubuntu 18.04 guest on Windows 10 host. Everything was running smoothly for weeks until I tried to access my NVIDIA GPU from within the VM. I changed the preferred GPU in Windows from integrated to NVIDIA for the VirtualBox app and I turned on 3D acceleration in VB. I then re-installed GuestBoxAdditions in Ubuntu. Everything worked fined until I rebooted. Now Ubuntu loads up (even though the booting looks different than previously, simply with more text) and eventually displays my desktop but it's frozen - I cannot do anything but power off the machine. In the meantime I turned off 3D acceleration again and changed preferred GPU to integrated.

I would much appreciate any help with fixing this! Log attached.

First problem to clear up is this one:

Your log contains these lines:

{timestamp} HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
{timestamp} NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

You might notice in the guest window's Status Bar the green turtle: The choice of animal is appropriate: Your guest is running, just really slow. Or it might guru-meditate. This is because a service that uses Microsoft Hyper-V is running on your host PC. Normally Hyper-V blocks Virtualbox. But your PC is of the type and OS where Virtualbox can attempt to run the guest using the Hyper-V engine. This arrangement is still being developed and isn't 100% yet.

If VirtualBox is running without Hyper-V enabled, and nothing else is interfering with hardware virtualization (VT-x / AMD-V), then the usual virtualization icon () will be seen in the Status Bar.

To turn Hyper-V off completely, do this:

1. Shut down all programs. You will have to reboot your host.

2. See I have a 64bit host, but can't install 64bit guests. This tutorial has a couple more things to look for in step 2. Be sure these are all turned off.

3. Find the Command Prompt icon, right click it and choose Run As Administrator.

4. Enter this command:

bcdedit /set hypervisorlaunchtype off

5. Enter this command:

shutdown -s -t 2

6. When the computer turns off, unplug it for 20 seconds. Then plug it in again and boot up Windows 10.

If your Virtualbox does not start successfully, zip and post another vbox.log. For further info, see https://www.tenforums.com/tutorials/139 ... puter.html

Hi,

thanks a lot for your help. I followed the instructions and the lines you quoted no longer appear in the log file (I think) though the problem persists. I also cannot see the turtle you mentioned anywhere. I am attaching the new log file.

Now tried to start the machine again, without changing anything at all, and this time it didn't even get to the Ubuntu landing page. Instead it's printing alternating lines "Created slice User Slice of gdm." "Starting User Manager for UID 121..." and finally "Started Session c48 of user gdm."

Guest RAM settings:

00:00:02.879424 RamSize <integer> = 0x000000013d800000 (5 326 766 080, 5 080 MB, 4.9 GB)
00:00:02.879636 VRamSize <integer> = 0x0000000008000000 (134 217 728, 128 MB)

Host RAM available:

Log 1:
00:00:02.738919 Host RAM: 8048MB (7.8GB) total, 3544MB (3.4GB) available
Log 2:
00:00:07.384604 Host RAM: 8048MB (7.8GB) total, 3125MB (3.0GB) available

Not enough host RAM for the guest RAM settings. Set Guest regular RAM to 2GB to fit in your host's capabilities and try again.

Also, though it is probably not causing trouble now, it might one day:

00:00:02.879422 NumCPUs {in the guest} = 0x0000000000000004 (4)
00:00:03.674170 CPUM: Physical host cores: 4

All your physical CPU cores are available for the guest to use. If the guest ever goes 100% on all 4 cores, host stability may suffer. And more cores makes a guest run slower due to extra scheduling commands on the host OS. Set guest cores to 2 unless you specifically installed parallel-processing-enhanced software in the guest, at which use 3 at most so the host has something to run on.

This is really odd. Everything worked just fine for weeks with these exact same CPU and RAM settings. (In addition, my PC has 8CPUs so I figured 4 shouldn't crash it) I made the changes you suggested but the outcome is the same. I'll also add that visually everything works just fine - I first see the Desktop, when I clicked on Insert the guest box additions .iso, a window immediately pops up to ask me if I want to run. It doesn't seem slow at all. It even goes to sleep after some time and shows the screen with a clock which updates at the strike of every minute precisely. No mouse clicks or keyboard hits do anything though.

Please download the Guest Additions ISO for 6.1.10 and try them:
https://download.virtualbox.org/virtual ... 6.1.10.iso
One poster reports that the 6.1.12 GAs broke a couple of their Linux guests.

Napifolious wrote:my PC has 8CPUs

00:00:07.855260 Full Name: "Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz"

https://ark.intel.com/content/www/us/en ... 0-ghz.html
It has four hyperthreaded cores. Your host OS cheats when it reports 8 processors. The hyperthreads don't help in running Virtualbox.

Hi, thanks for the effort. None of the above worked for me so I opted for a clean install and set up my OS and all programmes from scratch.