VMmanager 6: Administrator guide

Operating systems

ISPSystem

OS templates in VMmanager


VMmanager utilizes OS templates to install operating systems (OS) on virtual machines. OS templates in VMmanager are images of the virtual machine disks with an operating system without additional software applications and special settings ("clean" OS). The installation of an operating system on a virtual machine includes two steps: 

  1. Recovery of VM disk from the image of the selected operating system.
  2. Automatic configuration of network parameters. 

Images are kept in .tgz archives and are uploaded to a cluster node only after the first deployment of the operating system on a virtual machine.  

The following operating systems can be installed from the ISPsystem repository on a virtual machine: 

  • AlmaLinux 8;
  • Astra Linux "Orel" 2.12;
  • CentOS 6, 7, 8;
  • CentOS Stream 8, 9;
  • Debian 8, 9, 10, 11;
  • FreeBSD 12, 13;
  • Oracle Linux 8;
  • Rocky Linux 8;
  • Ubuntu 16.04, 18.04, 20.04;
  • VzLinux 8;
  • Windows 10;
  • Windows Server 2012 R2, 2016, 2019. 

Note

Some functions may not be supported on Windows virtual machines. Learn more in Specifics of VM running on Windows

OS information is displayed in Templates → Operating systems. For more detailed information, click on the OS name. Learn more about the OS parameters in the article Editing an OS template

Licensing


You can set up automatic activation of Windows VMs through your own KMS server. KMS (Key Management Service) server allows you to activate corporate versions of Windows within the network without connecting to a Microsoft server.

To use activation via KMS:

  1. Configure the KMS server on a physical or virtual Windows server. This will require a Windows corporate license and a KMS key. Read more in the official Microsoft documentation.
  2. Specify KMS server parameters in the OS template settings in VMmanager:
    • License key. This key will be assigned to all VMs during OS installation.
    • IP address and connection Port.

      Note

      You cannot specify a Microsoft server as a KMS server.

      Note

      You can also set up VM access to the KMS server via SRV records on your DNS server.

To check activation, execute the following command on the VM:

slmgr.vbs /dli

Compatibility with scripts


Scripts allow configuring virtual machines automatically: install software programs, modify configuration files, etc. Normally, every script is developed for a certain operating system. E.g. a script for CentOS 7 may work incorrectly on Debian 9, as the configuration files of the system are located in different repositories.  VMmanager uses tags to define that scripts are compatible with a certain operating system. A script can be executed on an operating system provided that they have at least one similar tag.  The OS tags cannot be changed that's why you need to specify the tags when creating a new script. Learn more in the article Creating a script for the VM

Thank you for your feedback!
Was the article useful?
Tell us why not:

it does not match the title

it was hard to understand

I didn't find the answer

recommendations from the article did not help

other

Tell us what you didn't like in the article: