LHC@home

Hi.
My OS is Windows 10 Pro 64-bit and when I try to set up the VirtualBox under 'New' I can only chose the option Window 10 32-bit.
Can I use the VirtualBox despite the fact that I do not have the 32-bit version of Windows 10 or should I look for an other version of the VirtualBox?

Tomas

---

I will avoid setting up the VirtualBox, for now at least.
Seams to be a complicated procedure.

---

Problem solved!
All I had to do was going in to my account page here under 'Project Account' \' Preferences for this project' \ 'Edit preferences' and mark the checkbox for the project I want to run.

---

The applications that do the work for the Theory, ATLAS, LHCb and CMS simulations all run on Linux OS, not Windows. So even if you had created a Windows Virtual Machine it would not have done you any good.

The applications you see listed on the applications page don't do any of the number crunching. All they do is download a VMI (Virtual Machine Image) to your computer, hand that VMI over to VirtiualBox to run and then do some monitoring and uploading of reports. The VMI is a Linux machine that has the applications that run the Theory, ATLAS, LHCb and CMS simulations.

The applications that do the work for the Theory, ATLAS, LHCb and CMS simulations all run on Linux OS, not Windows. So even if you had created a Windows Virtual Machine it would not have done you any good.

The applications you see listed on the applications page don't do any of the number crunching. All they do is download a VMI (Virtual Machine Image) to your computer, hand that VMI over to VirtiualBox to run and then do some monitoring and uploading of reports. The VMI is a Linux machine that has the applications that run the Theory, ATLAS, LHCb and CMS simulations.

Thank you bronco!
I did not se that information but I will stop running this applikations now.

---

It seams to work now, I had to go in to BIOS under M.I.T -> Ext. CPU core settings and set "SVM mode" to "enabled"
2 Atlas WU has been running för 30 minutes now, I will take a look at the final result when they are finished before downloading more.

---

It looks like they ran for close to an hour then failed. In the stderr output for one of the failed tasks I see one problem that sounds serious:

- Processor supports HW virtualization: no
I believe this would be a fatal error. In a previous post it sounded like you turned hardware virtualization (AMD-V) on in BIOS. Maybe you did not save the BIOS settings?

and further down...
VBoxManage.exe: error: AMD-V is not available (VERR_SVM_NO_SVM)
Again it seems AMD-V is not enabled in BIOS

Another small problem which is likely not fatal:
Required extension pack not installed, remote desktop not enabled.

VBoxManage.exe: error: AMD-V is not available (VERR_SVM_NO_SVM)
Again it seems AMD-V is not enabled in BIOS

this definitely shows that virtualization is NOT enabled!

Another small problem which is likely not fatal:
Required extension pack not installed, remote desktop not enabled.

this should NOT be a problem - the installation of the extension pack is NOT essential for the VM to run properly.

I don't have extensions installed on any of my machines as it's more work to updated them.

My i7-4930K\Windows 8.1 and AMD FX(tm)-8350\Windows 8.1 computers seams to work fine now.
On my Threadripper I think I made a mistake by enabling 'Hyper-V' in Windows, I have un-checked that box now and waiting for next ATLAS wu to see if it will work now.

---

My i7-4930K\Windows 8.1 and AMD FX(tm)-8350\Windows 8.1 computers seams to work fine now.
On my Threadripper I think I made a mistake by enabling 'Hyper-V' in Windows, I have un-checked that box now and waiting for next ATLAS wu to see if it will work now.

If it works now then that would suggest enabling Windows' Hyper-V somehow confuses VBox and causes VBox to think AMD-V is not enabled when it actually is? Anything is possible but intuition tells me such a scenario is highly unlikely.

Time will tell. If it works now on your ThreadRipper then all is good but I think it won't work until you go into the BIOS and enable AMD-V.

I can't find AMD-V in BIOS on my Threadripper box, in BIOS I have 'SVM Mode' under M.I.T \ Advanced Frequency Settings \ Advanced CPU core Settings and that is set to 'Enabled'

---

Sounds like you did that right as long as you Go to “Save & Exit”, select “Save Changes and Reset”, and you are finished.

To enable AMD Secure Virtual Machine, SVM
Step 1: Start the Turbo NAS and press the F2 key until the BIOS screen is displayed. Then go to “Advanced” > “CPU Configuration”.

Step2: Go to “SVM Mode” and select “Enabled”.

Step3: Go to “Save & Exit”, select “Save Changes and Reset”, and you are finished. (and YES)

Then of course have the proper VB version installed and then reboot.

HERE --> https://www.virtualbox.org/wiki/Downloads

... 'SVM Mode' under M.I.T \ Advanced Frequency Settings \ Advanced CPU core Settings and that is set to 'Enabled'

Good.
Did you also follow step 5 of Yeti's checklist?

... 'SVM Mode' under M.I.T \ Advanced Frequency Settings \ Advanced CPU core Settings and that is set to 'Enabled'

Good.
Did you also follow step 5 of Yeti's checklist?

It looks like this in my client_state.xml

<p_vm_extensions_disabled>1</p_vm_extensions_disabled>

so that's looks ok

EDIT: This computer downloaded a lot of ATLAS work units at the beginning and they all failed, that's make me wonder if this computer has been marked as 'unreliable' and wont be sent an ATLAS work unit for a few days or so?

All I know is that this computer receives SixTrack work units and my other computers both SixTrack and ATLAS work units.

---

... <p_vm_extensions_disabled>1</p_vm_extensions_disabled>

so that's looks ok

No!
This is exactly how it should NOT look like.
Set the option to "0" or delete the line.

You didn't follow Yeti's checklist, did you?

... <p_vm_extensions_disabled>1</p_vm_extensions_disabled>

so that's looks ok

No!
This is exactly how it should NOT look like.
Set the option to "0" or delete the line.

You didn't follow Yeti's checklist, did you?

Sorry, you are right. :)

EDIT: I was back for lunch and just had a quick look before returning to work, work units for ATLAS is downloading now.

---

Now ATLAS finally runs but the BOINC (7.10.2) behavior is rather odd as it currently only use 58% of the memory and cpu, I wonder how much more it's going to drop.
atm BOINC only runs 2 ATLAS(8 cpu) and 3 SixTrack on a computer that has 32GB RAM and 16 cores.

EDIT: Now the use have dropped even more and currently only 2 ATLAS(8 cpu) and 1 SixTrack is running.

---