• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Quick Notfred VM question...

brokenarrow03

[H]ard|Gawd
Joined
Nov 20, 2007
Messages
1,655
Ok, so recently my Notfred VM's have been looking like the following picture. FAHSpy still shows them putting out good points. About 2300 per VM...

Untitled.jpg


Any help as always is greatly appreciated...
 
yup mine did the same exact thing.. i have no clue what caused it.. hopefully some one does..
 
So yours are still working as well? Wierd


no actually it kept locking up on me and not reporting data back and i lost over 15k points during the CC.. because no one bothered to tell anyone that they should use the beta client.. so i was using the borked older client that was linked in the VMplayer guide.. so i quit running the cpu client and went back to boinc..
 
Mine does tha same thing and still does good production. It almost appears that it is trying to access memory addresses beyond what it actually has available to it.
 
no actually it kept locking up on me and not reporting data back and i lost over 15k points during the CC.. because no one bothered to tell anyone that they should use the beta client.. so i was using the borked older client that was linked in the VMplayer guide.. so i quit running the cpu client and went back to boinc..

Which older client were you using? VMWare or notfred?



The "Attempt to access.." error can sometimes cause a VM instance to fail if you restart it. A lot of times it will just continue to chug along even with the errors.

Sorry, I'm not as active on the forum right now as my current consulting client blocks a lot of websites while we are onsite during the day.
 
I get weird stuff like that running VM workstation 6.5 and notFred. Still getting production though.
 
Per notfred - http://techreport.com/forums/viewtopic.php?f=9&t=63960
Re: Notfred - attempt to access beyond end of device
posted on Mon Jan 12, 2009 8:30 pm

Don't worry about /proc, it's not a real directory and the only directory that is actually on the drive is /hda and that only contains stuff when the backup script is running (it is unmounted the rest of the time). Some other people have reported this in the past and I'm a bit suspicious about my disk image and the partitioning on it. Unfortunately I'm having a few difficulties in other areas right now (having problems building with a new compiler) so there isn't anything I can really recommend, but it is on my list of things to look at.

So, that error will not hurt production or performance in any way of the SMP client.
 
lol .. I have been running the iso version on my fileserver for almost 2 months now without a reboot or problem .... so "don't worry" is okay with me ...:cool:

In the case of a folding CD sure, but knowing what /proc is and what you can do to a running system through it, that statement made me cringe.
 
one of mine is doing that, still putting out like a good little whore tho
 
Ok, to build a little on this. My Task Manager shows that only 2 cores are at 100%, shouldnt all 4 be up at 100%?
 
all 4 should be at 100% (they will actually fluctuate between 95 and 100).

If one of them is at 0, then it is probable that one of the VMs is "dead". You can take a look at the VMWare Console to see if there are any error messages. Sometimes it is easier to create a new VM to replace the new one rather than screw around trying to figure out "why" it is broke.
 
Ok, so yea a quick reboot of the VM and it is off and running again. All cores report 100% now

wierd
 
Back
Top