Personal computing discussed
Moderators: renee, farmpuma, just brew it!
Flying Fox wrote:IIRC you need to enable a flag in the vmx file. Try this and see if it helps after you enable the BIOS option.
Linux Tip: How to Tell if Your Processor Supports VT
Virtualization Technology (VT) is a set of enhancements to newer processors that improve performance for running a virtual machine by offloading some of the work to the new cpu extensions. Both AMD and Intel have processors that support this technology, but how do you tell if your system can handle it?
It's quite simple: We'll need to take a peek inside the /proc/cpuinfo file and look at the flags section for one of two values, vmx or svm.
* vmx - (intel)
* svm - (amd)
You can use grep to quickly see if either value exists in the file by running the following command:
egrep '(vmx|svm)' /proc/cpuinfo
If your system supports VT, then you'll see vmx or svm in the list of flags. My system has two processors, so there are two separate sections:
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm
VT technology can still be disabled in your computer's BIOS, however, so you'll want to check there to make sure that it hasn't been disabled. The flags in cpuinfo simply mean that your processor supports it.
From my research, VT is required in order to run 64-bit guests under the free VMware server for linux… so it would logically follow that if you can do so, VT is enabled.
32-bit VT is not enabled by default under VMware server. If you want to enable it, you need to add the following line to your *.vmx file for your virtual machine:
monitor_control.vt32 = TRUE
VMware does not recommend that you use VT for 32-bit guests, because they say it will actually hurt performance.
david00214 wrote:Flying Fox wrote:IIRC you need to enable a flag in the vmx file. Try this and see if it helps after you enable the BIOS option.
Uh, wth is egrep? Unix command? How would I run that? I can't even get the VM environment to come up. I am so lost. I think I have to find this flag and enable it somewhere, but they just say the /proc/cpuinfo folder... Uh, what about the stuff before the /proc??? Me. Confused.
monitor_control.vt32 = TRUE
monitor_control.restrict_backdoor = TRUE
Flying Fox wrote:More googling.
Add this one too:Code: Select allmonitor_control.restrict_backdoor = TRUE
Remember to restart the VM. The BIOS option has been enabled right?
david00214 wrote:Flying Fox wrote:More googling.
Add this one too:Code: Select allmonitor_control.restrict_backdoor = TRUE
Remember to restart the VM. The BIOS option has been enabled right?
I restarted the VM, removed and reinstalled the VM, double checked VT is enabled in the BIOS... all that.
kitsura wrote:Watch this space. I might get a dual proc G5 up and running soon.
kitsura wrote:Watch this space. I might get a dual proc G5 up and running soon.
kitsura wrote:v6.20 for some reason can't run on the G5 and keeps crashing immediately. I reverted to version 5 of the software and could only run non-SMP mode. I guess support for the PPC client is really sucky now.
Ttocs wrote:I have no idea what my PPD is, I'd have to do the calculations.
I shut down my PCs at night, as well, so it goes down somewhat.
Unfortunately, I'm having some problem where it thinks my GPU isn't supported on the second client. Strange...
Ttocs wrote:FahMon reports ~1480 per instance, on project 4727.
Turns out, however, that the F@H client doesn't properly detect the second X2 core. That might explain a few things...
I'll probably wind up waiting years for them to fix that, if at all. Unfortunate.
Ttocs wrote:FahMon reports ~1480 per instance, on project 4727.
Turns out, however, that the F@H client doesn't properly detect the second X2 core. That might explain a few things...
I'll probably wind up waiting years for them to fix that, if at all. Unfortunate.
Ttocs wrote:I'll check it out. thanksApparently, a lot of it is discussed starting at about halfway/at the end of page 1 here: http://foldingforum.org/viewtopic.php?f ... &sk=t&sd=a
Ttocs wrote:I ran another GPU2 client on my 4850 to see if it would use the unused processors. (The core speed is OCed) PPD was split between the two. From 1800PPD on 1 client to 900 and 900 PPD on 2 clients. I'm not seeing how I could use the extra processors on 1 core by running multiple clients.I can run two at once and get no slowdown right now (PPD doesn't change when I close one of my clients), because unless it's one of the new "big" workunits, I'm only using about 320 of the 800 stream processors. That's part of the reason why nVidia is beating AMD/ATI on F@H right now - fewer shaders, clocked higher.
41.60l23 wrote:Hey guys,
I quit folding for the summer (my AC couldn't quite keep up with it), but now that it's getting cooler, I'm going to start getting back into the game. I have a few machines to add:
P4 w/ 2600Pro GPU2
Celeron 2.66 w/ Linux Client
X2 5400 @3.0 w/ 8800 GTS (GPU2 client, I guess)
The first two are working fine, and I'll have them up soon. However, the third one (at a different house) is having some problems. Every time I start up the client, it gives the error "Error code 0 - Could not download core". This happens no matter the client I use. I have no firewall software, and the Windows firewall is disabled. As far as I know, there is nothing that should be blocking it on my router, either. Doesn't the client just use port 80 as a HTTP browser would? There's nothing helpful on the Stanford forum.
41.60l23 wrote:If anybody can figure out my problem, I'll be happy to fold on the card under their name for a month.
41.60l23 wrote:This was a solution when it was included with the clients. Unfortunately, none of the new clients have that option, including SMP and GPU2 =(
cd ~/folding/FAH
./fah6 -configonly