Re: [boinc_dev] Typo in computer detail, but only at E@H

2015-10-16 Thread Jord van der Elst
It's not a very recent problem, and it can even be worse: 'Stepnnng9'. Various BOINC projects shows it happened on hosts with last contacts as far back as 2013. http://primaboinca.com/top_hosts.php?sort_by=expavg_credit=880 http://boinc.med.usherbrooke.ca/nrg/hosts_user.php?sort=os=1_all=1=1209

Re: [boinc_dev] vbox64 and virtualization

2015-10-16 Thread Marius Millea
Thanks for the explanation Rom, thats helpful. However I'm using VBox 4.3.30 and vboxwrapper 26175 so I don't think that's it. I'm attaching my vbox.log, there's some errors in there about VT-x but searching for ERR_CPU_VM_EXTENSIONS_DISABLED yields nothing. Marius On Fri, Oct 16, 2015 at 1:55

Re: [boinc_dev] vbox64 and virtualization

2015-10-16 Thread Christian Beer
On 10/16/2015 11:16 AM, Marius Millea wrote: > However I'm using VBox > 4.3.30 and vboxwrapper 26175 so I don't think that's it. I'm attaching my > vbox.log, there's some errors in there about VT-x but searching > for ERR_CPU_VM_EXTENSIONS_DISABLED yields nothing. The vbox.log contains

Re: [boinc_dev] vbox64 and virtualization

2015-10-16 Thread Marius Millea
Thanks Christian, I added that option but same result. Its clear to me now that vboxwrapper is missing the fact that the VM doesn't start correctly. If you look at the attached stderr.txt, if says "Successfully started VM." Hence it never makes it to the part in the code that checks vbox.log for

Re: [boinc_dev] Fwd: New Defects reported by Coverity Scan for BOINC/boinc

2015-10-16 Thread McLeod, John
Coverity is a tool that uncovers security problems. You should investigate each one, and most of them will need a fix. Sent from my Android phone using TouchDown (www.nitrodesk.com) -Original Message- From: David Anderson [da...@ssl.berkeley.edu] Received: Tuesday, 13 Oct 2015, 6:49PM

Re: [boinc_dev] vbox64 and virtualization

2015-10-16 Thread Marius Millea
On Fri, Oct 16, 2015 at 2:23 PM, Marius Millea wrote: > Here's the relevant lines from the scheduler log, vmx is there, and its > present in /proc/cpuinfo as well. > > 2015-10-16 12:12:34.6279 [PID=66 ][send] CPU features: fpu vme de > pse tsc msr pae mce cx8 apic sep

Re: [boinc_dev] vbox64 and virtualization

2015-10-16 Thread Christian Beer
Did you restart the server processes just to make sure? The scheduler should use the new plan_class.xml config instantly and not send you any work. This seems to be a separate problem. So in theory the server shouldn't send you any task but it is. And the vboxwrapper should recognize the error

Re: [boinc_dev] vbox64 and virtualization

2015-10-16 Thread Marius Millea
On Fri, Oct 16, 2015 at 2:23 PM, Marius Millea wrote: > Here's the relevant lines from the scheduler log, vmx is there, and its > present in /proc/cpuinfo as well. > > 2015-10-16 12:12:34.6279 [PID=66 ][send] CPU features: fpu vme de > pse tsc msr pae mce cx8 apic sep

Re: [boinc_dev] vbox64 and virtualization

2015-10-16 Thread Rom Walton
> Yea, can confirm "VBoxManage startvm" returns successfully on my system even > though the VM immediately > dies with the VERR_VMX_MSR_VMXON_DISABLED error. That's why vboxwrapper never > catches it. Not sure if > this is a VBox bug and/or if its limited to my system. Well, it is a bug in

[boinc_dev] Suggestion for a RPC for reporting invalid (and other status) tasks

2015-10-16 Thread AgentB
Hi devs My first post -so thanks for making boinc, it really works well! Apologies for the long post, the formatting should be fixed format. - appreciate any comments or thoughts. BR Mike Summary: Suggestion for a RPC for reporting invalid (and other status) tasks This proposal started

Re: [boinc_dev] Typo in computer detail, but only at E@H

2015-10-16 Thread David Anderson
That string comes from the client; I'm not sure why E@h would show it incorrectly. -- David On 10/16/2015 6:27 AM, TarotApprentice wrote: On Einstein I have a bunch of computers that show as: GenuineIntel Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz [Family 6 Model 58 Stepinng9]](8 processors)