Untuk yang mau cobain nggiling make vmware (dengan catatan smp folding native tetep jalan) yang bertujuan untuk naikin ppd silakan nyobain make vmware.
Sebelumnya, kudu dicek dulu apakah prosesor kita support buat ngejalanin vmware, karena selain 64 bit system, fitur lain yang dipake adalah virtualisasi, biasanya kalo di intel ada kode VT gitu lah...kalo ada berarti bisa.
ato bisa di find out make tool ini dari sini:
http://download3.vmware.com/software....5.0-18463.exe
kalo bisa, silakan lanjut (kita make os windows dan vmware akan dipasangin linux ubuntu 7.04 64 bit)
1. donlot vmware server for windows dari sini: http://register.vmware.com/content/download.html
2. jangan lupa milih ini : "Register for your free serial number(s) to start using VMware Server." atau kalau setok aku masih banyak silakan pm, nanti aku kasih sn nya
3. kalo udah selesai donlot, jalankan installer nya seperti langkah langkah normal nginstal aplikasi di winblows lah...next next aja...
Yang perlu diperhatikan waktu buat New Virtual Machine:
1. pilih jumlah prosesor: 2
2. jenis hd udah di pilihkan scsi
3. ram besarnya kalau bisa setengah dari ram pc kita yang dialokasikan ke vmware
4. network pilih bridged aja
5. besar hd 8g default sudah cukup
nah itu yang paling utama sih, lainnya standar aja sesuai keinginan...
Dengan asumsi ubuntu sudah terinstal di vmware, lanjut ke instalasi smp folding nya....
Buka terminal, ada di Application >Accesories> Terminal, drag aja ke desktop:
setelah terminal di jalankan, silakan ketik perintah yang aku tebelin ya, diakhir dengan enter pastinya
sudo -s
(masukkan password user, karena shadow password jadi apa yang kita ketik nggak keliatan ya)
sudo passwd root
(ketik password user 2 kali untuk ganti password root nya)
sudo apt-get update
sudo apt-get install ia32-libs
sudo wget -c http://www.vendomar.ee/~ivo/finstall
sudo chmod +x finstall
./finstall smp
ikuti dan jawab aja sesuai keinginan kalau ada pertanyaan
nah akhirnya masuk ke folding inti nya nih:
sekarang di seting biar folding otomatis begitu ubuntu nya nyala, kita set sebagai service, lokasi installer nya ada di:
/home/user_name/foldingathome/
./installService
jalankan folding nya dengan perintah:
./folding start
kalo semua lancar jaya nggak ada error seperti di ss berarti udah ok, terminal boleh di tutup.
Tinggal kita sekali sekali ngintip FAHlog nya aja buat ngecek progress hehehe....sengaja nggak dipakein monitoring tools, karena udah cukup dari log lagian biar nggak berat aja ubuntu nya....contoh monitoring yang jalan bagus misalnya FAHmon atau conky juga bisa.
Kita bisa liat FAHlog.txt di dalam folder:
/home/user_name?foldingathome/CPU1/
nah ini ditinggal ngetik tips udah dapet segini, not bad kan?
yah, dipake atau tidak ini sekedar share aja, yang jelas 1 id sekarang udah bisa jalankan 2 instances smp dengan bantuan vmware, bisa diduga ppd nya kan?
mudahan bermanfaat ya...let's share then...
Nice tips also dari bro andre....silakan dipilih mana yang sesuai, demi 38608!
ini gw temukan very easy and simple guide nya Vmware+Ubuntu64bit... dijamin lebih cepat 1 - 2 menit time per framenya dibanding di windows.
Quote:
The easy Linux SMP client Install guide for both Linux and Windows XP
The carrot: The SMP client rules in points per day and is a major boost in the speed of the research! On average the PPD for a system more than doubles when using this client! This is in part due to the efficient optimized 64bit multi-tasking client working in an OS that is well suited for this work. This results in the work completed a lot faster than the standard client, and a fair bit faster than the Windows SMP client!
This SMP client requires a 64bit capable CPUs with 2 cores (or more) or 2 CPUs (or more). For dual core systems that can't run this client, consider the Windows SMP client - download & instructions at http://folding.stanford.edu/download.html
The Linux SMP client can be run under Windows XP (any) using VMware Server (free) or directly with a 64 bit version of Linux.
Windows XP or Vista (and perhaps W2K): If using Windows, will need to install VMware Server (available for free) so to run a virtual OS within Windows as the SMP client requires 64bit Linux. Due to VMware limitations, this works only with AMD X2s, Opterons (dual core) and with Intel CPUs that have 64bit & VT (unlike AMD CPUs that don't need VT) - what works are the C2D 6300 and higher (not C2D 4xxx series or lower), C2D T5600 and higher (not the T5500 and lower). Pentium D and 4 are not recommended as for some WUs it won't be able to complete some projects (e.g. 2605). Some multi CPU configuration will work (e.g. dual Opteron CPUs Revision E or later). To verify if the CPU will work, run the VMware "Processor Check for 64-Bit Compatibility" available at http://www.vmware.com/download/ws/drivers_tools.html
Note running a virtual OS causes the SMP client to run about 20% slower (much worse for Pentium 4/D). It will also take about 500MB of RAM and 5GB of hard disk space.
For those running 64 bit Linux natively, skip the instructions relating to the VMware. Note that Pentium D and very fast Pentium 4s (HT enabled) (those with 64bit and VT) CAN run this client fairly quickly using Linux natively. It is suspected there is a bug with VMware that they perform so poorly under vmware, so if using Windows with those CPUs, then the Windows SMP client is the only SMP choice (don't need 64bit nor VT for that client).
1. Download VMware Server for Windows
http://www.vmware.com/download/server/ (just need the .exe file) and get a serial number (after filling out the registration)
Currently it is version 1.04
2. Install VMware Server
Go with the default options (if you want). Ignore the warnings regarding that not using Windows Server and that don't have IIS installed.
3. Download Ubuntu Linux
Click the following link and then select "Other installation options" and take the "64-bit PC (AMD64) desktop CD" both 6.10 and 7.04 tested as working (might as well use the latest) http://www.ubuntu.com/products/GetUb...currentrelease
Note that this version also works with Intel CPUs with 64bit and VT.
For Intel CPU, enable virtualisation/64bit in the BIOS if those option is available.
4. Burn the Ubuntu ISO image to a CD. If running under VMware, this step can be skipped if don't want to burn a CD.
5. Start VMware. Select "New Virtual Machine". Pick custom virtual machine configuration, then for Guest OS, select "Linux" option and pick "Ubuntu 64 bit" from the list. In general select default options, but make sure that select 2 processors, at least 400MB of RAM (500MB suggest in case the WUs get larger) and either Bridged (suggested) or NAT (if bridged doesn't work) for network type. For HD space, 4GB is minimum suggested with all space allocated but if plan to play with Linux, make it larger (and if want, can select to not allocate all space now). HD space isn't changeable, but RAM, network, CD (among other settings) are changeable.
6. If running VMware, and have burned the CD then put the Ubuntu CD in, wait until the CD light goes off.
If didn't burn the CD, then go to "Edit virtual machine settings" -> Hardware tab -> select CD-ROM -> Connection group -> Use ISO image and browse to where the ISO image was downloaded (in step 3).
In either case, then select "Start Virtual Machine" - and it should boot Ubuntu.
Note that when in a Virtual OS, to get out at any time, just press Ctrl-Alt
7. Install Ubuntu - can use the default settings. It will reboot when finished so make sure you take out the CD. With Ubuntu ver 7 (e.g. 7.04) it will pause and ask to remove the disk then press enter. In VMware, select VM->Removable Devices->CD ROM->Edit and unclick "Connected" and "Connect at power on". Otherwise if it is set to use upon bootup (default) - it will ask if you want to install packages from it (answer no).
8. After it rebooted, verify with Firefox browser that it can access the network. Then open a Terminal (click on Applications on top and go into Accessories and click on Terminal - note, if right click on Terminal, it offers the option to add it to the top menu panel).
Then type the following:
sudo apt-get install ia32-libs
(answer yes to it's request for disk space)
9. Install the SMP folding client by typing the following:
mkdir -p ~/folding/FAH
cd ~/folding/FAH
wget http://www.stanford.edu/group/pandeg...eta1-Linux.tgz
tar xzvf FAH6.00beta1-Linux.tgz
10. Configure it. Note that this client works fairly similar to the console client.
cd ~/folding/FAH
./fah6 -configonly
This is similar to the standard console configuration (the team is 2630)
http://www.techreport.com/etc/folding/. However answer big for "Acceptable size of work units". I don't suggest to accept advanced work units unless monitoring it carefully. And if run into timing problems with an AMD CPU, can set ignore deadline information.
11. Run it by typing
cd ~/folding/FAH
./fah6 -forceasm -smp -verbosity 9 (and any other parameters desired)
It should download the SMP Gromacs core and then a work unit (WU).
Note to stop it, just hit Ctrl-C. It will take up to a minute before all 4 threads are shut down, so don't restart the client before then!
12. To create an easy script to start this, type the following
cd ~
nano startfah
This opens a simple edit program. Type the following
cd ~/folding/FAH
./fah6 -forceasm -smp -verbosity 9
Save the script by pressing CTRL-X and then answering Y to the editor's prompt.
Finally, at the command prompt type
chmod +x startfah
Now when open the terminal, just type ./startfah and it will start SMP folding with the usual parameters.
Note if want different parameters (e.g. for -oneunit or reconfigure the client), then the original method applies (see step 11).
13. In VMware, the X2s and Opterons have an issue with clock timings that can cause the SMP client to run slower than it should (due to sync problems). AMD has a patch for that called AMD Dual-Core Optimizer http://www.amd.com/us-en/Processors/..._13118,00.html
14. When planning to reboot or want the client to shutdown quickly (e.g. need the memory), can use Power->Suspend. When want it back running, just select Power->Resume. This is very fast!
15. Once folding is launched, there is no need to keep the VMware Server console running (it takes 24MB). If close the VMware Server console, the guest OS will keep running. Nice stealth mode! And when reopening the console - there it is - still running!
Notes
- The computer needs to be on most of the time to be able to make the tight deadlines. It is the preferred deadlines that must be considered as although will still get points for completing within the final deadline, the WU will be reissued if can't complete before the final deadline. For deadlines, see the project list at http://fah-web.stanford.edu/psummary.html
- The SMP client currently often doesn't use 100% of the CPU (can see as low as 80% use). Some people also run a regular folding client (or two) to take advantage of remaining idle CPU cycles. However with recent projects (e.g. 2608/2609) that often use 95%, this will have a noticeable impact on the SMP client.
-As the SMP client is still in beta, keep an eye on the log file and expect to update the client every few months until officially released. Also there are times that there is no work to do (get assigned to 0.0.0.0 for a few hours).
- The SMP client can run with up to 4 cores. However if running under VMware Server, only 2 cores are available per guest OS. Not sure with a VT capable CPU that can run two 64bit guest OSes (untested) If it does, can run 2 VMware guest OSes, otherwise can run the Windows SMP client )or GPU client or regular client, etc.).
- If want to play with Linux, consider installing the VMware tools (VM->Install VMware Tools)
- If experiencing lags in other apps, then in VMware server select Host->Setting->Priority->Input Ungrabbed to Low priority. Also in taskmgr, change the vmware-vmx.exe to below normal priority (and if necessary, set it to low).
- Can change the resolution to 800x600 if it takes too much space (or don't like the scroll bars) System (from toolbar at top)-> Preferences -> Screen Resolution
- Can change the Linux screen saver to none if desired (System->Preferences->ScreenSaver)
- If want to play with Linux, check out the HardOCP article http://consumer.hardocp.com/article....xoY29uc3VtZXI= and page 4 of the thread from the article.
Source: http://techreport.com/forums/viewtopic.php?t=47827
Update: 02 April 2009: sumber asli http://communities.vmware.com/docs/DOC-8978
Verifying that VT is Enabled and Locked at Boot
On Intel CPUs, it is expected that the BIOS (or other firmware) will either enable or disable VT at boot, and will then lock the setting so that it cannot be subsequently changed without powering down the CPU. Note that VT must be both enabled and locked before software can make use of the VMX extensions. This operation must be performed for each core of a multi-core system, and for each thread of a multi-threaded system.
Because the VT setting is typically locked at power on, it is necessary to fully power down the system after changing any VT options in the BIOS. A simple reboot is not sufficient! I recommend that you actually pull the power cord(s) out of the wall and wait ten seconds after saving your BIOS changes.
Some BIOSes do not have VT enable/disable options. Some BIOSes with such an option fail to enable/disable VT on each core of a multi-core system or on each thread of a multi-threaded system. To verify that VT is enabled and locked on each core/thread of your system, download the attached ISO, burn it to a CD, and boot your host from the CD.
If the ISO reports that VT is unlocked on one or more threads/cores, a workaround is available for current VMware hosted products. Simply add the following option to your system-wide configuration file:
On Linux systems, the system-wide configuration file is /etc/vmware/config. On Windows systems, the system-wide configuration file varies according to VMware product and Windows version. For VMware Workstation on XP hosts, the system-wide configuration file is C:\Documents and Settings\All Users\Application Data\VMware\VMware Workstation\config.ini. For VMware Workstation on Vista hosts, the system-wide configuration file is C:\ ProgramData\VMware\VMware Workstation\config.ini. For other VMware products, adjust the path appropriately.hv.enableIfUnlocked = TRUE
Note that this workaround can also be helpful if your BIOS fails to enable and lock VT when waking from hibernation. However, the ISO is not helpful in diagnosing this failure. If VT works after a power-cycle but fails after resuming from hibernation, then you should try the above workaround.
If your BIOS specifically disables VT and locks it in that state, then it is impossible to subsequently enable VT through software. Your only hope is that your BIOS may fail to lock the VT setting when waking from hibernation, in which case the above workaround can help, but only after hibernating the system. Aside from that, your only recourse is to complain to the system vendor.

















Reply With Quote












Bookmarks