Describe the bug
Only QAT devices in bus 0000 are handled by QAT device plugin's init container. Therefore for devices in bus 0001 (or any other I guess), services cannot be enabled, VFs cannot be created or VFs cannot be bound to a driver such as vfio-pci

In demo/qat-init.sh, bus 0000: is always prepended to the rest of the device address... see the 3rd line of sysfs_config() below. The same is also present in sriov_enable()

sysfs_config() {
  if [ "$SERVICES_ENABLED_FOUND" = "TRUE" ]; then
    for dev in $DEVS; do
      DEVPATH="/sys/bus/pci/devices/0000:$dev"
      PCI_DEV=$(cat "$DEVPATH"/device 2> /dev/null)
      if [ "$PCI_DEV" != "$QAT_4XXX_DEVICE_PCI_ID" ] && [ "$PCI_DEV" != "$QAT_401XX_DEVICE_PCI_ID" ] && [ "$PCI_DEV" != "$QAT_402XX_DEVICE_PCI_ID" ] && [ "$PCI_DEV" != "$QAT_420XX_DEVICE_PCI_ID" ]; then
        continue
      fi

To Reproduce
Run the QAT device plugin's init container on a server with QAT devices with bus 0001 e.g. 0001:01:00.0

Expected behavior
Services should be configured, VFs created and bound to vfio-pci for QAT devices in bus 0001