I have two machines here, both have i7 processors under Windows 8.1. One of these machines runs SkyNet's duchamp project, the other does not, it says...

>>>
duchamp: Notice from server
VirtualBox jobs require hardware acceleration support. Your processor does not support the required instruction set.
07/06/2017 11:19:40
<<<

... now, obviously that is not true as it is running on here, but it indicates that something is loaded or installed here that is not so on the other machine. So, simple question, what?

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

Are both of them the same VirtualBox?
For the i7 that has the message, when you go into its BIOS, is the VT-x option enabled?

---

>>> Are both of them the same VirtualBox?

Yes, 5.1.22, I don't know if that is the most up to date, but it is certainly adequate for the projects that use it on here. I'll check the BIOS of the other machine when I get back, certainly sounds possible from the wording of the warning.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

You may also want to check on the motherboard's web page if there is a new BIOS for that one. Especially when it's a new motherboard, they go through various revisions and modifications for stability.

---

Both have the same motherboard, (ASUS Sabertooth Z170, Sabertooth is how they spell it), but purchased at different times so another possibility. I'll look at this when I am back.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

UEFI BIOS says VTx is "supported" but does not give me an option to enable/disable it.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

I've noticed that when VT is not enabled in the BIOS then the only OSs I can install in VBox are 32bit even with a 64bit CPU. That might be an indicator of it being disabled.

But if the option to enable or disable is not presented, how can I do it? This machine also runs 64 bit Windows 8.1 and has no trouble running duchamp with the same version of VBox.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

I have downloaded your Motherboard Manual, in section 3.2 (page 3-3 and further) it says here you start in EZ Mode, where it shows you the status of the Intel Virtualization Technology. If you cannot change it here, press F7 to go to Advanced Mode, click Advanced at the top of the screen, click CPU Configuration, click Intel Virtualization Technology.

There is a separate VT-d under Advanced\System Agent (SA) Configuration. This allows you to use the GPU in virtual machines.

Use the Exit menu to save changes & reset.

---

This IS enabled.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

Okay, and the BIOS version is which?
What kind of i7 is it?

---

If they are already successfully completing duchamp tasks then its not the BIOS option being enabled or not. It should be something else.

Ageless:

I'll do this as a two step process, System Info, (msinfo32), from here, then later on, edit it in from the other machine.

Blackwater node, (the working system):

BIOS Version/Date: American Megatrends Inc. 1203, 22/10/2015
Processor: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz, 4001 MHz...

Frogmore node, (the system with the issue):

BIOS Version/Date: American Megatrends Inc. 1203, 22/10/2015
Processor: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz, 4001 MHz...

They appear to be identical.

mmonnin:

They are not completeing duchamp, one is, the other is not, that is why I am here trying to resolve the issue. To add, both systems are running multiple projects, it was trying to add duchamp, that this issue arose.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

I am on the failing machine now, I have...

<p_vm_extensions_disabled>1</p_vm_extensions_disabled>

... would it be right to assume this is wrong? If it is, how did it come to be so?

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

So it is safe to set to 0, okay, I'll try this. VBox runs on the failing machine, there are projects on there that use it, Einstein and MilkyWay for example. As I said earlier, the VTx parameter is set on there.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

I've changed it.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

I believe it gets set to 1 when you have tried to run a VBox task without having VT-x enabled in the Bios.
Unfortunately once set by Boinc it doesn't reset it (to 0) when VT-x is enabled, it has to be done manually.

Thanks for that. Learned something new. :)

---

... so am I.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

The machine that was not running the jobs, still has not run a job. It is beginning to look like the fix might have fixed something, but not the right thing.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

Fair enough, I'll see what happens then. I have no jobs on this system either. I'd set it's quota up to be sure I get one on there, but the VBox task does not run at low priority, several running together at normal priority knackers the system performance, they are aware of this.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.