Virtualization doesn't work with iTest?!

Question

question

simon asked Aug 6, '09 ericnute edited Aug 6, '09

Virtualization doesn't work with iTest?!

Has anyone else used a node-locked license on a virtual server e.g. Sun VirtualBox3?

I've tried 64-Bit Fedora11 and 32-Bit RHEL 5AS guests and I keep getting a "System clock as been set back!" error, even though it hasn't, and I'm syncing the host and guest and using NTP.

I've even tried an all-hosts eval license file and still get the same error, so its obviously a bogus error message.

The only way to get it to work it seems is to have my node-locked license and the eval license in the same directory, so seems more of an off-by-one bug to me than something to do with the system date - how would two licenses fix the date?!

Fanfare support say they only support RHEL 4WS and not virtualization, which seems pretty poor in this day and age; I've never found a single program that doesn't run fine under virtualization, and Hell its only Java.

After paying for support I was told to search the forums, so here I am, there's nothing about virtualization on here though.

I can't use a license server, Windows or a non-virtual host before anyone suggests that. Any other ideas?

Oh and this is on 3.4.0 and 3.4.1

Message Edited by simon on 08-06-2009 01:58 AM

iTest installation - licensing

10 |950

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 1 · 2009-08-06T17:09:40Z

AmeyaB answered Aug 6, '09 AmeyaB posted Aug 6, '09

Simon,

Sorry to hear you are having issues, I can understand your frustration.Your node-locked license should worlk on RHEL 4WS, even if it is running in a Virtual Machine. It's possible that you may have reverted the VM to a prior state previously, which may have kicked-off the time-tampering check.

Secondly, it seems odd that it works for you when you have the eval licenses in the same folder - this would seem to imply that the node-locked file is incorrect, and iTest is actually using your eval licenses (This can be confirmed by going to Help - Configure iTest Licensing). Maybe the ffhostid of that machine has now changed? This could happen in a VM.

I would recommend the following course of action:

1) Revert your VBox VM to a known state (prior to iTest ever being installed).

2) Ensure the VM and VM host times are in sync

3) Restart the VM (just to be on the safe side)

4) Run ffhostid to ensure that your locking ids are still the same as those issued in the license file

5) Install iTest, and point it to your license file.

Let me know if this still does not work for you.

4

10 |950

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

simon commented · Aug 06, 2009 at 06:45 PM

1. No I don't use snapshots.
2. They definitely are.
3. I have several times.
4. ffhostid never changes, and its the same as the license.
5. I've installed 3.4.0 then a clean install of 3.4.1 as well.

I'll have a go with RHEL 4u7 AS, I don't have WS, but that's not a longterm solution anyway, it has to at least work with 5.0 AS, preferably 5u3 AS or Fedora >= 10

When I have a look at the configure itest licensing, it generally says its using the eval one (24 days left) but sometimes says its using the node locked one (10 days left).

Any ideas?

0 ·

AmeyaB ♦ simon commented · Aug 06, 2009 at 07:17 PM

[Simon] When I have a look at the configure itest licensing, it generally says its using the eval one (24 days left) but sometimes says its using the node locked one (10 days left).

The way Flex licensing works is that it simply goes through all license files in a folder until it finds a valid license, so it could be that it is loading the files to look for licenses in a different order each time. Can you try putting the license files in different folders, and then switch to each folder in turn? This will help us isolate the faulty license file.

0 ·

simon AmeyaB ♦ commented · Aug 06, 2009 at 08:40 PM

The strange thing is that neither one license will allow the program to start, they BOTH have to be present.

It's either an off-by-one bug in FlexLM, such as a for...while loop that's starting at 1 not 0, or one of the licenses is not complete.

The eval license works on a Windows machine though, and Fanfare Support have a copy of the node-locked one and didn't comment on it being broken.

0 ·

AmeyaB ♦ simon commented · Aug 06, 2009 at 10:32 PM

That is indeed wierd. I see that Fanfare Support is now working directly with you on this, so I will ask them to get some files from your system.

0 ·

question