Re: [boinc_dev] vbox64 and virtualization

[Rom Walton]

What is supposed to happen is:

When the VM shuts down, vboxwrapper parses the end of vbox.log looking for the 
possible error codes related to the VM extensions being disabled.  If found, it 
then writes the following to stderr 'ERR_CPU_VM_EXTENSIONS_DISABLED'.

BOINC parses the stderr text when the app exits, if it detects the above text 
it sets a flag that says the VM extensions have been disabled on the machine.  
In the sched_request file it is named .

I recently updated vboxwrapper to support the newer error codes returned in 
VirtualBox 5.0:
https://github.com/BOINC/boinc/commit/0ee90d7995118ff5fd00c68af734050172f7733a

That commit should be in 26173 or above.

- Rom

List of VirtualBox error codes is in vbox_common.cpp:320-338

What is written to stderr is in vboxwrapper.cpp:774-784

-Original Message-
From: boinc_dev [mailto:boinc_dev-boun...@ssl.berkeley.edu] On Behalf Of Marius 
Millea
Sent: Thursday, October 15, 2015 7:31 PM
To: BOINC-dev email list 
Subject: [boinc_dev] vbox64 and virtualization

Hi all,

Virtualbox can't run a 64bit guest OS unless you have virtualization (VT-x or 
AMD-v or whatever it might be called...) enabled in your BIOS. Hence no app 
which is plan class vbox64 should be sent to a host which does not have this 
enabled. Unfortunately I'm not seeing either happen. First, I turned off VT-x 
on my machine, rebooted and readded the project, and I'm still receiving vbox64 
jobs. Should this be happening or is this a feature which does not exist yet?

Secondly, it seems like vboxwrapper ought to catch this and shut down with some 
informative error message. From the source it looks like it does have some code 
which attempts to catch this, but at least on my system it doesn't seem to 
work. It gets stuck saying "Status Report:
virtualbox/vboxheadless is no longer running." for a while, then gives me 
"Waiting to run (VM Hypervisor failed to enter an online state in a timely 
fashion)". Any ideas what's going on?

Thanks,

Marius
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

[boinc_dev] vbox64 and virtualization

[Marius Millea]

Hi all,

Virtualbox can't run a 64bit guest OS unless you have virtualization (VT-x
or AMD-v or whatever it might be called...) enabled in your BIOS. Hence no
app which is plan class vbox64 should be sent to a host which does not have
this enabled. Unfortunately I'm not seeing either happen. First, I turned
off VT-x on my machine, rebooted and readded the project, and I'm still
receiving vbox64 jobs. Should this be happening or is this a feature which
does not exist yet?

Secondly, it seems like vboxwrapper ought to catch this and shut down with
some informative error message. From the source it looks like it does have
some code which attempts to catch this, but at least on my system it
doesn't seem to work. It gets stuck saying "Status Report:
virtualbox/vboxheadless is no longer running." for a while, then gives me
"Waiting to run (VM Hypervisor failed to enter an online state in a timely
fashion)". Any ideas what's going on?

Thanks,

Marius
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.