LHC@home

Hi,

I do not understand why on one of my machines I receive the sixtrack, ATLAS, CMS and Theory tasks and on another than the sixtrack tasks, how to fix the problem?

Sam.

---

Powered by Debian & Ubuntu 20.04
Boinc version 7.16.6 x86_64-pc-linux-gnu

2 of your computers show this entry on the computer details page:
https://lhcathome.cern.ch/lhcathome/show_host_detail.php?hostid=10680479
https://lhcathome.cern.ch/lhcathome/show_host_detail.php?hostid=10680860

Virtualization None

Those computers will only be able to run SixTrack or ATLAS/Theory native which require a local CVMFS (already discussed).

To run VBox apps your computer must support virtualisation, it must be switched on and VirtualBox must be installed.

2 of your computers show this entry on the computer details page:
https://lhcathome.cern.ch/lhcathome/show_host_detail.php?hostid=10680479
https://lhcathome.cern.ch/lhcathome/show_host_detail.php?hostid=10680860

Virtualization None

Those computers will only be able to run SixTrack or ATLAS/Theory native which require a local CVMFS (already discussed).

To run VBox apps your computer must support virtualisation, it must be switched on and VirtualBox must be installed.

Ok but I have virtualbox installed as well as the necessary libraries on soleil-host:

samp@soleil-host:/var/lib/boinc-client$ apt-cache show virtualbox
Package: virtualbox
Status: install ok installed
Priority: optional
Section: misc
Installed-Size: 45517
Maintainer: Debian Virtualbox Team <pkg-virtualbox-devel@lists.alioth.debian.org>
Architecture: amd64
Version: 4.1.42-dfsg-1+deb7u1
Replaces: virtualbox-ose (<< 4.0.6-dfsg-1~)
Depends: libc6 (>= 2.6), libgcc1 (>= 1:4.1.1), libgsoap2, libpng12-0 (>= 1.2.13-4), libpython2.7 (>= 2.7), libsdl1.2debian (>= 1.2.11), libssl1.0.0 (>= 1.0.0), libstdc++6 (>= 4.6), libvncserver0, libx11-6, libxcursor1 (>> 1.1.2), libxext6, libxml2 (>= 2.7.4), libxmu6, libxt6, zlib1g (>= 1:1.1.4), python (>= 2.6.6-7~), python (<< 2.8), python2.7, adduser
Pre-Depends: dpkg (>= 1.15.6~)
Recommends: virtualbox-dkms (= 4.1.42-dfsg-1+deb7u1) | virtualbox-source (= 4.1.42-dfsg-1+deb7u1), virtualbox-qt (= 4.1.42-dfsg-1+deb7u1), libgl1-mesa-glx | libgl1, libqt4-opengl (>= 4:4.5.3), libqtcore4 (>= 4:4.5.3), libqtgui4 (>= 4:4.5.3)
Suggests: virtualbox-guest-additions-iso, vde2
Breaks: virtualbox-ose (<< 4.0.6-dfsg-1~)
Conflicts: virtualbox-2.0, virtualbox-2.1, virtualbox-2.2, virtualbox-3.0
Conffiles:
 /etc/init.d/virtualbox e2c78950e836770caa0b1e21f235d191
 /etc/default/virtualbox 903beafa3922607d1ac07950d9ae2d50
Description: x86 virtualization solution - base binaries
 VirtualBox is a free x86 virtualization solution allowing a wide range
 of x86 operating systems such as Windows, DOS, BSD or Linux to run on a
 Linux system.
 .
 This package provides the binaries for VirtualBox. Either the virtualbox-dkms
 or the virtualbox-source package is also required in order to compile the
 kernel modules needed for virtualbox. A graphical user interface for
 VirtualBox is provided by the package virtualbox-qt.
Description-md5: 30f96d22c1a6ca04db16bdc1e79ad965
Homepage: http://www.virtualbox.org/

!?

Sam.

---

Powered by Debian & Ubuntu 20.04
Boinc version 7.16.6 x86_64-pc-linux-gnu

... I have virtualbox installed ...

The BOINC client tests the hardware/BIOS for virtualization first.
If this test fails for whatever reason it doesn't matter whether VirtualBox is installed or not.

... I have virtualbox installed ...

The BOINC client tests the hardware/BIOS for virtualization first.
If this test fails for whatever reason it doesn't matter whether VirtualBox is installed or not.

Ok, and there is no way to find out why?

Sam.

---

Powered by Debian & Ubuntu 20.04
Boinc version 7.16.6 x86_64-pc-linux-gnu

Ok, and there is no way to find out why?

On your affected computers you may:
- shut down BOINC
- open "client_state.xml" in BOINC's data directory and check whether there's a line "<p_vm_extensions_disabled>1</p_vm_extensions_disabled>"
- if YES, remove that line and save the file
- start BOINC


Recent BOINC clients solve this automatically at every client restart but your client might be too old.

Ok, and there is no way to find out why?

On your affected computers you may:
- shut down BOINC
- open "client_state.xml" in BOINC's data directory and check whether there's a line "<p_vm_extensions_disabled>1</p_vm_extensions_disabled>"
- if YES, remove that line and save the file
- start BOINC


Recent BOINC clients solve this automatically at every client restart but your client might be too old.

I upgraded to virtualbox v6.1.18, restarted Boinc, update project, it's ok now !

Thanks again.

Sam.

---

Powered by Debian & Ubuntu 20.04
Boinc version 7.16.6 x86_64-pc-linux-gnu