Changes between Version 64 and Version 65 of VboxApps


Ignore:
Timestamp:
Mar 24, 2014, 2:26:41 PM (10 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • VboxApps

    v64 v65  
    154154  If missing or zero, the host port number is assigned dynamically, and is written to a file
    155155  '''vbox_port_forward.xml''' in the slot directory.
    156  '''copy_to_shared''':: file(s) you wish to copy into the shared directory before launch.
     156 '''copy_to_shared''':: copy the given file into the shared directory before launch.
    157157  This directive can be used more than once.
     158
     159== Vboxwrapper command-line options ==
     160
     161 --trickle X :: Send a trickle message reporting elapsed time every X seconds.
     162  Use this for creating granting if needed.
     163 -- nthreads N :: Create a virtual machine that will use N cores.
     164 --vmimage file :: Use "file" as the VM image.
     165   This lets you create an app version with several images,
     166   and the app_plan function can decide which one to use for the particular host.
     167 -- register_only :: Register the VM but don't run it.  For debugging; see below.
    158168
    159169== Creating jobs for VM apps ==
     
    165175
    166176This causes the BOINC client to copy them to and from the '''slot/x/shared/''' directory.
     177
     178== Debugging VM apps ==
     179
     180To debug a VM within the BOINC/VboxWrapper framework:
     181
     182 * Launch BOINC with --exit_before_start
     183 * When BOINC exits, launch the VboxWrapper with the register_only
     184 * Set the VBOX_USER_HOME environment variable to the vbox directory
     185   under the slot directory.
     186   This changes where the VirtualBox applications look for the
     187   root VirtualBox configuration files.
     188   It may or may not apply to your installation of VirtualBox.
     189   It depends on where your copy of VirtualBox came from
     190   and what type of system it is installed on.
     191 * Now Launch the VM using the VirtualBox UI.
     192   You should now be able to interact with your VM.
    167193
    168194== Premade vboxwrapper executables ==