Intel® QuickAssist Technology (Intel® QAT)
For questions and discussions related to Intel® QuickAssist Technology (Intel® QAT).
66 Discussions

Not sure how to configure configuration for Ubuntu 22.04 for Quick assist technology

hiteshvishal
Beginner
858 Views

Hello I was trying to do configuration & tuning when the service is enabled. The docs says 
The configuration file /etc/sysconfig/qat will look like:

but unfortunately ubuntu doesn't use sysconfig

Could you please help 

 

i am getting following error also
Couldn't get section SHIM

0 Kudos
11 Replies
Ronny_G_Intel
Moderator
804 Views

Hi hiteshvishal,


I would need more information to assist you with the QAT configuration. Could you please specify the hardware you are using and the driver you have installed? Additionally, have you completed the QAT driver compilation?


Here are some reference materials to help you get started:

https://www.intel.com/content/www/us/en/support/articles/000094285/technologies/intel-quickassist-technology-intel-qat.html


Intel® QuickAssist Technology Software for Linux* - Getting Started Guide - Customer Enabling Release

https://www.intel.com/content/www/us/en/content-details/710059/intel-quickassist-technology-software-for-linux-getting-started-guide-customer-enabling-release.html


Intel® QuickAssist Technology (Intel® QAT) Software for Linux* Getting Started Guide – Hardware Version 2.0

https://www.intel.com/content/www/us/en/content-details/632506/intel-quickassist-technology-intel-qat-software-for-linux-getting-started-guide-hardware-version-2-0.html


Regards,

Ronny G


0 Kudos
hiteshvishal
Beginner
781 Views

Hello

 

I am using below hardware.

Motherboard
Gigabyte MS73-HBO having chipset Intel® C741. Please refer below for more details

https://www.gigabyte.com/Enterprise/Server-Motherboard/MS73-HB0-rev-1x-3x#Specifications

 

Intel processor : 2 processors 

Intel xeon gold 5520+
https://www.intel.com/content/www/us/en/products/sku/237561/intel-xeon-gold-5520-processor-52-5m-cache-2-20-ghz/specifications.html

we are trying 
Intel® QuickAssist Technology (Intel® QAT) Software for Linux* Getting Started Guide – Hardware Version 2.0

and the operating system that we have installed is ubuntu 24.04 LTS. We have tried with 22.04 LTS same issue.

We are using intel QAT2.0 driver.

could you please help us out , its quite painful journey for us.

Regards,

Regards,

Hitesh

 

0 Kudos
Ronny_G_Intel
Moderator
747 Views

Hi hiteshvishal,



Thanks for providing additional details and I am sorry that you are having issues with the QAT deployment.


I would recommend that you try the following installation steps:

https://intel.github.io/quickassist/GSG/2.X/installation.html#install-acceleration-software


Once the software is installed, please run the following commands and provide the output:

$ lsmod | grep qat

$ service qat_service status



Thanks,

Ronny G


0 Kudos
hiteshvishal
Beginner
713 Views

Hello,

 

Please find below the information as requested.

lsmod | grep qat
qat_4xxx 28672 0
intel_qat 802816 2 qat_4xxx,usdm_drv
uio 28672 1 intel_qat


lsmod | grep "qa"
service qat_service status
qat_4xxx 28672 0
intel_qat 802816 2 qat_4xxx,usdm_drv
uio 28672 1 intel_qat
○ qat_service.service
Loaded: masked (Reason: Unit qat_service.service is masked.)
Active: inactive (dead)

./build/cpa_sample_code
qaeMemInit started
[error] SalCtrl_AdfServicesStartedCheck() - : Sal Ctrl failed to start in given time

[error] do_userStart() - : Failed to start services

/QAT/quickassist/lookaside/access_layer/src/sample_code/performance/cpa_sample_code_main.c, main():455 Could not start sal for user space


systemctl status qat
● qat.service - QAT service
Loaded: loaded (/usr/lib/systemd/system/qat.service; enabled; preset: enabled)
Active: active (exited) since Sat 2025-01-18 20:33:00 IST; 5min ago
Process: 14180 ExecStart=/etc/init.d/qat_service start (code=exited, status=0/SUCCESS)
Main PID: 14180 (code=exited, status=0/SUCCESS)
CPU: 718ms

Jan 18 20:32:55 rv-MS73-HB0-000 systemd[1]: Starting qat.service - QAT service...
Jan 18 20:32:58 rv-MS73-HB0-000 qat_service[14367]: Restarting all devices.
Jan 18 20:32:58 rv-MS73-HB0-000 qat_service[14367]: Processing /etc/4xxx_dev0.conf
Jan 18 20:32:59 rv-MS73-HB0-000 qat_service[14367]: Processing /etc/4xxx_dev1.conf
Jan 18 20:33:00 rv-MS73-HB0-000 qat_service[14409]: Checking status of all devices.
Jan 18 20:33:00 rv-MS73-HB0-000 qat_service[14409]: There is 2 QAT acceleration device(s) in the system:
Jan 18 20:33:00 rv-MS73-HB0-000 qat_service[14409]: qat_dev0 - type: 4xxx, inst_id: 0, node_id: 0, bsf: 0000:76:00.0, #accel: 1 #engines: 9 state: up
Jan 18 20:33:00 rv-MS73-HB0-000 qat_service[14409]: qat_dev1 - type: 4xxx, inst_id: 1, node_id: 1, bsf: 0000:f3:00.0, #accel: 1 #engines: 9 state: up
Jan 18 20:33:00 rv-MS73-HB0-000 systemd[1]: Finished qat.service - QAT service.


Jan 12 15:31:28 rv-MS73-HB0-000 systemd[1]: Starting qat.service - QAT service...
Jan 12 15:31:28 rv-MS73-HB0-000 qat_init.sh[6650]: /usr/sbin/qat_init.sh, device 0000:76:00.0 configured with services: asym;dc
Jan 12 15:31:29 rv-MS73-HB0-000 qat_init.sh[6650]: /usr/sbin/qat_init.sh, device 0000:f3:00.0 configured with services: asym;dc
Jan 12 15:31:32 rv-MS73-HB0-000 systemd[1]: Started qat.service - QAT service.
Jan 12 15:37:21 rv-MS73-HB0-000 systemd[1]: Stopping qat.service - QAT service...
Jan 12 15:37:21 rv-MS73-HB0-000 systemd[1]: qat.service: Deactivated successfully.
Jan 12 15:37:21 rv-MS73-HB0-000 systemd[1]: Stopped qat.service - QAT service.
Jan 12 15:37:21 rv-MS73-HB0-000 systemd[1]: qat.service: Consumed 1.826s CPU time, 22.4M memory peak, 0B memory swap peak.
Jan 12 15:37:21 rv-MS73-HB0-000 systemd[1]: Starting qat.service - QAT service...
Jan 12 15:37:21 rv-MS73-HB0-000 qat_init.sh[9603]: /usr/sbin/qat_init.sh, device 0000:76:00.0 configured with services: asym;dc
Jan 12 15:37:21 rv-MS73-HB0-000 qat_init.sh[9603]: /usr/sbin/qat_init.sh, device 0000:f3:00.0 configured with services: asym;dc
Jan 12 15:37:23 rv-MS73-HB0-000 systemd[1]: Started qat.service - QAT service.
Jan 12 15:38:04 rv-MS73-HB0-000 systemd[1]: Stopping qat.service - QAT service...
Jan 12 15:38:04 rv-MS73-HB0-000 systemd[1]: qat.service: Deactivated successfully.
Jan 12 15:38:04 rv-MS73-HB0-000 systemd[1]: Stopped qat.service - QAT service.
Jan 12 15:38:04 rv-MS73-HB0-000 systemd[1]: qat.service: Consumed 1.495s CPU time.
Jan 12 15:38:09 rv-MS73-HB0-000 systemd[1]: Starting qat.service - QAT service...
Jan 12 15:38:10 rv-MS73-HB0-000 qat_init.sh[10371]: /usr/sbin/qat_init.sh, device 0000:76:00.0 configured with services: asym;dc
Jan 12 15:38:10 rv-MS73-HB0-000 qat_init.sh[10371]: /usr/sbin/qat_init.sh, device 0000:f3:00.0 configured with services: asym;dc
Jan 12 15:38:12 rv-MS73-HB0-000 systemd[1]: Started qat.service - QAT service.
Jan 12 16:12:35 rv-MS73-HB0-000 qatmgr[10978]: Couldn't get section SHIM
Jan 12 16:12:35 rv-MS73-HB0-000 qatmgr[10978]: Couldn't get section SHIM
Jan 12 16:12:35 rv-MS73-HB0-000 qatmgr[10978]: Couldn't get section SHIM
Jan 12 16:12:35 rv-MS73-HB0-000 qatmgr[10978]: Couldn't get section SHIM
Jan 12 16:12:35 rv-MS73-HB0-000 qatmgr[10978]: Couldn't get section SHIM
Jan 12 16:12:35 rv-MS73-HB0-000 qatmgr[10978]: Couldn't get section SHIM
Jan 12 16:12:35 rv-MS73-HB0-000 qatmgr[10978]: Couldn't get section SHIM

0 Kudos
Ronny_G_Intel
Moderator
655 Views

Hi hiteshvishal,


Based on the provided logs and information, it appears that there are a few issues with the Intel QuickAssist Technology (QAT) setup. 


  • Masked qat_service.service

The qat_service.service is masked, which means it is disabled and cannot be started or enabled. This is evident from the following log:

qat_service.service Loaded: masked (Reason: Unit qat_service.service is masked.) Active: inactive (dead)


To unmask and start the service, use the following commands:

$ sudo systemctl unmask qat_service.service

$ sudo systemctl enable qat_service.service

$ sudo systemctl start qat_service.service


  • The qat.service appears to be active and has recognized the QAT devices


  • The error in the cpa_sample_code indicates that the services failed to start:

qaeMemInit started [error] SalCtrl_AdfServicesStartedCheck() - : Sal Ctrl failed to start in given time [error] do_userStart() - : Failed to start services /QAT/quickassist/lookaside/access_layer/src/sample_code/performance/cpa_sample_code_main.c, main():455 Could not start sal for user space


If QAT install was performed with intel_iommu=on and ./configure --enable-icp-sriov=host – verify vfs are running:

To start vfs enter: # service qat_service_vfs start


To verify vfs are running enter: # service qat_service_vfs status


If QAT install was performed with intel_iommu=on and ./configure targeting PF use only

This particular configuration is not valid since PFs are not able to be used when IOMMU is enabled.



Thanks,

Ronny G


0 Kudos
Ronny_G_Intel
Moderator
591 Views

Hi hiteshvishal,


Did you have a chance to look into my previous post?

Do you still need assistance?


Thanks,

Ronny G


0 Kudos
hiteshvishal
Beginner
539 Views

Hello Sir,

 

We tried the above solutions doesn't worked for us.

so we switched to ubuntu 22 instead to 24  and tried to install from source.

lsmod | grep qat
qat_4xxx 20480 0
intel_qat 397312 1 qat_4xxx
crc8 12288 1 intel_qat
authenc 12288 1 intel_qat


service qat_service status
Unit qat_service.service could not be found.

systemctl status qat
● qat.service - QAT service
Loaded: loaded (/lib/systemd/system/qat.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2025-01-25 18:28:12 IST; 2min 30s ago
Process: 52717 ExecStartPre=/bin/sh -c test $(getent group qat) (code=exited, status=0/SUCCESS)
Process: 52719 ExecStartPre=/usr/sbin/qat_init.sh (code=exited, status=0/SUCCESS)
Process: 52999 ExecStart=/usr/sbin/qatmgr --policy=${POLICY} (code=exited, status=0/SUCCESS)
Main PID: 53001 (qatmgr)
Tasks: 1 (limit: 154044)
Memory: 364.0K
CPU: 696ms
CGroup: /system.slice/qat.service
└─53001 /usr/sbin/qatmgr --policy=0

Jan 25 18:28:10 rv-MS73-HB0-000 systemd[1]: qat.service: Deactivated successfully.
Jan 25 18:28:10 rv-MS73-HB0-000 systemd[1]: Stopped QAT service.
Jan 25 18:28:10 rv-MS73-HB0-000 systemd[1]: Starting QAT service...
Jan 25 18:28:12 rv-MS73-HB0-000 systemd[1]: Started QAT service.

 

no device is getting detected

we have used following command to configure

./configure --enable-service systemdsystemunitdir=/lib/systemd/system/ --prefix=/usr --enable-icp-sriov=host

--enable-icp-sriov=host option does n't exists. warning message is shown

we also performed

Update the GRUB_CMDLINE_LINUX line by adding intel_iommu=on.

Update the GRUB_CMDLINE_LINUX line by adding vfio-pci-ids=8086:4942.

still facing the issue



0 Kudos
Ronny_G_Intel
Moderator
438 Views

Hi hiteshvishal,


lsmod | grep qat

qat_4xxx 20480 0

intel_qat 397312 1 qat_4xxx

crc8 12288 1 intel_qat

authenc 12288 1 intel_qat


It looks like the QAT kernel modules are loaded, but the devices are not being detected.

Let's first check if the QAT hardware is detected by the system.


Please run the following:

$lspci | grep -i QAT

You should see something similar to:

00:06.0 PCI bridge: Intel Corporation Atom Processor P Series Integrated QAT Root Port (rev 11)

If no QAT devices are listed, it could indicate a hardware issue or a BIOS configuration problem.

Ensure that the following settings are enabled in your BIOS:

  • Intel VT-d (Virtualization Technology for Directed I/O)
  • SR-IOV (Single Root I/O Virtualization)

This could be the reason why you are getting: --enable-icp-sriov=host option does n't exists. warning message is shown.

Your grub configuration looks okay based on your comments but please provide me with the output after running:

$cat /proc/cmdline


Regards,

Ronny G



0 Kudos
Ronny_G_Intel
Moderator
347 Views

Hi hiteshvishal,


Just a quick follow-up: have you had a chance to review my previous note?


Regards,

Ronny G


0 Kudos
Ronny_G_Intel
Moderator
225 Views

Hi hiteshvishal,


Please inform me if you still require assistance with this issue; otherwise, I will proceed to close the internal ticket we created for it.


Regards,

Ronny G



0 Kudos
Ronny_G_Intel
Moderator
115 Views

Hello hiteshvishal,


I am closing the internal ticket we created for this issue as we have not received a response from you. 

If you still need assistance with this issue, please create a new community post, as we will no longer be monitoring this one.


Regards,

Ronny G


0 Kudos
Reply