This page includes setup instructions and screenshots for installing both the native and virtual folding images. The native image should work for VMware also. I setup a dedicated image for Virtualbox due to some kernel modifications that are more optimal for Virtualbox and to enable vbox-additions. For virtual images, make sure to enable VT in BIOS.
Native ISO Image Installation
1) Write the ISO image to a CD.
2) Make sure that only the CDROM and the one hard drive that you want to overwrite with the image are connected to the motherboard.
This is to prevent accidental overwriting of the wrong hard drive.
3) Bootup the system with the CD. Hit Enter at the boot menu.
4) After bootup, the image will give some basic instructions. Enter the command list to see a list of disks found. This will help you
determine where to write the image to. If you have only the CDROM and one hard disk connected, then only these two devices should
show up in the list.
5) Write the image using the command write sdx. Replace sdx with the disk shown by the list command. For example, the name may be
hda or sda depending on system configuration. This will overwrite the first 3.6GB of the disk you enter without warning. Make sure
this is what you want to do before proceeding.
6) The write process may take 10-20 minutes. When finished, enter the command reboot and remove the CD. The folding image should
now boot via the hard disk. On boot you have 10-seconds to select which kernel to start. There is a kernel for Intel and AMD processors.
The web configuration has the option to set one of the kernels as default.
7) The image will tell you how to access the web configuration and setup a monitoring program like FahMon or HFM.NET. The web
configuration is optional and the folding client can be started from the console if desired.
Install Virtualbox with default options.
Extract the disk image to a location of your choosing and note that location.
Next create a virtual machine.
Enter a name for the virtual machine and select Linux for operating system and Linux 2.6 (64-bit) for version.
Enter the memory amount you would like to allocate to the virtual machine. For bigadv, you will probably want to allocate at least 2-3GB.
From here you will select the extracted disk image. Before you can do that you have to select the yellow folder icon next to the pull-down
menu and add the disk image so that the image is visible to Virtualbox. After doing this, the image can be select in the pull-down menu.
The following four screenshots show how to configure the processor, SATA controller, and network configuration. I prefer to use bridged
for the network configuration to join the virtual machine on the LAN.
From here you can start the virtual machine. The web or console configuration is the same as the native image.
1) Install VMWare Player. You can also try this image with other types of VMware such as server, workstation, or ESXi. At least 8-core
support is required for bigadv support.
2) Download and extract the image. Put the file anywhere you like as long as there is at least 8GB free storage.
3) Startup VMWare Player.
4) Click Open a Virtual Machine on the right-side of the VMware window.
5) Go to the location where you put the image and double click on the Linux64_FAH.vmx file. In you decide to edit the vmx file, make sure to
leave the number of CPUs to at least 8 otherwise you will not be able to get bigadv work. Double click on the name "Linux64_FAH" to start the
virtual machine. The web or console configuration is the same as the native image.
Web and Console Configuration
In the screenshot provided above in the native section you can determine what IP address to go to in a browser to setup the folding
configuration. The console will show you the web IP address to access the configuration page.
Here is a sample image on how to setup the client for bigadv. There are also other options including enabling uni-processor support.
This screenshot should apply to all images.
The following information is for console configuration:
For SMP2 work units, enter the following:
./fah6 -advmethods -smp
For Bigadv work units, at the moment you will have to use Wine and the Windows client:
wine Folding@home-Win32-x86.exe -bigadv -smp
For uni-processor work units, enter the following:
Optionally you can add -advmethods for the uni-processor clients.
When starting the folding client for the first time, you will have to enter some basic information including username, team, and passkey. The
passkey is required to qualify for bonus points for work units that support bonus points including SMP2 and bigadv. I also set packet size to
big when prompted.
For folding monitoring via HFM.net, FahMon, or FahSpy, the log folder location format is as follows:
Change 192.168.0.200 to the IP address assigned to the system. The system will tell you this information on bootup.
This section will cover general folding information and other configuration options.
Bonus point requirements
1) At least 10 Core A3 (SMP2 or Bigadv) work units must be completed before qualifying for bonus points.
2) At least 80% of Core A3 work units must be completed by the preferred deadline.
3) A passkey must be used.
4) One other requirements are met, the bigadv work units must be completed by the preferred deadline.
View original IP configuration information
If you missed the original configuration information including the IP address, FahMon setup, and web configuration address, then you
can run this command to see that information again:
Shutting down or restarting
To shutdown the virtual machine, run this command:
shutdown -h now
To reboot the virtual machine, run this command:
The image supports opening multiple consoles at once (max 6). Simply hit ALT+F2 through F6 and login. Then you can run other commands
while folding at the same time.