131 results found
Can't activate within a virtual machine or a hypervisor. Run this floating license server on a real hardware.”
As far as downside of using TA on a VM, it’s covered here: https://wyday.com/limelm/help/vm-hypervisor-licensing/
“The function failed because this instance of your program is running inside a virtual machine or hypervisor.”
This is more and more common as people tend to install machine learning containers… Problem is as soon as you installl docker, it enables Hypervisor. Turning it off means breaking docker engine… which is not a very good reply to give to customers.
And when we want to activate our software it says "you cannot activate inside a Virtual machine or hypervisor". What can I do?
During activation they receive the error: "Can't activate within a virtual machine or a hypervisor. Run this floating license server on real hardware" Now apparently they are neither working in a VM, not have the Hyper-V Option in windows enabled.
References: Types of software licensing: https://wyday.com/limelm/help/licensing-types/ Licensing from inside a virtual machine or hypervisor: https://wyday.com/limelm/help/vm-hypervisor-licensing/
The solution, use TurboFloat: https://wyday.com/limelm/help/vm-hypervisor-licensing/ It handles cases like this.
https://wyday.com/limelm/help/vm-hypervisor-licensing/
To confirm, is it the case that free trials will reset following reboot on any windows computer with VM settings (e.g. hypervisor) enabled? It depends.
After running a trial of the licensed software, I am getting a VM detected message ("Failed to start the trial: The function failed because this instance of your program is running inside a virtual machine / hypervisor and you've prevented the function from running inside a VM.").
Hi,I've installed turbofloat [Server] on my Windows machine that host HyperV virtual machine, so hypervisor is enabled. Every two weeks my license will be deactivated, and I know that this is the reason, as written in the documentation.My question is: this behavior only affect installation on Windows ?
Post by Wyatt O'Day on Mar 17, 2020Longer answer: yes, you'll get that problem (as well as other problems) as described in the documentation: https://wyday.com/limelm/help/vm-hypervisor-licensing/ Instead, either use the TFS on a real machine.
We describe that in the article, but we don't explicitly tie it to trials: https://wyday.com/limelm/help/vm-hypervisor-licensing/ To disallow VMs in your LimeLM account and use TA_DISALLOW_VM in your app when you use TA_UseTrial().
Types of software licensingLicensing from inside a virtual machine or hypervisor
However, he sent a screenshot where TurboActivate.exe indicates - You cannot activate GPT Tools inside a virtual machine or a hypervisor. Please use a real computer. The user claims that he has a real computer and also tried disabling antivirus, etc.
You have the option of enabling or disabling activations in Virtual Machines: https://wyday.com/limelm/help/vm-hypervisor-licensing/ If what you're saying is that the customer is claiming they're not inside a VM, then see our FAQ: https://wyday.com/limelm/help/faq/#in-vm If you've followed that FAQ, you're using the latest version of TurboActivate, and you still believe TurboActivate is not correctly detecting the machine as a VM or not as a VM, then you need to provide useful information: https://wyday.com/limelm/help/faq/#useful-reports
If you're in a VM, make sure you allow VMs in the LimeLM interface (obviously, don't do that for production): https://wyday.com/limelm/help/vm-hypervisor-licensing/ Also, make sure you're using the verified trials when calling the TA_UseTrial() function.
The first case was you running under a hypervisor. Hypervisors are a special type of a VM where even the "host" operating system is techinally on a VM.
Hello,LimeLM works great for me so far but one user kept getting error code 17 which is described in TurboActivate.h as: MessageId: TA_E_IN_VM MessageText: The function failed because this instance of your program if running inside a virtual machine / hypervisor and you've prevented the function from running inside a VM.