Critical Error starting my first machine running windows server

[mikecies]

Cannot figure out the error, have the most recent version updated, provided a zip file of my log

[scottgus1]

The guest guru-meditates with this:

00:00:27.463654 PGMR3PhysAllocateLargePage: allocating large pages takes too long (last attempt 110 ms; nr of timeouts 11); DISABLE

soon after touching the CD-rom.

RAM might be not contiguous to allow a block for the guest, try a host reboot:

00:00:07.470095 Host RAM: 8151MB (7.9GB) total, 3716MB (3.6GB) available
00:00:07.920224 RamSize <integer> = 0x0000000080000000 (2 147 483 648, 2 048 MB)
00:00:07.920700 VRamSize <integer> = 0x0000000008000000 (134 217 728, 128 MB)

Windows 2019 is Windows 10 with less eye candy and more server. 10 likes 2 cores minimum, 2019 might too:

00:00:09.770801 CPUM: Physical host cores: 4
Guest CPU settings:
00:00:07.920218 NumCPUs <integer> = 0x0000000000000001 (1)

If the above changes don't fix things, try a new guest with 2016 64-bit instead of 2019 64-bit. There was word on the forum that the 2019 template might have had a bug in it.

Also, a safety point: Dynamically expanding VHD has a design flaw that can kill the whole disk. VDI & other disk types don't have this flaw. If you must use a VHD to maintain compatibility with Windows mounting requirements, use fixed-size VHD and leave yourself enough room in the VHD size to allow the guest to grow, as fixed VHD does not have the design flaw but fixed drives cannot be increased in size.

[mikecies]

The project requirements are that I have to use the windows server 2019 download, so running 2016 will not be feasable.

[fth0]

If the above changes don't fix things, try a new guest with 2016 64-bit instead of 2019 64-bit. There was word on the forum that the 2019 template might have had a bug in it.

If you're referring to the Paravirtualization Provider setting Default leading to None, the bug is in both templates ...

The project requirements are that I have to use the windows server 2019 download, so running 2016 will not be feasable.

If I'm guessing right (see above), scottgus1 meant that inside the VM configuration, you should set the guest OS Version to Windows 2016 (64-bit). Ignore that and set the Paravirtualization Provider to Hyper-V instead. The latter will not hurt in any case.