Vmware server 2.0.2 new Virtual machine failed to power on

Please post your .vmx file and the vmware.log file for the failing vm.
Thanks

I do see another post (http://blog.laksha.net/2009/10/vmware-workstation-unrecoverable-error.html) that indicates in some of the comments to be sure to run it as administrator. VMware server 2.x is about the same codebase as Workstation 6.x so you might try setting your service properties for VMware Server to run as the local adminsitrator account rather than local service and see what happens. With 2008, 2008 R2, Vista, Windows 7 there have been issues.

Looking at the HCL (http://www.vmware.com/go/hcl) it appears that Server 2.0.2 is only "Experimentally" supported on 2008 SP2 standard and enterprise, and not supported at all on Datacenter or Web versions

Good Lucki

Thanks for quick reply. Please find attached vmx file and the log file.

By the way, I've configured th local administrator account as the log on account of all VMware services but it didn't make any difference.

Sorry, file attached again.
vmx-and-log.zip

Nice box! 6-core hyperthreaded processors?

Anyway - was this VM imported from an ESX(i) platform? I am surprised to see a ft.secondary0.enabled = "TRUE" in the vmx, along with a few other parameters.

You might try:

1. Rename your test08 folder
2. Generate a new Win2k8 vm as test08 without a disk drive. This should get a more compatible Server 2 vmx file
3. Move or copy the test08.vmdk file(s) to the new test08 folder. There may be a -flat.vmdk file, if so don't miss it.
4. Add a hard disk to your vm, select use an existing disk, and pick your test08.vmdk
5. Try to power it up

Good Luck - Let me know what happens

Another thing you can try - if this is being moved from another VMware platform, try to do it as a V2V conversion using VMware converter, rather than copying the files. You may have to change the VM OStype on the source platform to Vista in order to get converter to like it. People have had issues with various flavors of converter on 2008 vms. Don't forget to change it back when you are done.

Hi Bgoering,
Thanks for your replies.
The vm a newly created one from VMware server, not am imported one from ESX(i).
I've tried your suggestion, renamed the folder, created a new vm, copied vmdk files and then link it to the new vm, but still getting same error.

I've even tried to create a 32bit winXP vm, same result.
Any thoughts?

test - having trouble entering a response

Trying it again. Looking at the VMware server user guide ( http://www.vmware.com/pdf/vmserver2.pdf ) I find:

"VMware Server hosts must meet the following requirements:
    Standard x86-compatible or x86-64-compatible server with up to 16 processors."

I am thinking you may be getting the NOT_IMPLEMENTED error because server is seeing 32 logical processors whereas, according to the documentation, it is only rated for 16.

Have you ever been able to power on a VM on this host? One thing to try is, again I am assuming you are running four 4-core CPUs with hyperthreading enabled, turn off hyperthreading. This would reduce the number of logical processors to match the number of physical cores and be within the limit of 16 for VMware server. Don't know if that is a long term solution, but it is something one could easily test.

A better solution, again in my humble opinion, would be to install ESXi directly on the R910. ESX(i) supports up to 128 logical processors and could better exploit your new system - probably much more effectively than your Windows 2008 SP2 that is running there now. Your Windows 2008 could always run as a VM under ESXi.

Let me know what you find

bgoering,
Thanks for finding  out this:
"VMware Server hosts must meet the following requirements:     Standard x86-compatible or x86-64-compatible server with up to 16 processors."
If it's true, it will be bit of pain then as the reason why we purchased this server is due to some CPU intensive testing tasks and ESX(i) solution cannot meet our requirement since it only support max 8 vCPU on a single virtual machine.
Anyway I will test it and let you know the result.

Actually I have posted a related question  in regards to our special requirements and I am still waiting for some expertise with it:
https://www.experts-exchange.com/questions/26386501/Virtualization-solution-for-CPU-intensive-task.html

Maybe you can have a look at it so as to get better understanding our needs.
Thanks again.

To answer your question:
Have you ever been able to power on a VM on this host?

No, I've just finished build of win2008 + vmware server 2 and that is the first vm I've created for testing.

BTW, the new server has 4 x 6-core CPUs and I can see 48 logic processors from the task manager.

I guess I figured out it was 6-core when I first looked at it - not sure why I thouht it was "only" 32 logical processors earlier today lol. Guess turning off hyperthreading won't do much good because there will still be 24 which is more than 16, so I would expect the same result.

I took a glance at your other thread - will the HPC cluster on ESXi not work for you? I am not a HPC expert, but see no immediate reason that it won't work.

Another thing you could try is VMware Workstation 7.1.1 - Free trial is available. Couldn't find any doc about what it will support in terms of number of cores - just that "mult-processor" systems are supported. And it is a couple generatious newer software than VMware Server 2.x

Good Luck

I found this vmware kb:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1008158

And I followed the instruction to server and replaced vmware-vmx.exe to a 32 bit one.
Then tried to power on the vm again. This time it doesn't crash but it just hang on 95% of powering on process, looks like frozen.
Tried another vm and got same result.

This is bizarre.
I think I might have to try Microsoft Hyper-v instead of VMware server.
What do you reckon?

VMware ESX(i), but for our special situation it's a pity that we can only stick on VMware Server.

I will test Hpyer-v then, instead of VMware station.

I've given up VMware and moved to Hyper-v.
thanks for all the help.