| | 99 | |
| | 100 | === Multiattach mode disk images === |
| | 101 | |
| | 102 | {{{ |
| | 103 | #!comment |
| | 104 | The vboxwrapper version number needs to be added once the new version is available. |
| | 105 | }}} |
| | 106 | As of version xxxxx '''vboxwrapper''' can deal with multiattach-mode/differencing disk images as described in the [https://www.virtualbox.org/manual/ch05.html#diffimages VirtualBox manual]. This avoids the need to copy a huge "vm_image.vdi" file to the worker slot each time a fresh WU starts. Instead the vdi image remains in the project directory, is opened read-only and used for all WUs referring to it. !VirtualBox transparently ensures that all disk '''writes''' go to a separate vdi file within the slot directory of a WU. That "differencing image" is usually much smaller than the parent vdi image. |
| | 107 | |
| | 108 | To enable this mode add '''<multiattach_vdi_file>filename_version.vdi</multiattach_vdi_file>''' to vbox_job.xml with filename_version.vdi being the name of the parent vdi image in the project directory. |
| | 109 | Compared to the setup above the app version needs to be configured slightly different: |
| | 110 | |
| | 111 | * The VM image, in !VirtualBox format. |
| | 112 | * The logical name "vm_image.vdi" should not be set. |
| | 113 | * The copy_file attribute should '''not''' be set to avoid copying the vdi file to the slot directory. |
| | 114 | * Should have the sticky attribute set. |
| | 115 | * During contextualization/creation of the vdi image this mode must not be used |