cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
definelicht
Adventurer
Adventurer
2,403 Views
Registered: ‎02-16-2017

License/device issue with 2017.2

Jump to solution

Hi all,

 

I'm attempting to use a cluster to build SDAccel kernels using SDx 2017.2.

I've generated node-locked licenses for both the login node and one of the compute nodes.

 

For both machines, running lmutil lmdiag gives me the expected output:

 

-----------------------------------------------------
"SDAccel" v2019.12, vendor: xilinxd
  uncounted nodelocked license, locked to ethernet address "<correct ethernet address>" no expiration date

  TS_OK: Checkout permitted when client is using terminal client

This is the correct node for this node-locked license
-----------------------------------------------------

 

However, building a kernel on the login node works, while the compute node fails with a license error:

 

****** xocc v2017.2_sdx (64-bit)
  **** SW Build 1972098 on Wed Aug 23 11:34:38 MDT 2017
    ** Copyright 1986-2017 Xilinx, Inc. All Rights Reserved.

ERROR: [XOCC 60-705] No device was found that matches 'xilinx:xil-accel-rd-ku115:4ddr-xpr:4.0'. The supported devices are:

ERROR: [XOCC 60-587] Failed to add a device: specified platform xilinx:xil-accel-rd-ku115:4ddr-xpr:4.0 is not found
WARNING: [XOCC 60-639] Failed to parse --xp option: 
ERROR: Uncaught Exception -- ERROR: [XOCC 60-400] Failed to get a license: ap_opencl

 

Running xocc --list_xdevices gives me all the expected boards on the login node, but nothing on the compute node.

Both machines run from the same filesystem on the same disks with the same user.

 

Either there is a mismatch between what "lmutil lmdiag" reports and what xocc finds, or the particular platforms are not loaded properly.

 

Does anyone know what could cause this?

 

Thanks in advance,

Johannes

0 Kudos
1 Solution

Accepted Solutions
definelicht
Adventurer
Adventurer
2,318 Views
Registered: ‎02-16-2017

@anatolihelped me isolate the issue. It comes from different naming of the MAC addresses being unsupported by older versions of FlexLM, and is described here:

https://www.xilinx.com/support/answers/60510.html

View solution in original post

0 Kudos
10 Replies
evant
Xilinx Employee
Xilinx Employee
2,375 Views
Registered: ‎09-08-2011

Hi definelicht,

 

Try this for me:

 

In the sdaccel.mk file:

 

#set target device for XCLBIN
#XDEVICE=xilinx:adm-pcie-7v3:1ddr:3.0
#XDEVICE=xilinx:xil-accel-rd-ku115:4ddr-xpr:4.0
XDEVICE=xilinx_xil-accel-rd-ku115_4ddr-xpr_4_0

 

Use this part name instead.

 

When i Used: XDEVICE=xilinx:xil-accel-rd-ku115:4ddr-xpr:4.0

 

I get: 

 

Error: Unable to find Target Device xilinx:xil-accel-rd-ku115:4ddr-xpr:4.0
make[1]: *** [run_em] Error 1
make[1]: Leaving directory `<path>/examples/vadd'
make: *** [run_cpu_em] Error 2

 

But with: 

 

XDEVICE=xilinx_xil-accel-rd-ku115_4ddr-xpr_4_0

 

****** xocc v2017.2_sdx (64-bit)
** Copyright 1986-2017 Xilinx, Inc. All Rights Reserved.

INFO: [XOCC 60-585] Compiling for software emulation target
INFO: [XOCC 60-895] Target platform: <path>/SDx/2017.2/platforms/xilinx_xil-accel-rd-ku115_4ddr-xpr_4_0/xilinx_xil-accel-rd-ku115_4ddr-xpr_4_0.xpfm
INFO: [XOCC 60-423] Target device: xilinx:xil-accel-rd-ku115:4ddr-xpr:4.0
INFO: [XOCC 60-242] Creating kernel: 'krnl_vadd'
INFO: [XOCC 60-594] Finished kernel compilation
INFO: [XOCC 60-586] Created bin_vadd_cpu_emu.xclbin
INFO: [XOCC 60-791] Total elapsed time: 0h 0m 20s
XCL_EMULATION_MODE=sw_emu ./vadd bin_vadd_cpu_emu.xclbin

Loading: 'bin_vadd_cpu_emu.xclbin'
TEST PASSED

This is with the vadd example in 2017.2 install directory to try this out.

 

I did the following commands to build:

 

/examples/vadd> make -f sdaccel.mk cleanall

/examples/vadd> make -f sdaccel.mk run_cpu_em

 

See if that does anything for you.

If at first you don't succeed, try redefining success?
0 Kudos
definelicht
Adventurer
Adventurer
2,353 Views
Registered: ‎02-16-2017

Hey evant,

 

Thank you for your suggestion.

 

Unfortunately this gives me the same error:

****** xocc v2017.2_sdx (64-bit)
  **** SW Build 1972098 on Wed Aug 23 11:34:38 MDT 2017
    ** Copyright 1986-2017 Xilinx, Inc. All Rights Reserved.

ERROR: [XOCC 60-705] No device was found that matches 'xilinx_xil-accel-rd-ku115_4ddr-xpr_4_0'. The supported devices are:

ERROR: [XOCC 60-587] Failed to add a device: specified platform xilinx_xil-accel-rd-ku115_4ddr-xpr_4_0 is not found
WARNING: [XOCC 60-639] Failed to parse --xp option: 
ERROR: Uncaught Exception -- ERROR: [XOCC 60-400] Failed to get a license: ap_opencl

In general, the list of supported devices is empty.

0 Kudos
evant
Xilinx Employee
Xilinx Employee
2,344 Views
Registered: ‎09-08-2011

Can you send a screen shot of your VLM on the machine you are running showing the feature?

 

Just to verify that you are able to see that the license is there, and it is considered valid from the machine you are trying to run. Please make sure you remove any HOSTID values or other info not for sharing.

 

 

If at first you don't succeed, try redefining success?
0 Kudos
definelicht
Adventurer
Adventurer
2,339 Views
Registered: ‎02-16-2017

Hey evant,

 

Unfortunately I have no graphical access to the compute node (I don't even think it's running an X server), so I'll have to stick to command line tools.

Is there any other way than lmutil lmdiag?

 

Here is the full output of the command:

 

-----------------------------------------------------
"SDAccel" v2019.12, vendor: xilinxd
  uncounted nodelocked license, locked to ethernet address "<correct MAC address>" no expiration date

  TS_OK: Checkout permitted when client is using terminal client

This is the correct node for this node-locked license
-----------------------------------------------------

Enter <CR> to continue:
"PartialReconfiguration" v2019.12, vendor: xilinxd
  uncounted nodelocked license, locked to ethernet address "<correct MAC address>" no expiration date

  TS_OK: Checkout permitted when client is using terminal client

This is the correct node for this node-locked license
-----------------------------------------------------

Enter <CR> to continue:
"Simulation" v2019.12, vendor: xilinxd
  uncounted nodelocked license, locked to ethernet address "<correct MAC address>" no expiration date

  TS_OK: Checkout permitted when client is using terminal client

This is the correct node for this node-locked license
-----------------------------------------------------

Enter <CR> to continue:
"Implementation" v2019.12, vendor: xilinxd
  uncounted nodelocked license, locked to ethernet address "<correct MAC address>" no expiration date

  TS_OK: Checkout permitted when client is using terminal client

This is the correct node for this node-locked license
-----------------------------------------------------

Enter <CR> to continue:
"Analyzer" v2019.12, vendor: xilinxd
  uncounted nodelocked license, locked to ethernet address "<correct MAC address>" no expiration date

  TS_OK: Checkout permitted when client is using terminal client

This is the correct node for this node-locked license
-----------------------------------------------------

Enter <CR> to continue:
"HLS" v2019.12, vendor: xilinxd
  uncounted nodelocked license, locked to ethernet address "<correct MAC address>" no expiration date

  TS_OK: Checkout permitted when client is using terminal client

This is the correct node for this node-locked license
-----------------------------------------------------

Enter <CR> to continue:
"Synthesis" v2019.12, vendor: xilinxd
  uncounted nodelocked license, locked to ethernet address "<correct MAC address>" no expiration date

  TS_OK: Checkout permitted when client is using terminal client

This is the correct node for this node-locked license
-----------------------------------------------------

Enter <CR> to continue:
"ap_opencl" v2019.12, vendor: xilinxd
  uncounted nodelocked license, locked to ethernet address "<correct MAC address>" no expiration date

  TS_OK: Checkout permitted when client is using terminal client

This is the correct node for this node-locked license
-----------------------------------------------------
-----------------------------------------------------
License file: /users/definelj/Xilinx_Greina22_1.lic
-----------------------------------------------------
"SDAccel" v2019.12, vendor: xilinxd
  uncounted nodelocked license, locked to ethernet address "<correct MAC address>" no expiration date

  TS_OK: Checkout permitted when client is using terminal client

This is the correct node for this node-locked license
-----------------------------------------------------

Enter <CR> to continue:
"PartialReconfiguration" v2019.12, vendor: xilinxd
  uncounted nodelocked license, locked to ethernet address "<correct MAC address>" no expiration date

  TS_OK: Checkout permitted when client is using terminal client

This is the correct node for this node-locked license
-----------------------------------------------------

Enter <CR> to continue:
"Simulation" v2019.12, vendor: xilinxd
  uncounted nodelocked license, locked to ethernet address "<correct MAC address>" no expiration date

  TS_OK: Checkout permitted when client is using terminal client

This is the correct node for this node-locked license
-----------------------------------------------------

Enter <CR> to continue:
"Implementation" v2019.12, vendor: xilinxd
  uncounted nodelocked license, locked to ethernet address "<correct MAC address>" no expiration date

  TS_OK: Checkout permitted when client is using terminal client

This is the correct node for this node-locked license
-----------------------------------------------------

Enter <CR> to continue:
"Analyzer" v2019.12, vendor: xilinxd
  uncounted nodelocked license, locked to ethernet address "<correct MAC address>" no expiration date

  TS_OK: Checkout permitted when client is using terminal client

This is the correct node for this node-locked license
-----------------------------------------------------

Enter <CR> to continue:
"HLS" v2019.12, vendor: xilinxd
  uncounted nodelocked license, locked to ethernet address "<correct MAC address>" no expiration date

  TS_OK: Checkout permitted when client is using terminal client

This is the correct node for this node-locked license
-----------------------------------------------------

Enter <CR> to continue:
"Synthesis" v2019.12, vendor: xilinxd
  uncounted nodelocked license, locked to ethernet address "<correct MAC address>" no expiration date

  TS_OK: Checkout permitted when client is using terminal client

This is the correct node for this node-locked license
-----------------------------------------------------

Enter <CR> to continue:
"ap_opencl" v2019.12, vendor: xilinxd
  uncounted nodelocked license, locked to ethernet address "<correct MAC address>" no expiration date

  TS_OK: Checkout permitted when client is using terminal client

This is the correct node for this node-locked license
-----------------------------------------------------

 

0 Kudos
evant
Xilinx Employee
Xilinx Employee
2,318 Views
Registered: ‎09-08-2011

Hi Definelicht,

 

   This is interesting.

 

I see the feature: Enter <CR> to continue: "ap_opencl" v2019.12, vendor: xilinxd uncounted nodelocked license, locked to ethernet address "<correct MAC address>" no expiration date TS_OK: Checkout permitted when client is using terminal client This is the correct node for this node-locked license ----------------------------------------------------- -----------------------------------------------------

 

Is this license loaded onto the specific machine? This isn't a floating license? And you have two node locked licenses on this same machine?

 

Do you have anything set in your XILNXD_LICENSE_FILE or your LM_LICENSE_FILE variables?

 

What version of FlexLM are you using? What happens if you install the latest version of SDx? Are any of the Machines VMs? Are there any older versions of the ap_opencl license? Is the MAC address not listed as all 0's?

 

It's a little odd that it can't see this license as on the surface it does seem to be present. Answer what you can above and maybe it might highlight something we didn't catch yet.

 

 

 

If at first you don't succeed, try redefining success?
0 Kudos
definelicht
Adventurer
Adventurer
2,237 Views
Registered: ‎02-16-2017

Hey evant,

 

Thanks for looking into this.

Your questions, one by one:

 

> Is this license loaded onto the specific machine? This isn't a floating license? And you have two node locked licenses on this same machine?

 

The machines use the same filesystem, so my home folder is mounted on both. Because of this, I have multiple node-nocked licenses tied to different machines present.

I have already tried removing the other licenses from my home folder, but with the same result.

 

> Do you have anything set in your XILNXD_LICENSE_FILE or your LM_LICENSE_FILE variables?

 

I tried both pointing it to the correct license and leaving it empty. It does not seem to make a difference.

 

> What version of FlexLM are you using?

 

These are node-locked licenses, does that involve any local version of FlexLM? (not sure how this works)

lmgrd does not seem to give me a version number.

 

> What happens if you install the latest version of SDx?

 

2017.4 does not seem to support my device (TUL KU115), so upgrading is unfortunately not an option :-(

 

> Are any of the Machines VMs?

 

No, they are physical machines.

 

> Are there any older versions of the ap_opencl license?

 

Would that show up with lmutil lmdiag? I have had 2017.1 on the machine before, but there are at least no licenses present in my home directory.

 

> Is the MAC address not listed as all 0's?

 

That MAC address is not all 0's, and I verified with the sysadmin that this is the correct address to use. The machine has two MAC addresses (I guess two network cards), and I installed node-locked licenses for both just in case.

 

> It's a little odd that it can't see this license as on the surface it does seem to be present. Answer what you can above and maybe it might highlight something we didn't catch yet.

 

Yes, it's quite strange. Is there a possibility that the output from lmutil does not match what xocc detects?

0 Kudos
definelicht
Adventurer
Adventurer
2,253 Views
Registered: ‎02-16-2017

Hey evant,

 

Thanks for following up on this.

To answer your questions:

 

> Is this license loaded onto the specific machine? This isn't a floating license?

 

It's a node-locked license. I'm not running any floating license server.

 

> And you have two node locked licenses on this same machine?

 

They are separate machines, but yes, in the sense that they both mount the same home partition/filesystem where the licenses are located.

I have tried removing other licenses and only keeping the one specific for the machine, but this didn't help.

 

> Do you have anything set in your XILNXD_LICENSE_FILE or your LM_LICENSE_FILE variables?

 

I tried both having it point to the specific license file, and to leave it empty, but to no avail.

 

> What version of FlexLM are you using?

 

Is any local version of FlexLM being used for a node-locked license? (I'm not sure how this works)

The lmgrd I found on the machine does not seem to report a version number, but the copyright stated is until 2013, so not brand new.

 

> What happens if you install the latest version of SDx?

 

SDx 2017.4 does not seem to support my device (TUL KU115), so this is unfortunately not an option :-(

 

> Are any of the Machines VMs?

 

No, they are both physical machines, with physical MAC addresses (I checked with the sysadmin to be sure). The compute node has two network cards, and I even generated licenses for both (also didn't help).

 

> Are there any older versions of the ap_opencl license?

 

There's no .lic-file present in $HOME, but I've had SDx 2017.1 on these machines before. Would this be reported by lmutil lmdiag?

 

> Is the MAC address not listed as all 0's?

 

The MAC address is not all 0's, and I checked with the sysadmin that the address is correct.

 

> It's a little odd that it can't see this license as on the surface it does seem to be present. Answer what you can above and maybe it might highlight something we didn't catch yet.

 

Yes, it's quite odd. Is there any chance that there's a mismatch between what lmutil lmdiag reports and what xocc uses?

0 Kudos
anatoli
Moderator
Moderator
2,245 Views
Registered: ‎06-14-2010

Hello @definelicht,

 

Please generate and share your Xinfo report (generated on the machine where you are seeing this licensing error), for examination. Thanks

 

xinfo report (xinfo.txt) can be generated by running the "report_environment –file xinfo.txt" command in Vivado TCL console.

Kind Regards,
Anatoli Curran,
Xilinx Technical Support
------------------------------------------------------------------------------------------------

Don’t forget to reply, kudo, and accept as solution.

If starting with Versal, take a look at our Versal Design Process Hub and our
Versal Blogs

------------------------------------------------------------------------------------------------
0 Kudos
definelicht
Adventurer
Adventurer
2,169 Views
Registered: ‎02-16-2017

Hi Anatoli,

 

To avoid having to comb throught the file to remove information that should perhaps not be public, I've sent the xinfo.txt to you in a private message.

 

Appreciate the effort,

- Johannes

0 Kudos
definelicht
Adventurer
Adventurer
2,319 Views
Registered: ‎02-16-2017

@anatolihelped me isolate the issue. It comes from different naming of the MAC addresses being unsupported by older versions of FlexLM, and is described here:

https://www.xilinx.com/support/answers/60510.html

View solution in original post

0 Kudos