Having problem when install SGX PSW 2.1.3 on Centos 7

[das__batsayan]

I got the following error during the installation of sgx PSW ( in Intel(R) Xeon(R) CPU E3-1275 v6 @ 3.80GHz, kernel 3.10.0-862.2.3.el7.x86_64). Thanks in advance for any help. 

[pts/0][05:53:00:e142679@localhost ] ~/sgx_repo/sgx213>sudo ./sgx_linux_x64_psw_2.1.103.44322.bin
Unpacking Intel SGX PSW Package ... done.
Verifying the integrity of the install package ... done.
Installing Intel SGX PSW Package ... done.
/tmp/sgx-psw-MGvlGD /home/e142679/sgx_repo/sgx213
install -d /opt/intel/sgxpsw
install -d /opt/intel/sgxpsw/scripts
install -d /usr/lib64
cp -r package/* /opt/intel/sgxpsw
install scripts/* /opt/intel/sgxpsw/scripts
mv /opt/intel/sgxpsw/lib64/libsgx_uae_service.so /usr/lib64
mv /opt/intel/sgxpsw/lib64/libsgx_urts.so /usr/lib64
rmdir /opt/intel/sgxpsw/lib64
/home/e142679/sgx_repo/sgx213
Installing aesmd.service service ...Created symlink from /etc/systemd/system/multi-user.target.wants/aesmd.service to /usr/lib/systemd/system/aesmd.service.
 done.
iclsInit() returned error.
Trusted platform service is unavailable. Check log in /opt/Intel/iclsClient/log/iclsClient.log.
Job for aesmd.service failed because the control process exited with error code. See "systemctl status aesmd.service" and "journalctl -xe" for details.

[pts/0][06:09:03:e142679@localhost ] ~/sgx_repo/sgx213>tail -f /opt/Intel/iclsClient/log/iclsClient.log
2018-05-24 05:53:07:247 00007ffa05838740 iclsClient:Closing config file
2018-05-24 05:53:07:247 00007ffa05838740 iclsClient:[INF] [N/A] PCH DID=a149
2018-05-24 05:53:07:247 00007ffa05838740 iclsClient:[DBG] [N/A] MCH:ICH / PCH device NOT found on the list of eligible devices.
2018-05-24 05:53:07:247 00007ffa05838740 iclsClient:[INF] [N/A] PCH DID=a149
2018-05-24 05:53:07:247 00007ffa05838740 iclsClient:[DBG] [N/A] MCH:ICH / PCH device NOT found on the list of eligible devices.
2018-05-24 05:53:07:247 00007ffa05838740 iclsClient:CreateMeiAccess: [INF] [N/A] DETECTED_PLATFORM: 0x0c [SKL]
2018-05-24 05:53:07:247 00007ffa05838740 iclsClient:CreateHeciCaller: [DBG] CreatingHeciCaller. Config addr: 94531845855728
2018-05-24 05:53:07:247 00007ffa05838740 iclsClient:CreateHeciCaller: [INF] [N/A] Using MalCommandLocal
2018-05-24 05:53:07:247 00007ffa05838740 iclsClient:initializeMeiAccessSingleton: [ERR] [N/A] Exception occurred when initializing MeiAccess singleton=Both MEI and HECI device driver's are missing.:
2018-05-24 05:53:07:247 00007ffa05838740 iclsClient:iclsInit: [ERR] iclsInit: initializeMeiAccessSingleton returned error. Status: STATUS_ERROR.

[Hoang_N_Intel]

This error simply indicates that the MEI driver is not available on Intel Xeon E3 Can you check to see whether the Intel SGX PSW service is still up and running.

Can you post the output of its status by issuing the following command:

$ sudo systemctl status aesmd

or

$ sudo service aesmd status

[huiqiang__zhang]

@Hoang Nguyen (Intel),I met the same error.

aesmd.service - Intel(R) Architectural Enclave Service Manager
   Loaded: loaded (/lib/systemd/system/aesmd.service; enabled; vendor preset: enabled)
   Active: active (running) since 二 2019-01-15 23:46:03 CST; 2min 55s ago
 Main PID: 5385 (aesm_service)
   CGroup: /system.slice/aesmd.service
           └─5385 /opt/intel/libsgx-enclave-common/aesm/aesm_service

1月 15 23:46:03 sgx_vm systemd[1]: Starting Intel(R) Architectural Enclave Service Manager...
1月 15 23:46:03 sgx_vm systemd[1]: Started Intel(R) Architectural Enclave Service Manager.
1月 15 23:46:03 sgx_vm aesm_service[5385]: [ADMIN]White List update requested
1月 15 23:46:03 sgx_vm aesm_service[5385]: The server sock is 0x5560b27519a0
1月 15 23:46:03 sgx_vm aesm_service[5385]: [ADMIN]Platform Services initializing
1月 15 23:46:03 sgx_vm aesm_service[5385]: [ADMIN]Platform Services initialization failed due to DAL error
1月 15 23:46:30 sgx_vm systemd[1]: Started Intel(R) Architectural Enclave Service Manager.
 

[huiqiang__zhang]

I try it again. the info:

root@sgxvm:/opt/sgx_main/intel-sgx/linux-2.4/ubuntu16.04-server# sudo systemctl status aesmd
● aesmd.service - Intel(R) Architectural Enclave Service Manager
   Loaded: loaded (/lib/systemd/system/aesmd.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since 五 2019-01-18 16:18:27 CST; 10s ago
  Process: 4120 ExecStart=/opt/intel/libsgx-enclave-common/aesm/aesm_service (code=exited, status=0/SUCCESS)
  Process: 4117 ExecStartPre=/bin/chmod 0755 /var/run/aesmd/ (code=exited, status=0/SUCCESS)
  Process: 4114 ExecStartPre=/bin/chown -R aesmd:aesmd /var/run/aesmd/ (code=exited, status=0/SUCCESS)
  Process: 4111 ExecStartPre=/bin/mkdir -p /var/run/aesmd/ (code=exited, status=0/SUCCESS)
  Process: 4105 ExecStartPre=/opt/intel/libsgx-enclave-common/aesm/linksgx.sh (code=exited, status=0/SUCCESS)
 Main PID: 4121 (code=exited, status=1/FAILURE)

1月 18 16:18:27 sgxvm systemd[1]: aesmd.service: Unit entered failed state.
1月 18 16:18:27 sgxvm systemd[1]: aesmd.service: Failed with result 'exit-code'.
 

[huiqiang__zhang]

root@sgxvm:/opt/sgx_main/intel-sgx/linux-2.4/ubuntu16.04-server# journalctl -o verbose _PID=4121
-- Logs begin at 五 2019-01-18 16:07:53 CST, end at 五 2019-01-18 16:25:34 CST. --
五 2019-01-18 16:18:27.776808 CST [s=7c8b6becc9474487bcc6fecc0dbf7efe;i=601;b=c08894cce9e0424fbf1013df249abf27;m=25e78d46;t=57fb727d835e1;x=e5f96ef915e996b]
    _SYSTEMD_SLICE=system.slice
    _BOOT_ID=c08894cce9e0424fbf1013df249abf27
    _MACHINE_ID=0d2ab8d7aecb4c1ba84e70e0a4efe7c4
    _HOSTNAME=sgxvm
    _TRANSPORT=syslog
    SYSLOG_FACILITY=1
    _CAP_EFFECTIVE=0
    PRIORITY=2
    SYSLOG_IDENTIFIER=aesm_service
    MESSAGE=SGX Service unavailable    
    _UID=999
    _GID=999
    _COMM=aesm_service
    _EXE=/opt/intel/libsgx-enclave-common/aesm/aesm_service
    _CMDLINE=/opt/intel/libsgx-enclave-common/aesm/aesm_service
    _SYSTEMD_CGROUP=/system.slice/aesmd.service
    _SYSTEMD_UNIT=aesmd.service
    SYSLOG_PID=4121
    _PID=4121
    _SOURCE_REALTIME_TIMESTAMP=1547799507776808
五 2019-01-18 16:18:27.776823 CST [s=7c8b6becc9474487bcc6fecc0dbf7efe;i=602;b=c08894cce9e0424fbf1013df249abf27;m=25e78de7;t=57fb727d83682;x=3c734b41df5dc46f]
    _SYSTEMD_SLICE=system.slice
    _BOOT_ID=c08894cce9e0424fbf1013df249abf27
    _MACHINE_ID=0d2ab8d7aecb4c1ba84e70e0a4efe7c4
    _HOSTNAME=sgxvm
    PRIORITY=3
    _TRANSPORT=syslog
    SYSLOG_FACILITY=1
    _CAP_EFFECTIVE=0
    SYSLOG_IDENTIFIER=aesm_service
    _UID=999
    _GID=999
    _COMM=aesm_service
    _EXE=/opt/intel/libsgx-enclave-common/aesm/aesm_service
    _CMDLINE=/opt/intel/libsgx-enclave-common/aesm/aesm_service
    _SYSTEMD_CGROUP=/system.slice/aesmd.service
    _SYSTEMD_UNIT=aesmd.service
    MESSAGE=Fail to start service.
    SYSLOG_PID=4121
    _PID=4121
    _SOURCE_REALTIME_TIMESTAMP=1547799507776823
why SGX Service unavailable  ?

[huiqiang__zhang]

root@sgxvm:/opt/sgx_main/intel-sgx/linux-2.4/ubuntu16.04-server# sudo service jhi status
● jhi.service - Intel Dynamic Application Loader Host Interface (JHI)
   Loaded: loaded (/lib/systemd/system/jhi.service; enabled; vendor preset: enabled)
   Active: active (running) since 五 2019-01-18 16:47:56 CST; 2min 34s ago
 Main PID: 8400 (jhid)
   CGroup: /system.slice/jhi.service
           └─8400 /usr/sbin/jhid

1月 18 16:48:09 sgxvm jhi[8400]: Error: discoverVmType() failed
1月 18 16:48:09 sgxvm jhi[8400]: JHI init failed
1月 18 16:48:09 sgxvm jhi[8400]: JHI service release prints are enabled
1月 18 16:48:09 sgxvm jhi[8400]: AppletsManager::discoverVmType(), Couldn't connect to either BHv1 or BHv2.
1月 18 16:48:09 sgxvm jhi[8400]: Error: discoverVmType() failed
1月 18 16:48:09 sgxvm jhi[8400]: JHI init failed
1月 18 16:48:09 sgxvm jhi[8400]: JHI service release prints are enabled
1月 18 16:48:09 sgxvm jhi[8400]: AppletsManager::discoverVmType(), Couldn't connect to either BHv1 or BHv2.
1月 18 16:48:09 sgxvm jhi[8400]: Error: discoverVmType() failed
1月 18 16:48:09 sgxvm jhi[8400]: JHI init failed