| Info | Message |
|---|---|
| 1) Message boards : Projects : News on Project Outages
Message 115221 Posted 2 days ago by computezrmle |
They fixed it this morning. |
| 2) Message boards : Projects : News on Project Outages
Message 115171 Posted 11 days ago by computezrmle |
In reply to computezrmle's message of 6 Jan 2025:... As confirmed by one of the scientists LHC@home sends out work for CMS again: https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=6265&postid=51359 |
| 3) Message boards : Projects : News on Project Outages
Message 115156 Posted 12 days ago by computezrmle |
In reply to Contact's message of 4 Jan 2025:LHC@home has work ... Not really. LHC@home doesn't send any scientific work atm: - SixTrack: now work for many months - Theory Simulation: very few long running resends every now and then - ATLAS Simulation: few batches of work every now and then - CMS Simulation: empty VM tasks that all fail after less than 1/2 h due to broken connections to backend systems (not a BOINC issue!) Please set CMS to "no new tasks" and follow their forum to get out when the issues are solved. |
| 4) Message boards : Questions and problems : CPU does not have hardware virtualization support
Message 114852 Posted 14 Nov 2024 by computezrmle |
This is what I got from an LHC@home volunteer who successfully runs VirtualBox VMs on Windows:HyperVisorPresent : False HyperVRequirementDataExecutionPreventionAvailable : True HyperVRequirementSecondLevelAddressTranslation : True HyperVRequirementVirtualizationFirmwareEnabled : True HyperVRequirementVMMonitorModeExtensions : True Your output suggests that you may still have left Hyper-V components active and/or SVM is not enabled in the BIOS: HyperVisorPresent : True HyperVRequirementVirtualizationFirmwareEnabled : Your board (X870E AORUS ELITE WIFI7) and your CPU (AMD Ryzen 9 9950X) are known to support SVM. The relevant BIOS entry that must be enabled is usually located here: Advanced Frequency Settings -> Advanced CPU Settings -> SVM Mode Don't mix this with other settings that look similar, e.g. SMT Mode. |
| 5) Message boards : Questions and problems : CPU does not have hardware virtualization support
Message 114845 Posted 13 Nov 2024 by computezrmle |
Open a Powershell window, run the following command and post it's output:Get-ComputerInfo -property "HyperV*" |
| 6) Message boards : Questions and problems : CPU does not have hardware virtualization support
Message 114836 Posted 11 Nov 2024 by computezrmle |
The issue is neither caused by BOINC nor by any of it's projects. It is caused either by a BIOS setting being disabled or by a conflict between Hyper-V and VirtualBox. The BIOS setting you need to enable is called VT-x on Intel based systems or AMD-V/SVM on AMD based systems. Without that none of the steps below will solve the issue. In addition you must ensure that Hyper-V does not conflict with your VirtualBox version. Best would be to completely disable all Hyper-V/Sandbox/WSL features in Windows and run: bcdedit /set hypervisorlaunchtype off In addition you must disable: Windows Security -> Device Security -> Core isolation -> Memory Integrity and you may need to disable certain other Windows features as explained here: https://learn.microsoft.com/en-us/troubleshoot/windows-client/application-management/virtualization-apps-not-work-with-hyper-v Then reboot, contact a BOINC project (e.g. LHC@home) and check your computer details page there. A wrong/incomplete configuration is reported like this and you will not get any vbox64 task: Virtualbox (a.b.c) installed, CPU does not have hardware virtualization support This must change to: Virtualbox (a.b.c) installed, CPU has hardware virtualization support and it is enabled Be aware that BIOS updates usually disable the settings mentioned above and Windows updates may reenable Hyper-V or related settings. |
| 7) Message boards : BOINC client : 8.1.0 Not able to start a client.
Message 113803 Posted 21 Mar 2024 by computezrmle |
Just a quick look at the master source used for boinc-client.service. There's this line: ProtectHome=true Didn't test it yet but you may try to use: ProtectHome=false Then run "sudo systemctl daemon-reload" and restart the client. |
| 8) Message boards : Questions and problems : BOINC seems to tell any V-Box project not to run on this machine.
Message 113801 Posted 21 Mar 2024 by computezrmle |
Of course you can test it, even without getting a task. This is your computer at LHC@home: https://lhcathome.cern.ch/lhcathome/show_host_detail.php?hostid=10835631 It states: Virtualbox (7.0.6) installed, CPU does not have hardware virtualization support Now change your local configuration, step by step according to each advice you have been given, reboot, start BOINC and connect to the project (once). Then check again the computer details page. as long as the statement from above remains unchanged (and I don't mean the VirtualBox version) the project will not send any VBox tasks. This makes sense since you (your computer) tells the project you are not able to run those tasks. So why should they waste them and send any? And yes, you have been told that a couple of times (see LHC@home) but it looks like you ignore every advice. Hint. On the computer details page you must find something like this: Virtualbox (7.0.14) installed, CPU has hardware virtualization support and it is enabled |
| 9) Message boards : Questions and problems : lost team points on march 13th
Message 113791 Posted 19 Mar 2024 by computezrmle |
LHC@home was fine. It was LHC@home-dev that temporarily got all credits from LHC@home. Boincstats corrected this last week. |
| 10) Message boards : Questions and problems : BOINC seems to tell any V-Box project not to run on this machine.
Message 113773 Posted 16 Mar 2024 by computezrmle |
Add #5. Another possible reason if you run BOINC inside a VirtualBox guest. To forward hardware virtualization to the guest this option must be ticked in the VirtualBox GUI: System -> Processor -> Enable Nested VT-x/AMD-V |
| 11) Message boards : Questions and problems : BOINC seems to tell any V-Box project not to run on this machine.
Message 113771 Posted 15 Mar 2024 by computezrmle |
This is what the VirtualBox manual explains regarding hardware virtualization in section 10.3: "Oracle VM VirtualBox's 64-bit guest and multiprocessing (SMP) support both require hardware virtualization to be enabled." Rosetta and LHC@home both send out vbox64 applications, which means their guests are 64-bit. LHC@home even sends out a multiprocessing application (ATLAS). Both don't send vbox tasks to a computer that reports hardware virtualization is disabled, like your computer at LHC@home does: "Virtualbox (7.0.6) installed, CPU does not have hardware virtualization support" Things you will have to do 1. Ensure SVM/AMD-V is enabled in the computer's BIOS 2. Ensure other hypervisors don't conflict with VirtualBox. Best would be to disable them if they are not required elsewhere. This mainly applies to Hyper-V which can be disabled running this command as admin: bcdedit /set hypervisorlaunchtype off Then reboot. Be aware that WSL uses certain Hyper-V components. Your logs show that you use WSL, hence Hyper-V is not completely disabled. 3. Ensure "<p_vm_extensions_disabled>" is set to "0" in BOINC's client_state.xml. Detailed instructions can be found here. 4. In your Windows Defender Security Center disable "Memory integrity" as it also conflicts with VirtualBox's hardware virtualization. |
| 12) Message boards : Questions and problems : Can't get virtual work.
Message 113666 Posted 23 Feb 2024 by computezrmle |
Just checked your computer details page at LHC@home. It states this: Virtualbox (7.0.6) installed, CPU does not have hardware virtualization support Since your BOINC client just reports what it gets from the BIOS/OS you have to ensure your BIOS/OS options are correctly set. Otherwise you will never get any vbox tasks. Most common reason: AMD-V (on an AMD platform) is disabled in the BIOS (on Intel it would be VT-x). This must be enabled. Carefully read your BIOS documentation since some manufacturers may use slightly different names or use more than just 1 switch. Next common reason: On Windows Hyper-V might be enabled. Hyper-V is a type-1-hypervisor started before any hyper-2-hypervisor like VirtualBox. Hence, all computer resources already allocated by Hyper-V are no longer available for other hypervisors. Ensure Hyper-V and all related components, e.g. WSL, are fully disabled or uninstalled. Be aware that Windows updates may reenable Hyper-V. You may use this command as admin, then reboot: bcdedit /set hypervisorlaunchtype off Next common reason: On Windows 11 "Memory integrity" must be switched off. Other reasons, e.g. virus scanner issues ..., are mentioned in a checklist at the LHC@home forum as well as in many other comments there. As for IOMMU Shouldn't be included any more in recent VirtualBox versions as mentioned here: https://forums.virtualbox.org/viewtopic.php?t=99396 |
| 13) Message boards : Questions and problems : Runninb BOINC on a Win 11 laptop
Message 113289 Posted 16 Dec 2023 by computezrmle |
This will not necessarily put less load on the cooling system. Unlike (very) old CPUs modern ones can be limited by power usage and/or CPU temperature. The same power usage/temperature can be reached with few cores running at a high frequency or more/all cores running at a lower frequency. The cooling system must be able to deal with max limits. If not this would be a design issue. Example: Recent AMDs typically throttle when 95 °C is reached. This limit can be set to 85 °C or even 75 °C via the BIOS. |
| 14) Message boards : Questions and problems : "Computing suspended because processor usage is high"
Message 113248 Posted 10 Dec 2023 by computezrmle |
Someone else will have to answer the problem with not getting a notification. Don't have a clue on that. @Richard Mitnick Please check your settings on this page: https://boinc.berkeley.edu/edit_forum_preferences_form.php Notifications -> Immediately, by email If you changed anything click "Update" close to the bottom of the page. Also on this page: https://boinc.berkeley.edu/edit_email_form.php Did you enter the correct email address? If you still don't get any email, try "Notifications -> On my Account page (no email)" on the forum preferences page. |
| 15) Message boards : Questions and problems : Your processor does not support the required instruction set.
Message 113194 Posted 29 Nov 2023 by computezrmle |
The task will automatically restart after the end of the 86400 s break. It will also restart after a BOINC client restart (if no other task has a higher priority). Ralph uses vboxwrapper 26202, right? That (Windows-)version is built against Microsoft's .com interface which is known to occasionally show the postpone issue. Recent vboxwrapper versions do not use the .com interface any more. Hence, the project developers should be asked to use the most recent vboxwrapper (currently 26206): https://boinc.berkeley.edu/dl/ |
| 16) Message boards : Questions and problems : Can the "slots" folder in the Data directory be located on a seperate drive?
Message 112578 Posted 23 Aug 2023 by computezrmle |
You can use /slots/ as mountpoint. That way the data can be sent to another drive/partition/folder, e.g. tmpfs or zram on Linux or a ramdisk on Windows. It is a different question whether this is useful or not. |
| 17) Message boards : Projects : CPDN server cert expired
Message 112499 Posted 7 Aug 2023 by computezrmle |
The server certificate for www.cpdn.org expired Mon, 07 Aug 2023 10:02:42 UTC. Needs to be replaced by a new one. |
| 18) Message boards : BOINC Manager : Boinc won't start on Linux Mint
Message 112455 Posted 5 Aug 2023 by computezrmle |
Your computers don't meet some essential requirements to run VirtualBox tasks. See an extended answer here: https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=6023&postid=48343 |
| 19) Message boards : BOINC client : Add Max concurent downloads and uploads setting under Computing Prefs -> network
Message 112440 Posted 3 Aug 2023 by computezrmle |
See: https://boinc.berkeley.edu/wiki/Client_configuration You may try to adjust the following options in cc_config.xml. <max_file_xfers>N</max_file_xfers>
Maximum number of simultaneous file transfers (default 8).
<max_file_xfers_per_project>N</max_file_xfers_per_project>
Maximum number of simultaneous file transfers per project (default 2).This is a per client setting. With the default values a single client should not be able to make a 1 Gbit connection unusable. Since you mention a "farm" and WIFI beside wired connections you may have lots of clients on many computers. To get an impression: How many of each? |
| 20) Message boards : Questions and problems : Taska have estimated remaining over 8 years, deadline in the past -- is something wrong?
Message 112215 Posted 30 Jun 2023 by computezrmle |
Looks like none of the following projects has a user account "David Pickett": Asteroids@home LHC@Home MilkyWay@home Rosetta@Home Are you sure you are correctly connected? Are you connected via an account manager using their account? |
Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.