Once VM2 is installed, you can login to it by opening a web browser and going to the URL http://mastersystem:10000/ , where mastersystem is the hostname or IP address of the machine on which it is installed. This should bring up a web page with a menu on the left frame, and a display of information about the master system on the right.
The VM2 interface is in many ways similar to Virtualmin - managed systems can be selected from a drop-down menu on the left, below which is a list of links for performing various operations on those systems. Below this are menu categories labelled Create System, Add System and VM2 Settings. These contain further links for creating new virtual systems, bringing existing virtual or real systems under VM2's control, and editing settings that apply to all managed machines.
At the bottom is the List Managed Systems link, which opens a list of all systems under VM2's control, showing details such as their hostname, current status and virtualization system type. By default, the only registered system will be the machine you are running VM2 on.
Every system managed by VM2 has a status, which is determined from either an automatic check (done every 5 minutes), or a manual check triggered by the Refresh Status link. The status can be seen on the left menu directly under the hostname. Possible statuses are :
The master system will most likely have the status Webmin but no Virtualmin, unless you are also using it to host domains with Virtualmin.
If you have several running physical systems on your network and want to control them using VM2, they can be added to its list of managed systems as follows :
root password and root logins via SSH are allowed, in the Root login mode section select Using password and enter the password into the adjacent textbox.Once a system has been added, it can be used to host Virtualmin domains, or virtual systems using Xen or VServers if it has the needed software installed.
To view the full details of a managed system, click on the Edit System link below its hostname on the left menu. This will bring up a page showing the software versions it runs, current status and login details. If it runs Virtualmin, hosted domains and more detailed system status will also be shown in collapsed sections. If it is a virtual system that VM2 can manage network interfaces on, a section listing interfaces will also be available.
For systems that are currently up, you can use the Reboot System and Shutdown System links on the left menu to reboot or turn them off, respectively. Similarly, a virtual system that is down can be started up using the Startup System link. If a system has been rebooted or changed manually since the last VM2 automatic check, you can use the Refresh Status link to have VM2 fetch the current status.
If a managed system has Webmin installed and running, you can connect to it using the Open Webmin link on the left menu. This will open a new browser window which will be automatically logged into the system, with all HTTP requests tunnelled through the VM2 master. This is a little slower that connecting directly (by opening the URL for Webmin on that system in your browser), but is more convenient and avoids any connectivity issues that may block access to the system.
Managed systems that are up and can be contacted via SSH can have commands executed on them via the VM2 interface by clicking on the Run Commands link on the left menu. This will open a page for entering a shell command, which will display the output from that command when it is run. However, only non-interactive programs can be run - you cannot invoke something like vi or yum which expects user input.
To update the root password for SSH or Webmin on a managed system, you can use the Change Password link on the left menu. This will open a form for entering one or both new passwords, which when submitted will update /etc/shadow and /etc/webmin/miniserv.users on the selected machine to make the changes. VM2's authentication information for the system will also be updated to match.
If you have created a virtual system for a customer, changing the root password when you are ready to hand it over is a good idea. Be aware that for Xen systems, if the password is changed on the system directly (perhaps using the passwd command), VM2 will be no longer able to login via SSH to change it, or even to check the system's status.
Once you have several systems registered, it becomes convenient to perform operations on more than one at once. This can be done as follows :