Live Migration on VMs

Hello, I have a client who is using a Floating Licence for their Virtual Machines. However whenever a live migration happens the product crashes and will continue to crash until they reboot the VM.

I suspect this is an issue with the Floating Licence, are the floating licences able to adapt to a live migration?

I'm assuming the lease from the Licensing server is tied to the pre-migration physical machine and when the post-migration physical machine takes over the lease is no longer valid.

Is this the case and are there any solutions?

Hey David, more information is needed: https://wyday.com/limelm/help/faq/#useful-reports

1. What do you mean by "live migration" -- can you give us a reproducible example.2. What version of TF?3. Static or dynamic?4. What do you mean by "crash" (do you mean error message, error code, or an actual crash). Again, more information -- full stack trace, full error code, exactly what method, etc., etc.

Hi Wyatt,

1. The user is logged into a Virtual Machine, the physical machine that is behind that Virtual Machine is migrated to a different physical machine without disconnecting the user.

2. 4.0.9.6

3. What do you mean by Static or dynamic? In reference to what exactly?

4. I will ask the client for more information on this but it is an actual crash of the program with the generic "X has stopped working window." Until the the Virtual Machine is rebooted the program will crash every time it is launched.

>> "1. The user is logged into a Virtual Machine, the physical machine that is behind that Virtual Machine is migrated to a different physical machine without disconnecting the user."

I was looking for an example. I get the concepts. But each VM has its own laundry list of critical bugs. And "moving VMs" (live or not) is a fraught area.

>> "3. What do you mean by Static or dynamic? In reference to what exactly?"

Static or dynamic version of TurboActivate. DLL vs lib. .so vs .a, etc.

>> "4. I will ask the client for more information on this but it is an actual crash of the program with the generic "X has stopped working window." Until the the Virtual Machine is rebooted the program will crash every time it is launched."

Yeah. Without more information it's hard to say what it is. It could be a thousand different things.

What OS are they on? Is it the latest? Is the VM software the latest? If not, start there. No use in tracking down bugs that others have already fixed.