- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Has anyone had any issues using virtual machines and certain altera licences? At work we had Quartus licences that worked fine on all machines. Then we got a load more, and the new ones refuse to work on the VM machines, while working fine on the non VMs, with the following warning and error:
Warning: FLEXlm software error: System clock has been set back Feature: quartus License path: 2100@fs4:1717@fs1:1717@fs3:1717@fm5:1717@fs4 FLEXlm error: -88,309 For further information, refer to the FLEXlm End User Manual, available at "www.macrovision.com". Error: Current license file does not support the EP4SGX230FF35I3 device VMs run CentOS 6.4, with the "working" machines running CentOS 5.5 and 5.6. Anyone any ideas?Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It seems to be complaining about the system clock within the VM.
Apparently, the RTC is a common enough topic that VMWare wrote a document dedicated to it: http://www.vmware.com/files/pdf/techpaper/timekeeping-in-virtualmachines.pdf It kind of sounds like FLexLM is having a problem possibly similar to the issue discussed in "Test Operating System Clock Against CMOS TOD Clock" of that PDF.- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
One thing I just noticed, we have no problems running synthesis, its just the fitter that it has problems with.

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page