Not getting credit in a VM

[benbaked]

I had (I say had because I've since deleted them) two VMs on my QX6700 that were copies of my ubuntu 7.10 VM from my E6600. When I copied them over to the quad I got VMware to recognize both as separate VMs, that is they were both in separate directories and I could run ubuntu updates on each one independently. I had fah6 installed on both, but before I ran it on either I deleted each one's queue.dat, config file, and work directories to give myself a fresh go at it.

I was running both and according to Task Manager fah was running in both VMs, taxing my CPU at 100%, and each VM was keeping track of its WU. When each completed I was only credited with one WU. I just noticed this last week, but I feel this may have been an issue dating back to just before the Chimp Challenge. During the Chimp Challenge I also had my E6600 running fah in its VM (this was the original VM that I made the copies from) and I'm unsure if I got credit for any of those either since it was folding under T32monkeys. I have since deleted both VMs and I'm running seti full time on this quad.

Any ideas why I would only be credited with one WU, although WUs were completing in both VMs? Do I need to have fresh VMs from scratch every time? I was under the impression that removing the fah config file, queue.dat, and work directories would be enough. Thanks in advance.

[ChasR]

My guess is you copied the FAH installation from VM1 to VM2 causing the AS to see the two VMs as the same machine. THey wound up folding identical WUs and only getting credit for the first turned in.

[benbaked]

Yeah that makes sense, I thought deleting the config and work queues would protect against that but perhaps I did not do it correctly. In the future will it work if I make copies of the VM before running FAH for the first time? Can I correct this by deleting the VM's FAH directory and then re-downloading the FAH client?

[ChasR]

All you have to do is change the machine ID in config. Make VM1 Machine ID 1 and the VM2 Machine ID 2. Problem solved. You could also delete the file machinedependent.dat in one vm which will cause the assignment of a new User ID.

[harlam357]

Can I correct this by deleting the VM's FAH directory and then re-downloading the FAH client?

Yep... I've done that on several occasions.

When setting up my second and third quad I just copied a VM from the first quad and for each VM instance deleted the FAH directory, recreated it, and downloaded the client again. That's all I did besides modify the Samba config on each VM to change the NetBios name.