10-08-2007 2:18 janiquec

Problems installing Windows Server Virtualization (AKA Viridian) CTP on AMD Machines

If like me you have tried to install the WSV CTP on an Acer Ferrari 1000 or 5000, both sport an AMD Turion 64 X2 processor, you have probably encountered a problem starting a virtual machine after a successful installation of WSV. Basically, the error states that the Hypervisor is not running. Well, it turns out according to a blog post from mikekol that "On AMD machines we require that the processor stepping be >=F3 (or that F2 processors have BIOS support)."

I have loaded the latest BIOS from Acer to no avail. So for the time being it looks like anyone with a machine that has an AMD F2 stepping processor (and no BIOS update from the machine manufacturer) is out of luck regardless if the processor supports hardware virtualization extensions (AMD-V). I'll be getting in contact with Acer to find out when I can expect a BIOS upgrade that corrects whatever the issue is with the F2 stepping processor. You can download the CPU-Z utility to help you determine processor stepping (and a wealth of other system info).

Another consideration is that your processor must have the NX option (or XD for eXecute Disable) turned on in the BIOS. 

Finally, be aware that once you install the WSV CTP, there is no upgrade path to future builds of Windows Server 2008. To load a newer Windows Server 2008 build, you will have to either perform a clean installation, or uninstall the WSV CTP before you can upgrade to the newer build.

I'll post again as soon as I get further details on the AMD processor issue.

Share this article in del.icio.us | Digg | reddit

Filed under: , , , ,

# re: Problems installing Windows Server Virtualization (AKA Viridian) CTP on AMD Machines

Friday, February 15, 2008 4:26 AM by Tony Reynolds

Any update from Acer on this ? I have this same issue with my Acer 1007wtm and would love to get this feature working..

# re: Problems installing Windows Server Virtualization (AKA Viridian) CTP on AMD Machines

Tuesday, February 19, 2008 5:03 PM by vs-admin

No new information. The problem required a BIOS update to address an issue with the processor, but no word on getting one produced. I had to buy a Dell D830 because I could not wait for a possible fix.

Leave a Comment

(required) 
(required) 
(optional)
(required)