Another Windows Server 2012 0x000000c4 problem?

[John Connett]

I am trying to install a Windows Server 2012 R2 guest on a Windows 8.1 Enterprise 64-bit host and am hitting the "Error Code: 0x000000c4" problem despite having applied the suggested:

VBoxManage setextradata [vmname] VBoxInternal/CPUM/CMPXCHG16B 1

I note that Windows Server 2012 R2 requires CMPXCHG16B; LAHF/SAHF; and PREFETCH/PREFETCHW. However, the "VBox.log.1" file contains the following lines:

Code: Select all

00:00:01.340940 Enabling CMPXCHG16B for Windows 8.1 / 2k12 guests
00:00:18.962351 CMPXCHG16B instruction                 = 1 (1)
00:00:18.962526 LahfSahf - LAHF/SAHF in 64-bit mode    = 1 (1)
00:00:18.962540 8  - PREFETCH and PREFETCHW instruction= 0 (1)
00:00:01.761413   CMPXCHG16B   <integer> = 0x0000000000000001 (1)

which suggests that the guest may not have PREFETCH/PREFETCHW.

Note that this also fails with "Enable EFI" but not with "Error Code: 0x000000c4".

Any hints as to what the problem may be and if there is a work around? The host system can boot from the .iso to the language specification page of the install. The host system lacks SLAT so cannot run Hyper-V. I'm happy to supply further details or try other options on request.

More details below:

VirtualBox Version: 4.3.8.r92456

Host: Windows 8.1 Enterprise Evaluation

• Processor: AMD Athlon(tm) 64 X2 Dual-Core Processor TK-55 1.80GHz
  Installed Memory (RAM): 2.00 GB (1.75 GB usable)
  System type: 64-bit Operating System, x64-based processor

Guest: Windows Server 2012 R2 Evaluation

• Memory Size: 850 MB
  9600.16384.WINBLUE_RTM.130821-1623_X64FRE_SERVER_EVAL_EN-US-IRM_SSS_X64FRE_EN-US_DV5.ISO

[Perryg]

Windows EFI in VirtualBox is not supported.
Uncheck it and try to install again.

[John Connett]

Windows EFI in VirtualBox is not supported.
Uncheck it and try to install again.

Apologies for the lack of clarity. The example I gave failed with "Enable EFI" unchecked. Thanks for the information regarding Windows EFI.

[Perryg]

Maybe, but the log you posted was with EFI enabled and as such is unusable. Post a log file of one without EFI.

[John Connett]

Maybe, but the log you posted was with EFI enabled and as such is unusable. Post a log file of one without EFI.

My apologies. Removed all the logs and reran. Only one file created.

[Perryg]

Here's what the log says:
00:00:01.430944 Host RAM: 1790MB total, 897MB available

00:00:02.769620 RamSize <integer> = 0x0000000035200000 (891 289 600, 850 MB)
00:00:02.770131 VRamSize <integer> = 0x0000000008000000 (134 217 728, 128 MB)

Available = 879MB

Allocated = 850+128 or 978MB ( overcommitment RAM )


00:00:34.819687 Console::powerDown(): A request to power off the VM has been issued (mMachineState=Stopping, InUninit=0)

Then you shut it down after 34 seconds of uptime. Given the lack of real memory I would not be surprised if it took minutes to hours to install Window 2012 server, especially on a Windows 8 host with less than 2 GB of RAM and only 897MB free.

[John Connett]

Thanks for the reply. I powered down after receiving

Your PC needs to restart.
Please hold down the power button.
Error Code: 0x000000C4
Parameters:
0x0000000000000091
0x000000000000000F
0xFFFFF803EA362A80
0x00000

which I took as the point of no return. I left to run it repeats the 0x000000C4 message until

VirtualBox - Guru Meditation

A critical error has occurred while running the virtual machine and the machine execution has been stopped. [...]

Logs of the full run (VBox.log, VBox.png) attached.

I have installed the same release of VirtualBox onto a more recent system running OpenSUSE 13.1 (Linux_VBox.log), used the same settings (including RamSize 850 MB) and the installation runs to completion.

I have also tried the .vdi file from the OpenSUSE system on the Windows 8.1 system which also fails to boot with repeated 0x000000C4 messages. I also tried reducing the memory to 700 MB in case the problem was overcommitment of RAM. Same result.

Now I know it's pretty silly trying to install this on elderly hardware but I'm trying to evaluate something for a volunteer run museum (http://www.museumoftechnology.com) with very limited resources. Windows Server 2012 R2 will boot to the language selection screen on the host. On the guest it goes "Loading Files" -> "Wonky Blue Squares" -> Error Code: 0x000000C4. It feels like the guest is missing a feature present on the host. Maybe what I'm trying is impossible but I would like to know why.

[mpack]

I also tried reducing the memory to 700 MB in case the problem was overcommitment of RAM.

There's no "in case" about it. You are still giving the VM RAM you don't have, i.e. :-

00:00:01.344515 Host RAM: 1790MB total, 788MB available
...
00:00:01.891212 RamSize <integer> = 0x0000000035200000 (891 289 600, 850 MB)
...
00:00:01.892235 VRamSize <integer> = 0x0000000008000000 (134 217 728, 128 MB)

850+128=978 (too much). 700+128=828 (still too much). I should also point out that a bit of tuning will not fix this - if you want stability then you need to leave the host with some RAM "headroom". As a general rule of thumb, the total of RAM+VRAM (in your case 850+128) should not exceed around 50% of the available RAM, i.e. not exceed ~400MB. If course that's unlikely to be a very good allocation for a 64bit guest.

Frankly, your PC doesn't have the resources to run two instances of 64bit Windows.

[Perryg]

On the Windows side you are receiving a triple fault at 1:59 into the session. This is a problem with 4.3.8 on some hardware and is being fixed for the next maintenance release.

On the Linux side the CPU is being read incorrectly IMHO and probably why you are having issues. Here again the same issue as above.

Code: Select all

00:00:00.550529 CPUM: Matched host CPU INTEL 0x6/0x3a/0x9 Intel_Core7_IvyBridge with CPU DB entry 'Intel Core i5-3570' (INTEL 0x6/0x3a/0x9 Intel_Core7_IvyBridge)
00:00:00.769794 Full Name:                             Intel(R) Xeon(R) CPU E3-1275 V2 @ 3.50GHz

Now the two may be equal but given the issues you are having I would say that this is a place to start. You should create a ticket at bugtracker and provide this information so the DEVs can make sure.

[drdigitial]

Is there a resolve for this error? my host is win 7 Ultm. I tried every thing.

Critical while running Vetural machineerror. Code:0X000000C4, Paramaters: 0x0000000000000091,0x0000000000000F,0xFFFF
F8008A1BAA80, 0x000000
3 GB of ram with 2.40Ghz processor.

[mpack]

Well, in the case of the above thread, the "resolve" is to buy more RAM, and perhaps revert to 4.3.6.

[klaus]

I know that it's not the cause of this issue, but just to mention it in a place which talks about those 0x000000c4 issues: the lack of NX/XD/DEP (no execute / execute disable / data execution prevention) will also lead to these symptoms. There will be a warning in the log about NX, which can't be made stronger as not all CPUs have NX support (Windows 8 etc. will not run on them, period).

Some BIOSes offer a config setting for this, and that means it's another potential BIOS misconfiguration.