LHC@home

Hi
Cant seem to get any LHC@ home projects to work, first I get a waiting for network access so I suspended my Rosetta projects. The LHC starts then a few seconds later I get computational errors. No idea where to go with this, any advice would be helpful.

thanks

Welcome Roger,
you have to allow us to see your Computer.
In the prefs of lhc@home you can set this flag.

https://lhcathome.cern.ch/lhcathome/show_host_detail.php?hostid=10667112

Output:
Waiting for VM "boinc_08b49a28d0ab4c53" to power on...
VBoxManage.exe: error: Not in a hypervisor partition (HVP=0) (VERR_NEM_NOT_AVAILABLE).
VBoxManage.exe: error: VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole

In the result it says "disabled in the BIOS", but the host details says "CPU has hardware virtualization support and it is enabled".

On your Win10 Pro machine Hyper-V is probably enabled. Disable that, reboot and try again.
Hyper-V is not compatible with VirtualBox or VMWare.

No network access would mean that boinc-client is not set to always use internet. You can change this in boinc-manager.

These tasks require internet as it they download and upload job data while they are running. So if task start and do not have internet it would fail after few minutes.

No network access would mean that boinc-client is not set to always use internet. You can change this in boinc-manager.

These tasks require internet as it they download and upload job data while they are running. So if task start and do not have internet it would fail after few minutes.

Not related. VM doesn't start.

Hi, the pc is always connected to the internet and certainly was at the time, which added to my confusion

I will check the hyper V settings.
One thing tho, maybe i'm just blind, but i cat see the flag that makes my pc visable to you in the lhc@home prefs?

On this page:
https://lhcathome.cern.ch/lhcathome/prefs.php?subset=project
"Should LHC@home show your computers on its web site?" should be checked.

Thanks, box ticked.
As for hyper-v. I have checked services (not there) and windows features (not ticked) and even turned it off in the command prompt. Does not seem to be a setting in my bios

This page might be helpful regarding the Hyper-V issue:
https://docs.microsoft.com/en-us/troubleshoot/windows-client/application-management/virtualization-apps-not-work-with-hyper-v

So just to be clear, Hyper v must be off? Becuase i can find anywhere that its on, even turned it on just so i can turn it off.

I assumed that i just virtualbox and all would be good. But do i have to set anything up in virtual box? For one thing, I've looked briefly at setting a VM in there and I only get a 32bit option but the pc is 64 bit. Could this be an issue?

I assumed that i just virtualbox and all would be good. But do i have to set anything up in virtual box? For one thing, I've looked briefly at setting a VM in there and I only get a 32bit option but the pc is 64 bit. Could this be an issue?

Only installing VirtualBox and enabling VT-x in BIOS should be enough.
Since your machine created VM's that part seems to be OK, but the created VM refuses to start IMO because of Hyper-V,
but there is an extensive checklist: https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=4161#29359, thanks to Yeti.
You can watch with VirtualBox Manager, that the VM's are created.

Roger wrote:

... Hyper v must be off?

Absolutely yes.
Otherwise Hyper-V and VirtualBox would fight against each other to get control over the hardware resources and since Windows starts Hyper-V first the resources would already be blocked when Windows starts VirtualBox.

Roger wrote:

I assumed that i just virtualbox and all would be good. But do i have to set anything up in virtual box? For one thing, I've looked briefly at setting a VM in there and I only get a 32bit option but the pc is 64 bit. Could this be an issue?

Just install VirtualBox (and VirtualBox Guest Extensions) and ensure the user running BOINC is allowed to use it.
The LHC@home tasks (-> vboxwrapper) will then create and control the VMs.

<edit>
second
;-(
</edit>

Ok, think i've cracked it.
So I think i read the comments wrong and checked that virtual tech was disabled in bios, which it was, but turns out it needs to be on in order for virtualbox to see the 64bit system. Fingers crossed thats done it.
Thanks for your help guys, sorry if i was a pain.

Roger

@Roger

Some suggestions regarding your project setup.

1.
Your logfiles show this CPU throttle:

2020-09-30 00:06:48 (9700): Setting CPU throttle for VM. (50%)

50% may sooner or later lead to timing problems regarding the communication between the VM and vboxwrapper.
A setting of 100% is recommended.
If you need to reduce the total load on your computer you may set <ncpus>x</ncpus> in your cc_config.xml to a lower value and run "reload config files" from the BOINC manager menu.



2.
This shows that VirtualBox's extension pack is not installed:

2020-09-30 00:06:42 (9700): Required extension pack not installed, remote desktop not enabled.

It's not a must but installing it would give you the opportunity to check the VM's console output.

Thanks for your help guys, sorry if i was a pain.

Roger

You're welcome and congratulations on your first 5 valid Theory tasks: https://lhcathome.cern.ch/lhcathome/results.php?hostid=10667112&offset=0&show_names=0&state=4&appid=13