The patch landed in linux-next an will be part of upstream 6.17 kernel. This 
mean it will be included in Questing by default.
I am starting the backport to Plucky.

** Changed in: linux (Ubuntu Questing)
       Status: Triaged => Invalid

** Changed in: linux (Ubuntu Plucky)
       Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2111231

Title:
  Documentation update for  [Ubuntu25.04] "virsh attach-interface"
  requires a reboot to reflect the attached interfaces on the guest

Status in The Ubuntu-power-systems project:
  Triaged
Status in Release Notes for Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Plucky:
  In Progress
Status in linux source package in Questing:
  Invalid

Bug description:
  == Comment: #2 - Amit Machhiwal <[email protected]> - 2025-05-12 
04:46:34 ==
  [Ubuntu25.04] "virsh attach-interface" requires a reboot to reflect the 
attached
  interfaces on the KVM guest running inside a PowerVM LPAR.

  Abstract
  --------
  A reboot is required for the interfaces attached through "virsh
  attach-interface" to be reflected on the KVM guest running inside a PowerVM
  LPAR. Same behavior is observed with or without the "--live" option.

  Linux releases affected
  -----------------------
  Ubuntu 25.04 (Kernel versions: all supported versions) and any distro which 
uses
  powerpc-utils/plucky,now 1.3.13-1 or later.

  Symptoms
  --------
  When a virsh attach-device is performed on L2, the corresponding hotplug
  operation does not go through and below errors are seen:

    dmesg
    -----
      On device-attach
      ----------------
      [  165.672791] RTAS: event: 1, Type: Hotplug Event (229), Severity: 1
      [  165.900889] dlpar: Could not handle DLPAR request "dt add index 
0x40010008"
      [  165.900889] dlpar: Could not handle DLPAR request "dt add index 
0x40010008"

    drmgr log
    ---------
     Found drc_name C65544
     is calling rtas_set_indicator(ISOLATE index 0x40010008)
     is calling set_power(POWER_OFF index 0x40010008, power_domain 0xffffffff)
     is calling card_present
     Waiting for the card to appear...
     get-sensor for 40010008: 0, 1
     is calling set_power(POWER_ON index 0x40010008, power_domain 0xffffffff
     calling rtas_set_indicator(UNISOLATE index 0x40010008)
     Initiating kernel DLPAR "dt add index 0x40010008"
     Failed to write to /sys/kernel/dlpar: Input/output error
     add_device_tree_nodes failed at /proc/device-tree/pci@800000020000001
     Internal software error. Contact your service representative.

  Workaround
  ----------
  This is a regression introduced in powerpc-utils/plucky,now 1.3.13-1 and a git
  bisect pointed to the below commit:

   a2d1b70cbc90 ("drmgr/pci: Add kernel interface support for device
  tree update")

  The above commit adds kernel interface for DLPAR IO add/remove if the it is
  supported. In the failure case, the kernel interface adding the device tree
  update is failing. This is because the kernel interface supports only
  ibm,drc-info property to identify drc-index which is available in recent FW. 
But
  the older FW does not provide this interface but instead ibm,drc-indexes
  property is available

  So, if we need kernel interface for the older FW, changes are needed in kernel
  for device tree update (add) or make changes in powerpc utils not to use 
kernel
  interface for the old FW (if drc-info not present) assuming we do not support
  secure boot on older FW.

  To workaround this problem, either revert to an older `drmgr` version prior to
  commit `a2d1b70cbc90` or reboot your guest so that the device is listed inside
  the KVM guest (L2).

  Fix Outlook
  -----------
  A kernel patch has been sent upstream for fixing this bug and awaiting merge
  into the mainline.

    https://lore.kernel.org/linuxppc-
  dev/[email protected]/

  Thanks,
  Amit

  == Comment: #3 - Amit Machhiwal <[email protected]> - 2025-05-12 
04:48:42 ==
  @Haren,

  Could you please review the above Ubuntu 25.04 documenatation update
  and suggest any changes if required.

  Thanks,
  Amit

  == Comment: #5 - Amit Machhiwal <[email protected]> - 2025-05-14 
00:41:26 ==
  [Ubuntu25.04] "virsh attach-interface" requires a reboot to reflect the 
attached
  interfaces on the KVM guest running inside a PowerVM LPAR.

  Abstract
  --------
  A reboot is required for the interfaces attached through "virsh
  attach-interface" to be reflected on the KVM guest running inside a PowerVM
  LPAR. Same behavior is observed with or without the "--live" option.

  Linux releases affected
  -----------------------
  Ubuntu 25.04 (Kernel versions: all supported versions) and any distro which 
uses
  powerpc-utils/plucky,now 1.3.13-1 or later.

  Symptoms
  --------
  When a virsh attach-device is performed on L2, the corresponding hotplug
  operation does not go through and below errors are seen:

    dmesg
    -----
      On device-attach
      ----------------
      [  165.672791] RTAS: event: 1, Type: Hotplug Event (229), Severity: 1
      [  165.900889] dlpar: Could not handle DLPAR request "dt add index 
0x40010008"
      [  165.900889] dlpar: Could not handle DLPAR request "dt add index 
0x40010008"

    drmgr log
    ---------
     Found drc_name C65544
     is calling rtas_set_indicator(ISOLATE index 0x40010008)
     is calling set_power(POWER_OFF index 0x40010008, power_domain 0xffffffff)
     is calling card_present
     Waiting for the card to appear...
     get-sensor for 40010008: 0, 1
     is calling set_power(POWER_ON index 0x40010008, power_domain 0xffffffff
     calling rtas_set_indicator(UNISOLATE index 0x40010008)
     Initiating kernel DLPAR "dt add index 0x40010008"
     Failed to write to /sys/kernel/dlpar: Input/output error
     add_device_tree_nodes failed at /proc/device-tree/pci@800000020000001
     Internal software error. Contact your service representative.

  Workaround
  ----------
  This is a regression introduced in powerpc-utils/plucky,now 1.3.13-1 and a git
  bisect pointed to the below commit:

   a2d1b70cbc90 ("drmgr/pci: Add kernel interface support for device
  tree update")

  The above commit adds kernel interface for DLPAR IO add/remove if the it is
  supported. In the failure case, the kernel interface adding the device tree
  update is failing. This is because the kernel interface supports only
  ibm,drc-info property to identify drc-index which is available in recent FW. 
But
  the older FW does not provide this interface but instead ibm,drc-indexes
  property is available

  So, if we need kernel interface for the older FW, changes are needed in kernel
  for device tree update (add) or make changes in powerpc utils not to use 
kernel
  interface for the old FW (if drc-info not present) assuming we do not support
  secure boot on older FW.

  To workaround this problem, either revert to an older `drmgr` version prior to
  commit `a2d1b70cbc90` or reboot your guest so that the device is listed inside
  the KVM guest (L2).

  Note: If you are using kernel lockdown, it's not recommended to revert to an
  older version of drmgr. In this case, rebooting the system is the only
  workaround.

  Fix Outlook
  -----------
  A kernel patch has been sent upstream for fixing this bug and awaiting merge
  into the mainline.

    https://lore.kernel.org/linuxppc-
  dev/[email protected]/

  Thanks,
  Amit

  == Comment: #8 - Amit Machhiwal <[email protected]> - 2025-05-19 
01:09:53 ==
  Copying the latest draft:

  [Ubuntu25.04] "virsh attach-interface" requires a reboot to reflect the 
attached
  interfaces on the KVM guest running inside a PowerVM LPAR.

  Abstract
  --------
  A reboot is required for the interfaces attached through "virsh
  attach-interface" to be reflected on the KVM guest running inside a PowerVM
  LPAR. Same behavior is observed with or without the "--live" option.

  Linux releases affected
  -----------------------
  Ubuntu 25.04 (Kernel versions: all supported versions) and any distro which 
uses
  powerpc-utils 1.3.13 or later.

  Symptoms
  --------
  When a virsh attach-device is performed on L2, the corresponding hotplug
  operation does not go through and below errors are seen:

    dmesg
    -----
      On device-attach
      ----------------
      [  165.672791] RTAS: event: 1, Type: Hotplug Event (229), Severity: 1
      [  165.900889] dlpar: Could not handle DLPAR request "dt add index 
0x40010008"
      [  165.900889] dlpar: Could not handle DLPAR request "dt add index 
0x40010008"

    drmgr log
    ---------
     Found drc_name C65544
     is calling rtas_set_indicator(ISOLATE index 0x40010008)
     is calling set_power(POWER_OFF index 0x40010008, power_domain 0xffffffff)
     is calling card_present
     Waiting for the card to appear...
     get-sensor for 40010008: 0, 1
     is calling set_power(POWER_ON index 0x40010008, power_domain 0xffffffff
     calling rtas_set_indicator(UNISOLATE index 0x40010008)
     Initiating kernel DLPAR "dt add index 0x40010008"
     Failed to write to /sys/kernel/dlpar: Input/output error
     add_device_tree_nodes failed at /proc/device-tree/pci@800000020000001
     Internal software error. Contact your service representative.

  Workaround
  ----------
  This is a regression caused by a change done in powerpc-utils v1.3.13. The
  hotplug operations work fine till powerpc-utils v1.3.12.

  To workaround this problem, either revert to an older `drmgr` version v1.3.12 
or
  older or reboot your guest so that the device is recognised by the KVM guest
  (L2).

  Note: If you are using kernel lockdown, it's not recommended to revert to an
  older version of drmgr. In this case, rebooting the system is the only
  workaround.

  Fix Outlook
  -----------
  A kernel patch has been sent upstream for fixing this bug and awaiting merge
  into the mainline.

    https://lore.kernel.org/linuxppc-
  dev/[email protected]/

  Thanks,
  Amit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2111231/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to