virtualbox.org

Hello,

I have the following setup on a Windows 10 Host:

* Virtual Box 5.2.36
* Intel i9-9900K
* Virtualization enabled, Hyper-V disabled

and I have the following situation:
* Windows 2012 VM works perfectly fine
* Ubuntu Server VM works perfectly fine
=> * Windows 10 VM, Windows Server 2016+ won't boot, not even from the official installation media (the Microsoft ISO).

I also tried with Virtual Box 6.1 and 6.0, but the result is the same.

I have attached the corresponding log files: I don't see any reason why one VM would run while another one wouldn't.

Thank you in advance to anybody who might be able to help!

I'm afraid that both logs seem to have been grabbed while the VM was still running and therefore had the files open for writing. Both logs are therefore truncated and pretty useless.

One thing I can tell you right now: don't assign 8 cores to any VM. Your host has 8 cores total and therefore it makes no sense to assign them all to one task. Start with 2 cores, only add more only if the VM is CPU bound.

Hello and thank you for your prompt reply!

Please excuse my previous truncated logs. Attached you can find the ones I took after powering off the VM - this time with 6 cores.
I managed to install a windows server 2016 VM. The guests that are not working are Win10 and WinServer2019;

Thanks for the new logs. FYI: you do not have a hardening problem (the hardening log ends with error code 0), so you can skip that log from now on. No point in wasting server space.

Looking at the new VM log, I see a guest OS starting up as normal, e.g. I see the guest additions firing up. Unfortunately you are running the 6.0.0 GAs, meaning that you committed the cardinal sin of running GAs which are newer than the host VBox software (5.3.36). You'd have to boot Windows in safe mode in order to uninstall them.

I understand, but then why would this be happening also when booting from the windows ISO, in a new guest with an empty disc? What can I do in such a situation?

I can only tell you what's in the log you provided. That shows a VM being booted from a hard disk, and loading GAs from a future version of VirtualBox.

If you were really booting from a CD then no GAs would be running and that btw would also ensure that display size changes didn't work properly. How could it, before the drivers are loaded?

Check to see if the VM boot order is set to boot from hdd first.

Sir,

Attached I have uploaded a new log resulted from the following scenario:
* New VM, windows 10 guest.
* Next, next, next on all the steps in the wizard.
* The only change: I set 2 cores, instead of the default 1; I attached the iso file named "en_windows_10_consumer_editions_version_1909_updated_dec_2019_x64_dvd_001f73f0.iso"

Start VM: I see the Windows Logo and nothing else, no other movement at all.
Here's the new log: Thank you for your assistance!

Ok, now I see the VM booting from a CD. 2048MB seems a bit optimistic, but otherwise the settings look fine. Perhaps there is something wrong with the ISO.

Sir,

I assigned 32 GB RAM and the result is the same. Also, I redownloaded the ISO from MSDN, and the result is the same.
Windows Server 2016 works fine ... but Server 2019 and Win10 do not, their behaviour is the same.


Thank you in advance.

I have nothing more to offer right now. As I said, I see no other problem in the log, so perhaps the version of Windows is simply too new. Is it an insider release?

Incidentally, "Win10" is a family, not so much a version. I have Windows 10 VMs which work fine, I believe my newest is 1910 (it's at home, so I can't double check that here at work).

VBox.log file wrote:

00:00:09.734284 IEM: wrmsr(0x122,0x0`00000003) -> #GP(0)

This is a known problem, for details see viewtopic.php?f=2&t=95783. IMHO the best workaround at the moment is to pretend to have an older CPU:

mpack wrote:I can only tell you what's in the log you provided. That shows a VM being booted from a hard disk, and loading GAs from a future version of VirtualBox.

If you were really booting from a CD then no GAs would be running and that btw would also ensure that display size changes didn't work properly. How could it, before the drivers are loaded?

Check to see if the VM boot order is set to boot from hdd first.

THANK YOU mpack, I'm new to Virtual Box & had the optical disc starting first... THANK YOU!