Tips for Working with Virtual Machines

Have you installed GMS, SMS, or WMS (collectively referred to as XMS) on a virtual machine in your office? Using a virtual machine is often done in order to run multiple operating systems, consolidate computing resources, provide integrated disaster recovery, or a number of other reasons. XMS software can be installed on a virtual machine in order to fit your needs. Here are some tips for working with XMS when using a virtual machine.

First, make certain that your XMS license is compatible with a virtual machine. Both local and flex license codes can be used with a virtual machine. However, local codes will not allow the software to be used by other machines. Older single-user locks cannot be used with a virtual machine.

When using a flex license, the virtual machine will need to have access to the local network in order for other machines to access the XMS license and use the software. Both the XMS application and the Aquaveo License manager need to be installed on the virtual machine.

When sharing files between a virtual machine and a host machine, pay attention to where XMS is running. XMS requires that all files be placed where XMS is installed. Therefore, you cannot save your project on the host machine and run them from the virtual machine if XMS is installed on the virtual machine. You will need to move the files to the virtual machine where XMS and XMS license is installed.

It should also be noted that some simulation runs and application processes in XMS will run slower on a virtual machine than running the same process directly on a physical machine. This is due to the nature of using a virtual machine. If there is a process that is taking an unusually long time, it is recommended that you try running the application on a physical machine.

If you are experiencing issues running XMS on a virtual machine, contact our technical support team and they will be happy to assist you.