Message boards : Questions and problems : Can't get virtual work.
Message board moderation
Author | Message |
---|---|
Send message Joined: 28 Aug 19 Posts: 50 |
Can't get virtual work for Rosset or LHC. All I get is 0 New Tasks. I checked they both got task ready to send and I have both to get all work units. I suspend all other tasks just to have BOINC get Virtual work. The hard pat is I get no message from Event Log on why I can't get Virtual work. I got Mint to run on VirtualBox. 2/3/2024 7:34:47 PM | | Starting BOINC client version 7.24.1 for windows_x86_64 |
Send message Joined: 19 Feb 16 Posts: 85 |
Just to clarify, this is Rubning Mint within VirtualBox, and trying to get work from within that instance? Or is this something else? https://boinc.berkeley.edu/dl/ |
Send message Joined: 28 Jun 10 Posts: 2709 |
Just to eliminate it from possibilities, how much memory have you allowed BOINC to use? |
Send message Joined: 28 Aug 19 Posts: 50 |
Just to clarify, this is Rubning Mint within VirtualBox, and trying to get work from within that instance? Or is this something else? Yes, Mint is running within VirtualBox. Software: BOINC v7.24.1 Win 11 Pro, Video Drivers v551.76, CUDA v12.4, V-Box v7.0.6 Hardware: ASRock B650E - AMD Ryzen 7 7700X 8 core - 32GB RAM, EVGA GTX 1080Ti 11GBs, GTX 980 4GBs, 512GB M.2 for BOINC Program and 3TB HD for Data |
Send message Joined: 28 Aug 19 Posts: 50 |
Just to eliminate it from possibilities, how much memory have you allowed BOINC to use? 32 Gigs. Software: BOINC v7.24.1 Win 11 Pro, Video Drivers v551.76, CUDA v12.4, V-Box v7.0.6 Hardware: ASRock B650E - AMD Ryzen 7 7700X 8 core - 32GB RAM, EVGA GTX 1080Ti 11GBs, GTX 980 4GBs, 512GB M.2 for BOINC Program and 3TB HD for Data |
Send message Joined: 18 Feb 20 Posts: 21 |
You have to install and configure cvmfs and install runc. Then tick Run native if available in lhcathome settings. https://lhcathome.cern.ch/lhcathome/prefs.php?subset=project |
Send message Joined: 28 Jun 10 Posts: 2709 |
For LHC VBox tasks to work, I also had to change something in the bios. I can't remember exactly what off hand. It was in addition to allowing virtualisation. |
Send message Joined: 28 Aug 19 Posts: 50 |
Well if you don't know what it is then I have no idea. The LHC FAQ says nothing about it that I can fine. Just the AMD-V. Software: BOINC v7.24.1 Win 11 Pro, Video Drivers v551.76, CUDA v12.4, V-Box v7.0.6 Hardware: ASRock B650E - AMD Ryzen 7 7700X 8 core - 32GB RAM, EVGA GTX 1080Ti 11GBs, GTX 980 4GBs, 512GB M.2 for BOINC Program and 3TB HD for Data |
Send message Joined: 17 Nov 16 Posts: 890 |
For LHC VBox tasks to work, I also had to change something in the bios. I can't remember exactly what off hand. It was in addition to allowing virtualisation. From Google AI answer you also need to enable IOMMU in the UEFI along with virtualization to get Oracle VM Virtual Box to work. Yes, you need to enable IOMMU and virtualization extensions to enable PCI passthrough in Oracle VM VirtualBox. |
Send message Joined: 28 Aug 19 Posts: 50 |
You have to install and configure cvmfs and install runc. Not installing anything if LHC didn't install itself. And I don't know what your talking about? And it's not in the FAQ for any cvmfs. I'm using V-BOX 7.0.6 which is bundled with BOINC 7.24.1. Running Windows 11. With AMD-V enabled. V-Box is running other OS just fine. Software: BOINC v7.24.1 Win 11 Pro, Video Drivers v551.76, CUDA v12.4, V-Box v7.0.6 Hardware: ASRock B650E - AMD Ryzen 7 7700X 8 core - 32GB RAM, EVGA GTX 1080Ti 11GBs, GTX 980 4GBs, 512GB M.2 for BOINC Program and 3TB HD for Data |
Send message Joined: 28 Aug 19 Posts: 50 |
From Google AI answer you also need to enable IOMMU in the UEFI along with virtualization to get Oracle VM Virtual Box to work. Ok I'll check it out. Software: BOINC v7.24.1 Win 11 Pro, Video Drivers v551.76, CUDA v12.4, V-Box v7.0.6 Hardware: ASRock B650E - AMD Ryzen 7 7700X 8 core - 32GB RAM, EVGA GTX 1080Ti 11GBs, GTX 980 4GBs, 512GB M.2 for BOINC Program and 3TB HD for Data |
Send message Joined: 28 Aug 19 Posts: 50 |
From Google AI answer you also need to enable IOMMU in the UEFI along with virtualization to get Oracle VM Virtual Box to work. IOMMU is set to auto. I'm setting not to get work except for LHC AND wait. I've did get work for LHC SSE2 and AVX. Software: BOINC v7.24.1 Win 11 Pro, Video Drivers v551.76, CUDA v12.4, V-Box v7.0.6 Hardware: ASRock B650E - AMD Ryzen 7 7700X 8 core - 32GB RAM, EVGA GTX 1080Ti 11GBs, GTX 980 4GBs, 512GB M.2 for BOINC Program and 3TB HD for Data |
Send message Joined: 2 Feb 22 Posts: 84 |
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 |
Copyright © 2024 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.