VM fails to start after upgrade to Windows 10 1803

[tipper258]

Hi folks,

Virtualbox has just worked for me for years so never had to delve into the details before, however since taking the recommended upgrade to Win 10 1803 last night, Win 10 has failed to start. Visual symptom is the blue windows offset square thing appears, the white dots running round in circles are there, then the screen goes blank, wait a bit and it resets to the virtualbox logo and restarts.

I tried all the hits on this I found here, changing various parameters, however the symptoms haven't changed. Looking through the VBox.log, not sure if any of this is relevant but there is something about display resolutions not being accepted by frontend, followed by some USB suspended, hyperv reset then the VM moves from RUNNING to RESETTING.

Any chance someone who knows what they're doing more than me can take a look at the attached VBox.log file please? I see it contains all the config info but for ease it's macOS 10.14.02, VirtualBox 5.2.26 r128414 (Qt5.6.3), VM config is 2 vCPUs, 4096mb ram, APIC enabled, paravirt default, nested paging enabled, 256mb video ram, 1 monitor, no scaling or video acceleration. VirtualBox reports the vmconfig as VT-x/AMD-V, Nested Paging, PAE/NX, HyperV Paravirtualisation.

Many thanks
Alan

[socratis]

00:00:02.254911 File system of '/Users/alanwhite/VirtualBox VMs/WIn10/Snapshots' (snapshots) is unknown
00:00:02.255024 File system of '/Users/alanwhite/Virtual Machines/WinDev10.vdi' is unknown

Did you manually move the VDI? Is this VDI coming from somewhere else?

00:00:02.153074 Host RAM: 8192MB (8.0GB) total, 2750MB (2.6GB) available
00:00:02.318682 RamSize <integer> = 0x0000000100000000 (4 294 967 296, 4 096 MB, 4.0 GB)

You are assigning memory to your guest, that you do not have available. Either close some applications on the host, buy more RAM for the host, or reduce the amount of RAM assigned to the guest.

00:00:02.318677 NumCPUs <integer> = 0x0000000000000002 (2)
00:00:02.645750 CPUM: Physical host cores: 2

You have assigned all your CPUs to the VM. The host is going to run low on resources, since VirtualBox cares about physical processors (cores), not logical ones (threads). See "CPU Cores versus threads" and "Why is it a bad idea to allocate as many VCPUs as there are physical CPUs?".

PS. For future reference you should ZIP your logs. It helps you, it helps us, it helps save a (virtual) tree or two...