- Joined
- Feb 20, 2001
Introduction
This is an all-in-one sticky to cover installation on all platforms. Please let me know if anything needs added or fixed. This is based on a number of other threads by the following members. Thanks to them for their contributions:
The Basics
Originally written by Cluster
This guide is for anyone running dual or quad-core setups that need windows as their main OS, but want more PPD than the windows SMP client can provide. The reason for this is that the linux client is more effecient(even through a VM) and also the linux client has access to A2 WUs which seem to provide much better throughput and thus more PPD.
Before i begin i'd like to make a couple of notes. If you can at all, it is better to run linux as your main OS as you remove the overhead of the VM, obviously getting even better output. Now results may vary with systems and time, after going through this myself, i went from 1100ppd to 3-4k ppd, not a trivial increase. One more thing, make sure you have the ram for this. Each of my VMs uses between 550-650mb of ram.
Also, while this guide uses Ubuntu 8.04, you can use any linux distro. Ubuntu is not the lightest choice, but it is the simplest to get setup on. For those that wont to setup a VM in order to clone across multiple systems, a slimmer Linux install might be better as you can get away with much less than a 5gb disk to install the OS on.
System requirements
1.5GB of Ram
15GB HDD Space (using Ubuntu 8.04)
All your cpu cycles!
The basic process goes something like this :
Both VmWare and Ubuntu are big downloads. VmWare is a little over 100mb, Ubuntu is around 700mb. Will give you lots of time to skim through the guide once or twice.
Now that the hard part is over with, we're almost done, the last step is to make a copy of your new VM.
I - Windows Vista 64-bit notes
Quote:
Windows 64-bit users are going to have the problem of windows complaining about unsigned drivers. For this you have a couple of options.
A) Use Vmware server 2.0. I did do an install of vmware 2.0 and windows did not complain. But i have not configured a vm with it yet. In the future perhaps i will do this, or if someone else cares to, i will add the install procedure for vmware server 2.0.
B) Before windows starts loading, just after your bios finish the POST routine, hit your F8 key and it will bring up an advanced boot menu. In there is an option to disable driver signature checking. The only annoying part is, you will have to do this every time you reboot. This is what i do, but i have to go through a multi-boot menu regardless.
C)For this option you will have to perform the above operation for the install of vmware server 1.0.x, reboot, F8, select disable driver signing, and install vmware. There is also an application that will enable 'Test Mode' for vista64. This is designed for developers who are creating drivers that are not yet signed. It allows you to set Test Mode on which is basically the same as doing (B). Hit up google for enabling windows vista 64 test mode for more info.
II - Setting vmware priority/affinity
Quote:
Once everything is up and running. Hop into Task Manager and find the two vmware-vmx.exe processes. If you use this system, and its not a dedicated folding rig, you'll want to set their priority to Low. Otherwise you will notice some lag as the vmware priority overrides the clients. So instead of your clients picking up idle cycles, they'll be competing for cycles like every other process, and generally they win
Now for affinities, its recommended to set one processes to cores 0/1 and the other to cores 2/3. Latest word from the new nvidia drivers is their client is using very little cpu time, so this would be a good setup even for those with nvidia gpu clients.
If you have ATI clients running, atm they're still using a good part of 1 core, then set _both_ vm processes to 0/1/2 and let the gpu client have core 3. The gpu client may not pick up all of core 3, but there are some other processes aside from the vmware-vmx ones that the vm is using. This will pick up whats left on core 3. On my system, this is what i do, and core 3 is averaging 95-97%, while cores 0/1/2 are almost solid at 100%. I tried doing core 0/1 to one vm and just core 2 to the other, and it didnt seem to work all that hot, ymmv.
III - Setting up VMWare Tools by the_cultie
Quote:
This is an all-in-one sticky to cover installation on all platforms. Please let me know if anything needs added or fixed. This is based on a number of other threads by the following members. Thanks to them for their contributions:
- Adak - SMP/Ubuntu (Post #1)
- Jolly-Swagman - SMP/Vista or XP (Post #2)
- Harlam357 - SMP MPICH2 Client (Post #3)
- Nitteo - GPU2 (Post #4) [Also link to GPU2 for Linux]
- Leelegend - SMP/VMWare (Post #5)
- Landshark - Multi-GPU2 (Post #6)
The Basics
- How does it work?
Folding@Home downloads a chunk of data, processes it and returns the results to Stanford who assemble all the data and can determine if any interesting results have been raised. - Why different clients?
There are clients for various platforms, and each is optimised for the platform it runs on:- Classic client is the easiest one to deal with and can run on Mac OSX (PPC or x86), Linux or Windows (98SE or later).
- SMP Client for XP and Vista is optimised for multiple-core systems, particularly quad core chips.
- GPU2 client runs on Graphics Cards
- Playstation 3 client runs on... PS3s!
- Where do I get it?
Download it from here. - What team do I fold for?
We are Team 32!
Originally written by Cluster
This guide is for anyone running dual or quad-core setups that need windows as their main OS, but want more PPD than the windows SMP client can provide. The reason for this is that the linux client is more effecient(even through a VM) and also the linux client has access to A2 WUs which seem to provide much better throughput and thus more PPD.
Before i begin i'd like to make a couple of notes. If you can at all, it is better to run linux as your main OS as you remove the overhead of the VM, obviously getting even better output. Now results may vary with systems and time, after going through this myself, i went from 1100ppd to 3-4k ppd, not a trivial increase. One more thing, make sure you have the ram for this. Each of my VMs uses between 550-650mb of ram.
Also, while this guide uses Ubuntu 8.04, you can use any linux distro. Ubuntu is not the lightest choice, but it is the simplest to get setup on. For those that wont to setup a VM in order to clone across multiple systems, a slimmer Linux install might be better as you can get away with much less than a 5gb disk to install the OS on.
System requirements
1.5GB of Ram
15GB HDD Space (using Ubuntu 8.04)
All your cpu cycles!
The basic process goes something like this :
[*]Download VmWare and Ubuntu
[*]Install VmWare
[*]Install Ubuntu
[*]Configure Ubuntu and download F@H
[*]Install VmWare Toolso
[*]Copy the VM
[*]Configure the client and Fold Fold Fold!
Both VmWare and Ubuntu are big downloads. VmWare is a little over 100mb, Ubuntu is around 700mb. Will give you lots of time to skim through the guide once or twice.
- Vmware Server 150MB
A Note for Vista64 users. If you try to install vmware, it is going to complain about unsigned drivers. See Appendix I for details.
For those who might wish to take the leap to guinea pig status, VmWare Server 2.0 is the latest offering. It uses a Web UI instead of a regular GUI. I haven't been successful at getting the web ui to load, probably because i neuter my windows installs *shrug* - Ubuntu Download [700MB]
!!! Remember to choose 64-bit !!!
It does not matter if you use a 64-bit Host OS or not. Its all the same if your on 32-bit windows, but the guest linux OS needs to be 64-bit. Also it was reported there was some issue with kernel version supplied in Ubuntu 8.10. Until i hear different i'll recommend using 8.04-64bit, or until a new Ubuntu release is available to test on.
- Install VmWare Server
Pretty straightforward, just install with the rest of your software. Vista64 users read Appendix I before doing this or windows will crap on you. - Create directories for VMs
You'll want to create two directories for each VM. I named mine C:\FAH\SMP1 and C:\FAH\SMP2. - Configure your VM
Start up the VmWare Server Console, localhost should be highlighted, select connect, then create a new virtual machine.
Note: If when you boot up windows, and open the console to start your VMs, the localhost option is not shown, this means that the services have not started yet. It takes them a few seconds, close the console and try again in a minute.- Select Custom install
- The type of Guest OS is Linux -> Ubuntu-64bit
- Name the VM (SMP1) and select the directory you created earlier (C:\FAH\SMP1)
- Leaving access rights and startup/shutdown at default is fine.
- Select 2 Processors
- Set the amount of ram for the VM (Min: 640, Recommended: 768)
- Select Bridged Networking.
- Create a 5GB Virtual Disk - Allocate all disk space now
- Name the disk whatever you like and hit finish.
- Select your VM from the Tabs at the top if its not already. In the main window below Start this VM, click Edit this VMs settings. We want to configure a CD-Rom that points to our Ubuntu ISO. Click CD-Rom on the left, and on the right there will be an option to set the drive to read an ISO image. Select the ISO option and point it to your Ubuntu ISO.
- Start the VM and install Ubuntu
For the most part you should be able to select the default install setup. Selecting timezone/keyboard/language as needed.
- Configure Ubuntu
Once your at the Ubuntu desktop, feel free to change your desktop, some people aren't to partial of the stork- Install the 32-bit math libs for F@H
Code:
> sudo apt-get install ia32-libs - Open FireFox (you should see it on the taskbar at the top) and make your way to the Stanford F@H Page, download the linux client. You should see a tarball (.tar.gz file) on your desktop.
- Double click the archive to open the archive manager, click extract, and choose a location. I put mine in /home/[username]/FAH. Do not start the folding client until you have finished and have the second VM copied. They need to be configured separately.
- I highly recommend that you install VmWare Tools at this time. Amongst other things, it adds in time synchronization between host/guest OSes. See Appendix III for the install of this.
- If you want to setup samba, which will allow you to share your FAH directory and make it visible to FahMon, see Appendix IV for the samba setup.
- Install the 32-bit math libs for F@H
Now that the hard part is over with, we're almost done, the last step is to make a copy of your new VM.
- Stop the VM you have running already.
- Go to the directory where you created the VM and copy all of the files over to the other directory you created. (Copy from C:\FAH\SMP1 to C:\FAH\SMP2). This may take a couple of minutes as it is copying the 5gb vitual hard driver you created.
- Hop back into the VmWare Server Console, select File > Open > Browse, point it to your _second_ vm (C:\FAH\SMP2) and select the file that shows up. It will ask you if you have copied this VM and if you would like to create a new Machine ID, select create new machine ID.
- You should now have two VMs in VmWare. Start them up, open the command line console, go to the directory where you unzipped the client (/home/[username]/FAH), configure the clients, and enjoy your awesome PPD.
Code:
> cd ~/FAH
> ./fah6 -smp -verbosity 9
I - Windows Vista 64-bit notes
Quote:
Windows 64-bit users are going to have the problem of windows complaining about unsigned drivers. For this you have a couple of options.
A) Use Vmware server 2.0. I did do an install of vmware 2.0 and windows did not complain. But i have not configured a vm with it yet. In the future perhaps i will do this, or if someone else cares to, i will add the install procedure for vmware server 2.0.
B) Before windows starts loading, just after your bios finish the POST routine, hit your F8 key and it will bring up an advanced boot menu. In there is an option to disable driver signature checking. The only annoying part is, you will have to do this every time you reboot. This is what i do, but i have to go through a multi-boot menu regardless.
C)For this option you will have to perform the above operation for the install of vmware server 1.0.x, reboot, F8, select disable driver signing, and install vmware. There is also an application that will enable 'Test Mode' for vista64. This is designed for developers who are creating drivers that are not yet signed. It allows you to set Test Mode on which is basically the same as doing (B). Hit up google for enabling windows vista 64 test mode for more info.
II - Setting vmware priority/affinity
Quote:
Once everything is up and running. Hop into Task Manager and find the two vmware-vmx.exe processes. If you use this system, and its not a dedicated folding rig, you'll want to set their priority to Low. Otherwise you will notice some lag as the vmware priority overrides the clients. So instead of your clients picking up idle cycles, they'll be competing for cycles like every other process, and generally they win
Now for affinities, its recommended to set one processes to cores 0/1 and the other to cores 2/3. Latest word from the new nvidia drivers is their client is using very little cpu time, so this would be a good setup even for those with nvidia gpu clients.
If you have ATI clients running, atm they're still using a good part of 1 core, then set _both_ vm processes to 0/1/2 and let the gpu client have core 3. The gpu client may not pick up all of core 3, but there are some other processes aside from the vmware-vmx ones that the vm is using. This will pick up whats left on core 3. On my system, this is what i do, and core 3 is averaging 95-97%, while cores 0/1/2 are almost solid at 100%. I tried doing core 0/1 to one vm and just core 2 to the other, and it didnt seem to work all that hot, ymmv.
III - Setting up VMWare Tools by the_cultie
Quote:
- When you have your VM open go the toolbar and click VM and select Install VMware Tools. A window will appear asking you to make sure the guest operating system is running. Click install to proceed.
- On the guest OS desktop there should now be a DVD icon called VMware tools. Open it and extract the contents of the file called VMwareTools-1.0.8-xxxxxx.tar.gz to your Home Folder (also called [username] in the extract manager). It’s a good idea to go into the Home Folder and re-name the vmware-tools-distrib to something short like vmt as it saves some typing later on.
- Open up Terminal and enter the following:
-> cd ~/vmt
-> sudo ./vmware-install.pl
It will then ask you to select where to install the Binary Files, Init Directories, Init Scripts, Daemon Files, Library Files, and the Documentation. For each one just press enter and they will be installed in default locations. You will then be asked if you want to VMware Tools; just press enter to continue. - When the configuration starts you may get the following warning depending on the version of Linux you are using:
None of the pre-built vmhgfs modules for VMware Tools is suitable for your running kernel. Do you want this program to try and build the vmhgfs module for your system (you need to have a C compiler installed on your system)? [yes]
Just press enter and when it asks for the location of the directory of C header files just press enter again for the default location. The module is then built.
When it is finished press enter again to continue. You are then asked to select a resolution for you screen by selecting a number from the list 1-13 where each number is for a different resolution. Press enter after making you selection and VMware Tools is installed. You should then re-start Linux before continuing. - After restarting Linux its time to actually configure VMware Tools to keep the time synchronized with your system time.
Open Terminal and enter the following:
-> vmware-toolbox &
This will launch the VMware Tools. On the first tab of the window that open you will find an option for Time Synchronization Between the Virtual Machine and the Host Operation System. Tick the box beside it and click close. Your time will now stay synchronized with your system time.
Last edited by a moderator: