131 results found
This is actually a perfect use-case for TurboFloat: http://wyday.com/limelm/help/using-turbofloat/ http://wyday.com/limelm/help/vm-hypervisor-licensing/ Your app, using the TurboFloat library, will be able to run no matter whether they're using your app under a bare-metal machine or the virtual machine.
The problem with VMs is that they can be cloned bit-for-bit: https://wyday.com/limelm/help/vm-hypervisor-licensing/ So, as always, you have the choice of whether you want activations and trials to happen in virtual machines.
Not recommended for reasons stated here: https://wyday.com/limelm/help/vm-hypervisor-licensing/ 2. Tell the customer to run your app on a real machine if they want a trial of it.
When I run the Text Editor demo project I get an EVirtualMachineException stating that "The function failed because the instance of your program is running inside a virtual machine or hypervisor...", even though I am not running the program in a virtual machine.
Post by Wyatt O'Day on Sep 5, 2016Leave the "disabled VM activations" as is, and for customers running on a VM, have them use TurboFloat: https://wyday.com/limelm/help/using-turbofloat/ See more about that here: https://wyday.com/limelm/help/vm-hypervisor-licensing/
We are running into an issue where we can't launch the server inside of docker due to the hypervisor restriction. Is there any way to remove this restriction in order to enable this form of testing?
Also, VM means: Virtual Machine or Hypervisor or Sandbox or "Container" (e.g.
Answer by Wyatt O'Day on Nov 2, 2020If after unchecking them, restarting the machine, and then starting your app again and TurboActivate still says the customer is inside a virtual machine, then it's very likely they have Intel's hypervisor enabled in their BIOS. They'll need to disable it.
See: http://wyday.com/limelm/help/vm-hypervisor-licensing/ If you're using the latest version of TurboActivate, and the customer is not on a virtual machine, then tell me the product key -- that way I can actually tell you what the problem is.
Nope, Hyper-V is a hypervisor, and even the "base system" is running under the VM.
I was hoping for a "magic" solution 🤣 that somehow guarantees a unique fingerprint on virtual machines (even if it was VMware only or Hyper-V only), but I understand that isn't totally feasible without the hypervisor providing some crucial bit of uniqueness to add to the "fingerprint".
Program runs inside the virtual machine or MS HyperVisor is active. Contact ((support@ Bart's company email)) to resolve this issue."
More info: https://wyday.com/limelm/help/vm-hypervisor-licensing/
If you're just cloning a VM and TurboActivate sees the same computers as the same computers, then that's to be expected (and why we tell customers to disallow VM activations and instead use TurboFloat): https://wyday.com/limelm/help/vm-hypervisor-licensing/
See: http://wyday.com/limelm/help/vm-hypervisor-licensing/
> > https://wyday.com/limelm/help/vm-hypervisor-licensing/
It's often hard to get useful feedback as to why the trial fails to start, but could it be related to default security/hypervisor settings in Windows 11 as mentioned above?
https://wyday.com/limelm/help/vm-hypervisor-licensing/ https://wyday.com/limelm/help/licensing-types/ https://wyday.com/limelm/help/using-turbofloat/
You *can* install the TurboFloat Server on a VM, but we don't recommend it for the reasons listed in our article on virtual machines, and how to properly license your software in VMs: https://wyday.com/limelm/help/vm-hypervisor-licensing/ Recommended behavior on VMs: 1.
Licensing from inside a virtual machine or hypervisor. From the article: Another reason why you should disallow VM activations is that on certain "cloud VM providers" like Azure and Amazon Web Services, whenever you reboot the machine the VM instance is started on a different underlying physical machine, and thus the "computer fingerprint" changes.