Changes between Version 74 and Version 75 of VboxApps
- Timestamp:
- Jul 1, 2014, 1:23:47 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
VboxApps
v74 v75 28 28 so in general you can't use them in the VM image. 29 29 Similarly, you can't include pay-per-user software such as Matlab in the VM image. 30 31 30 * !VirtualBox runs only on Intel-compatible processors. 32 31 If you want to support other processors (such as ARM, SPARC, etc.), 33 32 you'll need to use non-VM-based app versions. 34 35 33 * Currently you can't run GPU applications in !VirtualBox VMs. 36 34 This may change in the future. … … 164 162 vboxwrapper sends a [TrickleApi trickle-up message] whose variety is the filename 165 163 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). 171 172 '''minimum_checkpoint_interval''':: minimum number of seconds before a checkpoint/snaposhot can be created. 172 173 Defaults to 10 minutes. (v26086+)