CPU not compatible with 64 bit mode.

[Astro Head]

Hi Everyone,

I'm totally new to this and this is my first post so forgive me if I'm asking what seems to be a simple question to you.

I have a server that I use to host Exchange running under SBS2008.

The current installation has a problem in that it will not do any automatic updates.

My first thought was that I could simply do a repair installation but you can't do that with SBS. Secondly I thought that would upgrade to SBS2011 but you can't perform an in place upgrade from one to the other; good old Microsoft.

The only way to do it is to 'migrate' to SBS 2011. However this assumes that you are going to install SBS2011 on a shiny new server. I'm not going to and don't want to do that as my server hardware is only 12 months old and I've no need to change it.

I had the idea of converting my existing SBS2008 installation to a VM, install SBS2011 on the existing server hardware and then 'migrate' the SBS2008 to SBS2011.

I've done the conversion using VMWare's conversion tool and created a test system on my Windows 8 PC, however, when I try to run the SBS2008 VM I get the following error message in the VM window:

Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:

"Usual list of things to do"

File: \windows\system32\winload.exe

Status: 0xc000035a

Info: Attempting to load a 64-bit application, however this CPU is not compatible with 64-bit mode.


The cpu in my PC is 64 bit and I'm running 64 bit Windows 8 if that has any bearing.

Is there a workaround to this or am I just unable to do it.

- Neil

[Perryg]

The error indicates that you have not enabled hardware virtualization (in your pc bios) or your CPU does not support hardware virtualization.

[Astro Head]

Thanks for the reply.

Since posting I've done a check to see if my processor supports Hardware Virtualization and unfortunately it doesn't so it's time to go back to the drawing board.

- Neil

[Astro Head]

OK, I've now got my SBS2008 VM running on the original server hardware.

The problem that I have now is that I cannot access Exchange at all, it used to work perfectly before I converted it into a VM so I'm thinking that there is something simple that I'm missing. Even programs that are running in the same VM cannot access it they are reporting that smtp port 25 is blocked.

I can't Telnet to the VM from any other PC or the Host although I can ping it from anywhere by its name or ip address.

- Neil

[mpack]

If the VM is running then everything else is a matter of proper guest configuration. VirtualBox is mostly not relevant except to say that most servers will require a full network interface, i.e. bridged, not NAT.

If you want to discuss this further then provide a log file for the new situation. See Minimum information needed for assistance.

[Astro Head]

I'm running version 4.2.18 r88780.

Guest additions are installed in the Guest.

Host is running Windows 7 64 bit fully updated with 5gb of ram

Guest is running SBS2008 64 bit with 1.5gb allocated to it, network is Bridged.

I've attached all logs.

- Neil