1) Forums : General Topics : Unattended Project ... (Message 22564)
Posted 16 Jun 2020 by Evans CAH
Post:
Disconnecting.
2) Forums : General Topics : Jobs are being created with VT-x / AMD-V disabled (Message 22563)
Posted 16 Jun 2020 by Evans CAH
Post:
Related issue: a bug in the BOINC client meant that once system-level virtualization was switched off (e.g. after a BIOS flash or reset) BOINC would then assume it was off forever. The effect was that VB projects would be ignored irrespective of the firmware setting. This was fixed in March 2020 in client 7.16 (see https://boinc.berkeley.edu/wiki/Release_Notes)
3) Forums : General Topics : Will upcoming Windows Sandbox feature cause problems? (Message 22095)
Posted 20 Feb 2019 by Evans CAH
Post:
Not so fast on the Hyper-V: as this article makes sort of clear, security partitioning using virtualization is a double edged sword. In a way, all it does is raise the stakes. A better defence may be (still) to engineer for rebuildability, not recoverability.

https://arstechnica.com/gadgets/2019/02/researchers-use-intel-sgx-to-put-malware-beyond-the-reach-of-antivirus-software/
4) Forums : General Topics : Jobs are being created with VT-x / AMD-V disabled (Message 22093)
Posted 18 Feb 2019 by Evans CAH
Post:
That's what I'm referring to, yes. I just realized this setting enables nested hardware virtualization, new in VB 6.0, which obviously isn't needed.

BOINC is correctly assigning CPUs up to the maximum. After a bit of experimentation, I think my issue is exactly what you describe: that I (and BOINC) can't set the scheduler priority of individual VMs. On this box I am using VB for non-BOINC stuff that needs to be responsive. I can't just demote the VB service to a lower priority because that will demote all VMs, BOINC and non-BOINC.

I will try your app_config fix, but last I checked all Cosmology jobs had been 'unmanageable' for days and I had to humanely kill them.

For what it's worth there is another workaround, which is to allow BOINC network access only at night, when the machine doesn't have fussy users on it. The VM jobs won't run without internet access, so they politely wait. The side-effect is that you have to run a huge job cache so that the machine has something to do during the day.
5) Forums : General Topics : Jobs are being created with VT-x / AMD-V disabled (Message 22091)
Posted 13 Feb 2019 by Evans CAH
Post:
Thanks for the feedback. I am seeing it in the VirtualBox interface under Settings/System/Processor. Every Cosomology VM has AMD-V disabled. While the VMs are running, the machine is unusable.

The flag can be manually set, and the setting sticks.

I probably aborted jobs that are 'unmanageable'. This has nothing to do with AMD-V.

I should add I am using an app_config to limit each VM to two CPUs.

Anyone else on VB 6.02?
6) Forums : General Topics : Jobs are being created with VT-x / AMD-V disabled (Message 22066)
Posted 5 Feb 2019 by Evans CAH
Post:
All Cosmology jobs are being created with the VT-x / AMD-V flag reset. This makes running the project more or less impossible. The jobs run, but they clobber the machine so badly that it is unusable.

If I set the flag manually for each waiting VM, they and other VMs run normally.

This may not be a Cosmology problem - I think Atlas was doing the same thing. I can't verify that right now as there is no Atlas work available.

The only mention of VT-x in any log is in the VM log:

00:00:02.108645 HM: VT-x/AMD-V init method: LOCAL


but this entry looks the same for VMs with the flag set. I don't see way to enforce this setting globally.

This is an AMD box.

Anyone else seeing this? Google says not.

VB 6.02
BOINC 7.14.2 & 7.15
7) Forums : General Topics : Will upcoming Windows Sandbox feature cause problems? (Message 22065)
Posted 5 Feb 2019 by Evans CAH
Post:
A recent Windows update enabled Hyper-V and broke VirtualBox on my system. Disabling Hyper-V using bcdedit fixed VB.
Unfortunately there are some nice security features that do require a type I hypervisor like Hyper-V, so in the medium term I will make the switch away from VB if I can ever get Hyper-V's networking to work.