Date: Fri, 29 Mar 2024 13:58:54 +0100 (CET) Message-ID: <2096599684.5420.1711717134549@confluence-server> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_5419_1128681457.1711717134549" ------=_Part_5419_1128681457.1711717134549 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The= information on this page refers to LM-X License Manager 5.4 or newer, whic= h introduced support for Xen virtualization detection and introduced the CL= OUD sharing type. If = you are running a previous version of License Statistics, please see <= /span>docu= mentation for previous versions. |
Licensing your software to run on = virtual machines or in a cloud environment carries special considerations, = as described below.
You can install a license server o= n a virtual machine. To do this, enable support for virtual machines in the= license file.
By default, LM-X denies all checkouts=
for local licenses in virtual environments, and refuses to load licenses o=
n license servers to prevent potential license overuse. Virtualization dete=
ction is officially supported for VMware=
, Microsoft Hyper-V, VirtualBox, KVM, QEMU, and Xen.
Virtual machine environments are typi= cally undesirable for use with software licensing. Normally, operating syst= ems running in virtual environments are designed to be hardware independent= , so Ethernet or harddisk HostIDs no longer specify physical hardware ident= ifiers. Duplicating the virtual machines and modifying the HostIDs is simpl= e and takes minutes to perform.
However, you may choose to explicitly= allow your application to run in a virtual environment (for example, limit= ed to use by trusted and enterprise customers) by specifying the SHARE= a> keyword VIRTUAL for the particular feature (see FEATURE settings for details on setting the virtual share option in your license.)
You may also allow trial licenses to = run on a virtual machine using= LMX_OPT_TRIAL_VIRTU= AL_MACHINE, described in LMX_SetOption.
There are a number of ways that LM= -X makes it safe for you to deliver your application for use on virtual mac= hines:
LM-X End-user Utility v3.4
=
Copyright (C) 2002-2016 X-Form=
ation. All rights reserved.
BIOS: Phoenix Technologies LTD - UNKNOWN
Hostid: VMware-42321a30c22ce364-aca97bac=
6ea0bdb8
You may choose to explicitly allow yo= ur application to run in a virtual environment (for example, limited to use= by trusted and enterprise customers) by specifying the SHARE&nb= sp;keyword CLOUD for the particular feature (see <= a href=3D"https://docs.x-formation.com/display/LMX/FEATURE+settings" rel=3D= "nofollow">FEATURE settings for details on setting th= e cloud share option in your license.)
You may also allow trial licenses to = run on a virtual machine using= LMX_OP= T_TRIAL_CLOUD_HOST, described in LMX_SetOption.<= /p>
When using Amazon EC2, Microsoft Azure, or Google Compute Engine (GCE), yo= u can use the Instance ID for the HostID (see HostID values).= However, for other cloud service provid= ers, virtual machines do not have HostIDs. To solve this problem:
Licenses created using v5.4 and newer can use either or both of the VIRTUAL or CLOUD share options. Using the VI= RTUAL option allows your application to be licensed on virtual platforms, b= ut not in the cloud (AWS, Azure, GCE). Using the CLOUD option allo= ws your application to be licensed on cloud platforms, which adds more flex= ibility to licensing modes.
For backward compatibility, licenses created using LM-X License Manager = versions older than v5.4 will continue to use the share option VIRTUAL, whi= ch includes both virtual machine environments and cloud environments. =