1. The virtual appliance
With the Checkmk virt1 virtual appliance you can run Checkmk as a guest on an existing virtualization platform (hypervisor) such as VMware ESXi or Proxmox. VirtualBox is also supported and is particularly suitable for testing purposes.
The operating system and a web interface for administration are already pre-installed in the appliance. The appliance is set up with dialog support, can be configured via the web interface and is ready for use after a few simple steps. You therefore do not need any Linux knowledge.
2. Downloading the appliance
You can download the appliance software via the download page. For the Standard Edition and the Managed Services Edition you will require a valid subscription and the associated access data.
The following file types are available as downloads for the virtual appliance:
OVA file: The virtual appliance Checkmk virt1 for import into the hypervisor. OVA stands for Open Virtualization Archive and is the archive format used by the Open Virtualization Format (OVF). The OVA file can be found in the download area at the Checkmk appliance product.
You need this file for the initial installation.
CFW file: The appliance’s firmware. Just like the OVA file, a CFW file is provided in the download area for each appliance version. You can use this file to update an already installed appliance during operation. An update of the firmware is done through the appliance web interface.
You do not need the CFW file for the initial installation, as the OVA file already contains the firmware.
CMA file: The Checkmk software for installation in the appliance. Starting with appliance version 1.4.14, no Checkmk software is pre-installed in the appliance. You also carry out the installation of the Checkmk software via the appliance web interface. The CMA file is available in the download area after selecting the appliance as the platform, the Checkmk edition and version.
You will only need the CMA file after the installation has been completed — when you configure the appliance.
Download the OVA file for the initial installation of the virtual appliance.
3. Installation under VirtualBox
For the following steps, you will need a functioning VirtualBox installation in addition to the OVA file. It does not matter on which system VirtualBox is running.
3.2. Importing the appliance
Start the import of the OVA file via File > Import Appliance and select the OVA file. You will then see all of the settings for the virtual machine — and you can leave these as they are for now. You can, of course, modify values at this point or later, for example, to assign additional resources to the machine.
Important: In the appliance settings, you should always select the Generate new MAC addresses for all network adapters option under MAC Address Policy. Otherwise, there will be problems if more than one appliance with the same MAC address is running on the network.
You can now import the appliance.
Following the import, you will still need to carry out one more step: Call up the network configuration for the virtual machine. The mode here is set to Bridged Adapter: The virtual network adapter is thereby connected to an adapter on your host — and of course these will vary. If in doubt, simply exit the configuration without changing it by pressing OK — VirtualBox will then automatically fill in the missing adapter name with your default adapter.
You have now completed the VirtualBox-specific steps.
4. Installation under VMware ESXi
You need the OVA file for the appliance. You will also need an ESXi server already running on the network and data storage in this for the virtual machine configurations.
4.2. Importing the appliance
The appliance import runs largely automatically, but afterwards you should take a look at the network configuration.
In the ESXi main navigation, select the item Virtual Machines.
Start the import wizard via Create/Register VM.
Select the import via OVA/OVF.
Add the OVA file.
Continue clicking through the wizard without making any further changes.
The import process may take a few minutes, after which the new virtual machine will then be made available.
Important: The Checkmk virt1 comes with an E1000 type network interface, an emulation of the 1 GB network adapter Intel 82545EM Gigabit Ethernet NIC, for which drivers are usually already available. For better performance on an ESXi server you should replace this card with a card of the VMXNET 3 type, a completely virtualized 10 GB interface. To do this, install VMware Tools and change the setting under virt1 > Edit > Network Adapter 1 > Adapter Type:
You will now have completed the VMware ESXi-specific steps.
5. Installation under Proxmox
You will require the OVA file for the appliance and a functioning Proxmox installation (a basic configuration is sufficient).
The import under Proxmox currently needs to be done partly by hand, so it consists of several steps:
the creation of the virtual machine via the Proxmox web interface
uploading the OVA file to the Proxmox server
unpacking the OVA file in the terminal
importing the virtual hard disks using the terminal
5.3. Importing the appliance
First create a virtual machine in the Proxmox web interface. When doing so, configure at least the following settings differently from the defaults:
General > VM ID: any, here
OS: Do not use any media
HardDisk: Delete default entry!
CPU > Sockets:
Now upload the OVA file to the Proxmox server (here
user@linux# scp virt1-demo-1.5.4.ova email@example.com:/var/lib/vz/images
Switch to the Proxmox server via SSH and unpack the uploaded OVA file:
user@linux# ssh firstname.lastname@example.org root@myproxmox# cd /var/lib/vz/images root@myproxmox# /var/lib/vz/images# tar xvf virt1-demo-1.5.4.ova root@myproxmox# /var/lib/vz/images# ls virt1-demo-1.5.4-disk1.vmdk virt1-demo-1.5.4-disk2.vmdk virt1-demo-1.5.4.mf virt1-demo-1.5.4.ovf virt1-demo-1.5.4.ova root@myproxmox# /var/lib/vz/images#
Then import the two virtual disks into the virtual machine (here the VM ID
103) and your memory (default:
root@myproxmox# qm importdisk 103 virt1-demo-1.5.4-disk1.vmdk local-lvm
You can now delete the CMA file and the unpacked files.
You have now completed the VMware Proxmox-specific steps. Your appliance is now ready to start and you can begin with its basic configuration.