Changes between Version 74 and Version 75 of VboxApps


Ignore:
Timestamp:
Jul 1, 2014, 1:23:47 PM (10 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • VboxApps

    v74 v75  
    2828  so in general you can't use them in the VM image.
    2929  Similarly, you can't include pay-per-user software such as Matlab in the VM image.
    30 
    3130 * !VirtualBox runs only on Intel-compatible processors.
    3231  If you want to support other processors (such as ARM, SPARC, etc.),
    3332  you'll need to use non-VM-based app versions.
    34 
    3533 * Currently you can't run GPU applications in !VirtualBox VMs.
    3634  This may change in the future.
     
    164162   vboxwrapper sends a [TrickleApi trickle-up message] whose variety is the filename
    165163   and whose contents is the contents of the file, then deletes the file.
    166  '''completion_trigger_file''':: if vboxwrapper finds a file of this name in the shared directory,
    167    it cleans up the VM and exits.
    168    The file can optionally contain an integer exit code (first line)
    169    and stderr text (second line).
    170    This is a workaround for a problem where VMs don't exit cleanly.
     164 '''completion_trigger_file'''::
     165   This provides a more bulletproof way for VM apps to exit;
     166   sometimes VMs fail to shut down, and the task hangs indefinitely.
     167   When the VM app is done, it writes a file of this name in the shared directory;
     168   the file can optionally contain an integer exit code (first line)
     169   and stderr text (subsequent lines).
     170   If vboxwrapper finds this file,
     171   it cleans up the VM and exits with the given code (default 0).
    171172 '''minimum_checkpoint_interval''':: minimum number of seconds before a checkpoint/snaposhot can be created.
    172173  Defaults to 10 minutes. (v26086+)