Page 1 of 1

Missing log in dialog after updating to latest version

Posted: 23. Jan 2018, 15:06
by zabdullah
Hello
I went from version 5.2.2 to version 5.2.6 (latest) after two months of inactivity and after updating the GA and following a reboot Windows 10 professional instance is not showing me the login dialog. Has anyone else see this kind of behavior? If so any help will be appreciated.
thank you
Z.

Re: Missing log in dialog after updating to latest version

Posted: 23. Jan 2018, 15:11
by socratis
Did you try and click on the VM after some time? It does that with mine. The Preview (in VirtualBox Manager) shows OK, but the actual guest window is black until I click on it. In any event, we're going to need to see a VM log from a complete VM run:
  • Start the VM from cold-boot (not from a paused or saved state) / Observe error / Shutdown the VM (force close it if you have to).
  • With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
  • Save only the first "VBox.log", ZIP it and attach it to your response (see the "Upload attachment" tab below the reply form).

Re: Missing log in dialog after updating to latest version

Posted: 23. Jan 2018, 17:13
by zabdullah
Hi
thanks for your help. I've attached the 1st log file. the windows 10 main page shows up with a picture of a bird - also attached in the zip. nothing happens when I click around.

thanks
Z.

Re: Missing log in dialog after updating to latest version

Posted: 23. Jan 2018, 19:28
by socratis
00:00:01.573449 Host RAM: 8192MB (8.0GB) total, 1938MB available
00:00:01.816203 RamSize <integer> = 0x0000000100000000 (4 294 967 296, 4 096 MB, 4.0 GB)
You're low on the available memory on your host. You host is going to be swapping like crazy.
00:00:01.816263 NumCPUs <integer> = 0x0000000000000004 (4)
00:00:02.129090 CPUM: Physical host cores: 4
00:00:02.129828 Full Name: "Intel(R) Core(TM) i7-4750HQ CPU @ 2.00GHz"
Same for the number of CPUs. You have 4, you give 4. Not a great idea...

Other than that, I don't see a smoking gun. Try to lower your RAM to 3072 MB, the CPUs to 2, and try to free some host RAM by quitting a couple of heavy hitters. Also, try to keep an eye on your RAM with Memory Monitor.