131 results found
Hi,We don't normally allow our software to activate a trial in a hypervisor. However, we would like to allow it internally for test purposes.
* Operating system is Centos 7* License is not expired* License allows hypervisor/vm activations* Using TurboActivate 4* System time in VM is up to date* System time on host is up to date
The actual solution is to use TurboFloat: https://wyday.com/limelm/help/vm-hypervisor-licensing/ If you just all TA activations in VMs it might work for a little while.
The problems you're having with any node-locked licensing on VMs, and the solution to said problem is described here: https://wyday.com/limelm/help/vm-hypervisor-licensing/ >> "Now, I enforce checking the License every 0 (for VMs, 30 for real PC *) days on the Internet.
We've read that one for years now and will only believe it when I see itTurn off hypervisor and use TA is not possible in modern days as developer frequently use Docker and Microsoft is actively pushing for Windows Subsystem for Linux which is gaining traction from a lot of our users
Or follow our recommendations for selling to customers running under VMs: http://wyday.com/limelm/help/vm-hypervisor-licensing/ We give you lots of choices.
It doesn't matter if they call it something else (Hypervisor) or if they enable the VM based on certain settings.
We actually cover this in Licensing from inside a virtual machine or hypervisor; Step 2. Use floating licenses (TurboFloat): One way to do this is to use the UseTrial(TA_DISALLOW_VM) function.
For the same reason you should disallow VM activations (VMs can be cloned): https://wyday.com/limelm/help/vm-hypervisor-licensing/ >> "- You're planning to host TurboFloat instances" Yes, hosted TurboFloat Server instances will be available later this year.
To confirm, is it the case that free trials will reset following reboot on any windows computer with VM settings (e.g. hypervisor) enabled? As such, we are planning to remove the free-trial capabilities.
I keep getting an error message saying: "You cannot activate MC360 NBT Editor inside a virtual machine or a hypervisor .Please use a real computer." Here's my Laptop Specifications:Brand AsusScreen Size 15.6-InchScreen Resolution 136668Touchscreen NoIPS Display Tech NoProcessor Intel Core i3-3217U Ivy Bridge Dual-Core 1.8GHz 3MB Cache (~2,300 PassMark benchmark points)Graphics Intel HD 4000RAM 4GBStorage 500GB HDD (Upgraded to 1TB)Optical Drive DVD WriterInput Non-Backlit Keyboard with Numeric Pad, Multi-Touch Trackpad with Integrated ButtonsCameras FrontSpeakers Stereo SpeakersWi-Fi 802.11NBluetooth NoEthernet LAN YesUSB 1 x USB 3.0 + 1 x USB 2.0Video Ports 1 x HDMI + 1 x VGAMedia Card Reader YesBattery 4-CellWeight 5.1 poundsHeight 1.2?
This is described here: https://wyday.com/limelm/help/vm-hypervisor-licensing/ #2. How you solve this is up to you.
Longer answer: if you do it, understand the risks: https://wyday.com/limelm/help/vm-hypervisor-licensing/ Note the part of that article that actually applies to you -- besides all of it: "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.
Security implications are here: https://wyday.com/limelm/help/vm-hypervisor-licensing/ Short answer: if you enable VM activations the customer gets infinite licenses.
See: https://wyday.com/limelm/help/vm-hypervisor-licensing/
Post by a guest on Nov 18, 2016See:> https://wyday.com/limelm/help/vm-hypervisor-licensing/ Unfortunately, this is not a possible solution for us 🙁 Thanks for your response
See: Licensing from inside a virtual machine or hypervisor So you have 2 choices for customers running on EC2: 1.
I Try again and then I get the following message : "You cannot activate Xeocoder inside a virtual machine or a hypervisor. Please use a real computer."- If I keep trying with this key I get all the time this messageIt doesn't make sense since the VM activation is allowed, and was working fine previously.So, is there an issue with a service pack, or any windows xp update, or is there any problem related to the changes I made on the lime lm server side ?
SWActivation — TA_UseTrial failed: hr = Oxll2024-10-28 [Ox00000c64] DEBUG *software name*.SWActivation - 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.
Here's are the specs running the turbofloatserver software: lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 46 bits physical, 48 bits virtual CPU(s): 1 On-line CPU(s) list: 0 Thread(s) per core: 1 Core(s) per socket: 1 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 63 Model name: Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz Stepping: 2 CPU MHz: 2400.059 BogoMIPS: 4800.01 Hypervisor vendor: Xen Virtualization type: full L1d cache: 32 KiB L1i cache: 32 KiB L2 cache: 256 KiB L3 cache: 30 MiB NUMA node0 CPU(s): 0 Vulnerability Itlb multihit: KVM: Mitigation: VMX unsupported Vulnerability L1tf: Mitigation; PTE Inversion Vulnerability Mds: Vulnerable: Clear CPU buffers attempted, no microcode; SMT Host state unknown Vulnerability Meltdown: Mitigation; PTI Vulnerability Spec store bypass: Vulnerable Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization Vulnerability Spectre v2: Mitigation; Retpolines, STIBP disabled, RSB filling Vulnerability Srbds: Not affected Vulnerability Tsx async abort: Not affected Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx rdtscp lm constant_tsc rep_good nopl xtopology cpuid tsc_known_freq p ni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm cpuid_fault invpcid_single pti fsgsbase bmi1 a vx2 smep bmi2 erms invpcid xsaveopt Since I cannot reproduce the error reliably, any pointers for troubleshooting are appreciated!