Window Server 2016 installation crashes on virtualbox

[Incognito333]

I just upgraded to the current version of the virtualbox to create new vms with an iso image, but it fails after loading windows for installation. I looked at the log file, but it is huge so I don't know what I'm looking for.

It keeps pausing (the screen goes gray) when trying to complete the installation.

[scottgus1]

Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.

Right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.

[AndyCot]

Do you have hyper-v enabled?

[Incognito333]

Not running Hyper-V yet. I can't get into the OS, because the installation never completed.

The log file has been added.

[BillG]

I think Andy was asking "are you running Hyper-V on the host PC". Even if you have not enabled it yourself, the host may have the Windows hypervisor running, and that can interfere, sometimes severely, with a VirtualBox guest. Hyper-V is unlikely to run in a Windows Server OS running as a VirtualBox guest.

Your log file does not show that as your problem. Your problem is not enough memory available on the host.

Code: Select all

00:00:02.803860 Firmware type: BIOS
00:00:02.803886 Host RAM: 4001MB (3.9GB) total, 897MB available
00:00:02.803890 Executable: C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
00:00:02.803891 Process ID: 1864

[scottgus1]

So far, this one's easy:

00:00:02.803886 Host RAM: 4001MB (3.9GB) total, 897MB available
00:00:03.104353 RamSize <integer> = 0x0000000080000000 (2 147 483 648, 2 048 MB)

Nowhere near enough host RAM for the VM setting. Windows will want all RAM at the start, so it all has to be free. Reboot the host so RAM is as freed up as possible, then start the VM before anything else is started.

BTW, the line in the log regarding Hyper-V is this one (or something like it, saying VT-x or AMD-V is present:

{timestamp} HM: HMR3Init: VT-x w/ nested paging and unrestricted guest execution hw support

If you see that , you're free and easy, no Hyper-V impingements.

If you see this:

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

then host Hyper-V is involved.

[BillG]

@scottgus2

Hi Scott. great minds think alike!

[scottgus1]

Oops! Had you posted that already, Bill? I gotta read better!

[BillG]

Just another point we both missed first time around. The log shows the OP is running a Windows 7 host, so Hyper-V was never a chance as the cause.

[Incognito333]

I resolved the initial issue and the files loaded, but then I got a black screen and before Windows Server 2016 ever loaded. I added the log file and went through it, but nothing stands out.

Please advise.

[scottgus1]

The log shows a VM restoring from saved state and not fully shut down when the log was taken.

Please follow the instructions you received above and post a new log showing the problem happening.