Will KosmicTask run on a virtual machine?
KosmicTask runs well on virtual machines such as vmware Fusion and numerous virtual installations of the application are used for testing purposes. The virtualisation technology makes it much easier to produce a network of interacting KosmicTask instances.
There are a few points to bear in mind however when using KosmicTask in virtualised environments:
- The virtual machine (vm) must have functioning network access in order for KosmicTask to see other network instances and be seen by them (the application uses Bonjour to locate other instances). Each vm must have a unique IP address set. An IP address collision will prevent the vm from accessing the network. This can be a problem when cloning existing vms. In the case of the Fusion vm the network settings should be configured for bridging rather than NAT.
- If the vm is suspended while KosmicTask is running then other instances of the application may not detect it when the vm is reloaded. In this case it may be necessary to restart KosmicTask on the vm.
- A virtual environment is not the same as a native environment and some tasks may behave differently when executed with a virtualised host. For example, screen capture tasks may fail to capture the expected screen image.