[Kernel-packages] [Bug 2111231] Re: Documentation update for [Ubuntu25.04] "virsh attach-interface" requires a reboot to reflect the attached interfaces on the guest
This bug is awaiting verification that the linux-azure-
nvidia-6.14/6.14.0-1006.6 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-noble-linux-azure-
nvidia-6.14' to 'verification-done-noble-linux-azure-nvidia-6.14'. If
the problem still exists, change the tag 'verification-needed-noble-
linux-azure-nvidia-6.14' to 'verification-failed-noble-linux-azure-
nvidia-6.14'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-noble-linux-azure-nvidia-6.14-v2
verification-needed-noble-linux-azure-nvidia-6.14
--
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:
Fix Released
Status in Release Notes for Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Plucky:
Fix Released
Status in linux source package in Questing:
Invalid
Bug description:
[ Impact ]
powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes for IO
add
IO hotplug add event is handled in the user space with drmgr tool.
After the device is enabled, the user space uses /sys/kernel/dlpar
interface with “dt add index ” to update the device tree.
The kernel interface (dlpar_hp_dt_add()) finds the parent node for
the specified ‘drc_index’ from ibm,drc-info property. The recent FW
provides this property from 2017 onwards. But KVM guest code in
some releases is still using the older SLOF firmware which has
ibm,drc-indexes property instead of ibm,drc-info.
If the ibm,drc-info is not available, this patch adds changes to
search ‘drc_index’ from the indexes array in ibm,drc-indexes
property to support old FW.
[ Fix ]
Backport from linux-next commit:
- 41a1452759a8b1 powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes
for IO add
[ Test Plan ]
Perform a virsh attach-device on an L2 VM (on a Power instance) and
verify that the corresponding hotplug operation does go through.
[ Regression Potential ]
The patch introduces a fallback mechanism that scans ibm,drc-indexes
only when ibm,drc-info is missing, minimizing disruption to existing
behavior. However, in malformed or ambiguous device trees, the
fallback logic might match unintended nodes, potentially
misconfiguring the hotplug target.
---
== Comment: #2 - Amit Machhiwal - 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 0x)
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 0x
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@8002001
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 kerne
[Kernel-packages] [Bug 2111231] Re: Documentation update for [Ubuntu25.04] "virsh attach-interface" requires a reboot to reflect the attached interfaces on the guest
** Tags removed: verification-needed-noble-linux-azure-nvidia-6.14
** Tags added: verification-done-noble-linux-azure-nvidia-6.14
--
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:
Fix Released
Status in Release Notes for Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Plucky:
Fix Released
Status in linux source package in Questing:
Invalid
Bug description:
[ Impact ]
powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes for IO
add
IO hotplug add event is handled in the user space with drmgr tool.
After the device is enabled, the user space uses /sys/kernel/dlpar
interface with “dt add index ” to update the device tree.
The kernel interface (dlpar_hp_dt_add()) finds the parent node for
the specified ‘drc_index’ from ibm,drc-info property. The recent FW
provides this property from 2017 onwards. But KVM guest code in
some releases is still using the older SLOF firmware which has
ibm,drc-indexes property instead of ibm,drc-info.
If the ibm,drc-info is not available, this patch adds changes to
search ‘drc_index’ from the indexes array in ibm,drc-indexes
property to support old FW.
[ Fix ]
Backport from linux-next commit:
- 41a1452759a8b1 powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes
for IO add
[ Test Plan ]
Perform a virsh attach-device on an L2 VM (on a Power instance) and
verify that the corresponding hotplug operation does go through.
[ Regression Potential ]
The patch introduces a fallback mechanism that scans ibm,drc-indexes
only when ibm,drc-info is missing, minimizing disruption to existing
behavior. However, in malformed or ambiguous device trees, the
fallback logic might match unintended nodes, potentially
misconfiguring the hotplug target.
---
== Comment: #2 - Amit Machhiwal - 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 0x)
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 0x
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@8002001
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 insi
[Kernel-packages] [Bug 2111231] Re: Documentation update for [Ubuntu25.04] "virsh attach-interface" requires a reboot to reflect the attached interfaces on the guest
This bug is awaiting verification that the linux-intel/6.14.0-1008.8
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-plucky-linux-intel' to 'verification-done-
plucky-linux-intel'. If the problem still exists, change the tag
'verification-needed-plucky-linux-intel' to 'verification-failed-plucky-
linux-intel'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-plucky-linux-intel-v2
verification-needed-plucky-linux-intel
--
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:
Fix Released
Status in Release Notes for Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Plucky:
Fix Released
Status in linux source package in Questing:
Invalid
Bug description:
[ Impact ]
powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes for IO
add
IO hotplug add event is handled in the user space with drmgr tool.
After the device is enabled, the user space uses /sys/kernel/dlpar
interface with “dt add index ” to update the device tree.
The kernel interface (dlpar_hp_dt_add()) finds the parent node for
the specified ‘drc_index’ from ibm,drc-info property. The recent FW
provides this property from 2017 onwards. But KVM guest code in
some releases is still using the older SLOF firmware which has
ibm,drc-indexes property instead of ibm,drc-info.
If the ibm,drc-info is not available, this patch adds changes to
search ‘drc_index’ from the indexes array in ibm,drc-indexes
property to support old FW.
[ Fix ]
Backport from linux-next commit:
- 41a1452759a8b1 powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes
for IO add
[ Test Plan ]
Perform a virsh attach-device on an L2 VM (on a Power instance) and
verify that the corresponding hotplug operation does go through.
[ Regression Potential ]
The patch introduces a fallback mechanism that scans ibm,drc-indexes
only when ibm,drc-info is missing, minimizing disruption to existing
behavior. However, in malformed or ambiguous device trees, the
fallback logic might match unintended nodes, potentially
misconfiguring the hotplug target.
---
== Comment: #2 - Amit Machhiwal - 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 0x)
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 0x
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@8002001
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 kern
[Kernel-packages] [Bug 2111231] Re: Documentation update for [Ubuntu25.04] "virsh attach-interface" requires a reboot to reflect the attached interfaces on the guest
** Tags removed: verification-needed-plucky-linux-intel
** Tags added: verification-done-plucky-linux-intel
--
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:
Fix Released
Status in Release Notes for Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Plucky:
Fix Released
Status in linux source package in Questing:
Invalid
Bug description:
[ Impact ]
powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes for IO
add
IO hotplug add event is handled in the user space with drmgr tool.
After the device is enabled, the user space uses /sys/kernel/dlpar
interface with “dt add index ” to update the device tree.
The kernel interface (dlpar_hp_dt_add()) finds the parent node for
the specified ‘drc_index’ from ibm,drc-info property. The recent FW
provides this property from 2017 onwards. But KVM guest code in
some releases is still using the older SLOF firmware which has
ibm,drc-indexes property instead of ibm,drc-info.
If the ibm,drc-info is not available, this patch adds changes to
search ‘drc_index’ from the indexes array in ibm,drc-indexes
property to support old FW.
[ Fix ]
Backport from linux-next commit:
- 41a1452759a8b1 powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes
for IO add
[ Test Plan ]
Perform a virsh attach-device on an L2 VM (on a Power instance) and
verify that the corresponding hotplug operation does go through.
[ Regression Potential ]
The patch introduces a fallback mechanism that scans ibm,drc-indexes
only when ibm,drc-info is missing, minimizing disruption to existing
behavior. However, in malformed or ambiguous device trees, the
fallback logic might match unintended nodes, potentially
misconfiguring the hotplug target.
---
== Comment: #2 - Amit Machhiwal - 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 0x)
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 0x
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@8002001
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
[Kernel-packages] [Bug 2111231] Re: Documentation update for [Ubuntu25.04] "virsh attach-interface" requires a reboot to reflect the attached interfaces on the guest
** Tags removed: verification-needed-noble-linux-nvidia-6.14
** Tags added: verification-done-noble-linux-nvidia-6.14
--
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:
Fix Released
Status in Release Notes for Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Plucky:
Fix Released
Status in linux source package in Questing:
Invalid
Bug description:
[ Impact ]
powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes for IO
add
IO hotplug add event is handled in the user space with drmgr tool.
After the device is enabled, the user space uses /sys/kernel/dlpar
interface with “dt add index ” to update the device tree.
The kernel interface (dlpar_hp_dt_add()) finds the parent node for
the specified ‘drc_index’ from ibm,drc-info property. The recent FW
provides this property from 2017 onwards. But KVM guest code in
some releases is still using the older SLOF firmware which has
ibm,drc-indexes property instead of ibm,drc-info.
If the ibm,drc-info is not available, this patch adds changes to
search ‘drc_index’ from the indexes array in ibm,drc-indexes
property to support old FW.
[ Fix ]
Backport from linux-next commit:
- 41a1452759a8b1 powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes
for IO add
[ Test Plan ]
Perform a virsh attach-device on an L2 VM (on a Power instance) and
verify that the corresponding hotplug operation does go through.
[ Regression Potential ]
The patch introduces a fallback mechanism that scans ibm,drc-indexes
only when ibm,drc-info is missing, minimizing disruption to existing
behavior. However, in malformed or ambiguous device trees, the
fallback logic might match unintended nodes, potentially
misconfiguring the hotplug target.
---
== Comment: #2 - Amit Machhiwal - 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 0x)
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 0x
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@8002001
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
[Kernel-packages] [Bug 2111231] Re: Documentation update for [Ubuntu25.04] "virsh attach-interface" requires a reboot to reflect the attached interfaces on the guest
This bug is awaiting verification that the linux-
nvidia-6.14/6.14.0-1011.11 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-noble-linux-
nvidia-6.14' to 'verification-done-noble-linux-nvidia-6.14'. If the
problem still exists, change the tag 'verification-needed-noble-linux-
nvidia-6.14' to 'verification-failed-noble-linux-nvidia-6.14'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-noble-linux-nvidia-6.14-v2
verification-needed-noble-linux-nvidia-6.14
--
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:
Fix Released
Status in Release Notes for Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Plucky:
Fix Released
Status in linux source package in Questing:
Invalid
Bug description:
[ Impact ]
powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes for IO
add
IO hotplug add event is handled in the user space with drmgr tool.
After the device is enabled, the user space uses /sys/kernel/dlpar
interface with “dt add index ” to update the device tree.
The kernel interface (dlpar_hp_dt_add()) finds the parent node for
the specified ‘drc_index’ from ibm,drc-info property. The recent FW
provides this property from 2017 onwards. But KVM guest code in
some releases is still using the older SLOF firmware which has
ibm,drc-indexes property instead of ibm,drc-info.
If the ibm,drc-info is not available, this patch adds changes to
search ‘drc_index’ from the indexes array in ibm,drc-indexes
property to support old FW.
[ Fix ]
Backport from linux-next commit:
- 41a1452759a8b1 powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes
for IO add
[ Test Plan ]
Perform a virsh attach-device on an L2 VM (on a Power instance) and
verify that the corresponding hotplug operation does go through.
[ Regression Potential ]
The patch introduces a fallback mechanism that scans ibm,drc-indexes
only when ibm,drc-info is missing, minimizing disruption to existing
behavior. However, in malformed or ambiguous device trees, the
fallback logic might match unintended nodes, potentially
misconfiguring the hotplug target.
---
== Comment: #2 - Amit Machhiwal - 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 0x)
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 0x
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@8002001
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
updat
[Kernel-packages] [Bug 2111231] Re: Documentation update for [Ubuntu25.04] "virsh attach-interface" requires a reboot to reflect the attached interfaces on the guest
** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
--
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:
Fix Released
Status in Release Notes for Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Plucky:
Fix Released
Status in linux source package in Questing:
Invalid
Bug description:
[ Impact ]
powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes for IO
add
IO hotplug add event is handled in the user space with drmgr tool.
After the device is enabled, the user space uses /sys/kernel/dlpar
interface with “dt add index ” to update the device tree.
The kernel interface (dlpar_hp_dt_add()) finds the parent node for
the specified ‘drc_index’ from ibm,drc-info property. The recent FW
provides this property from 2017 onwards. But KVM guest code in
some releases is still using the older SLOF firmware which has
ibm,drc-indexes property instead of ibm,drc-info.
If the ibm,drc-info is not available, this patch adds changes to
search ‘drc_index’ from the indexes array in ibm,drc-indexes
property to support old FW.
[ Fix ]
Backport from linux-next commit:
- 41a1452759a8b1 powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes
for IO add
[ Test Plan ]
Perform a virsh attach-device on an L2 VM (on a Power instance) and
verify that the corresponding hotplug operation does go through.
[ Regression Potential ]
The patch introduces a fallback mechanism that scans ibm,drc-indexes
only when ibm,drc-info is missing, minimizing disruption to existing
behavior. However, in malformed or ambiguous device trees, the
fallback logic might match unintended nodes, potentially
misconfiguring the hotplug target.
---
== Comment: #2 - Amit Machhiwal - 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 0x)
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 0x
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@8002001
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
---
[Kernel-packages] [Bug 2111231] Re: Documentation update for [Ubuntu25.04] "virsh attach-interface" requires a reboot to reflect the attached interfaces on the guest
Details on successful verification see here:
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/2110407/comments/10
--
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:
Fix Committed
Status in Release Notes for Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Plucky:
Fix Committed
Status in linux source package in Questing:
Invalid
Bug description:
[ Impact ]
powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes for IO
add
IO hotplug add event is handled in the user space with drmgr tool.
After the device is enabled, the user space uses /sys/kernel/dlpar
interface with “dt add index ” to update the device tree.
The kernel interface (dlpar_hp_dt_add()) finds the parent node for
the specified ‘drc_index’ from ibm,drc-info property. The recent FW
provides this property from 2017 onwards. But KVM guest code in
some releases is still using the older SLOF firmware which has
ibm,drc-indexes property instead of ibm,drc-info.
If the ibm,drc-info is not available, this patch adds changes to
search ‘drc_index’ from the indexes array in ibm,drc-indexes
property to support old FW.
[ Fix ]
Backport from linux-next commit:
- 41a1452759a8b1 powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes
for IO add
[ Test Plan ]
Perform a virsh attach-device on an L2 VM (on a Power instance) and
verify that the corresponding hotplug operation does go through.
[ Regression Potential ]
The patch introduces a fallback mechanism that scans ibm,drc-indexes
only when ibm,drc-info is missing, minimizing disruption to existing
behavior. However, in malformed or ambiguous device trees, the
fallback logic might match unintended nodes, potentially
misconfiguring the hotplug target.
---
== Comment: #2 - Amit Machhiwal - 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 0x)
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 0x
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@8002001
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 insid
[Kernel-packages] [Bug 2111231] Re: Documentation update for [Ubuntu25.04] "virsh attach-interface" requires a reboot to reflect the attached interfaces on the guest
** Tags removed: verification-needed-plucky-linux
** Tags added: verification-done-plucky-linux
--
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:
Fix Committed
Status in Release Notes for Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Plucky:
Fix Committed
Status in linux source package in Questing:
Invalid
Bug description:
[ Impact ]
powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes for IO
add
IO hotplug add event is handled in the user space with drmgr tool.
After the device is enabled, the user space uses /sys/kernel/dlpar
interface with “dt add index ” to update the device tree.
The kernel interface (dlpar_hp_dt_add()) finds the parent node for
the specified ‘drc_index’ from ibm,drc-info property. The recent FW
provides this property from 2017 onwards. But KVM guest code in
some releases is still using the older SLOF firmware which has
ibm,drc-indexes property instead of ibm,drc-info.
If the ibm,drc-info is not available, this patch adds changes to
search ‘drc_index’ from the indexes array in ibm,drc-indexes
property to support old FW.
[ Fix ]
Backport from linux-next commit:
- 41a1452759a8b1 powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes
for IO add
[ Test Plan ]
Perform a virsh attach-device on an L2 VM (on a Power instance) and
verify that the corresponding hotplug operation does go through.
[ Regression Potential ]
The patch introduces a fallback mechanism that scans ibm,drc-indexes
only when ibm,drc-info is missing, minimizing disruption to existing
behavior. However, in malformed or ambiguous device trees, the
fallback logic might match unintended nodes, potentially
misconfiguring the hotplug target.
---
== Comment: #2 - Amit Machhiwal - 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 0x)
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 0x
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@8002001
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
[Kernel-packages] [Bug 2111231] Re: Documentation update for [Ubuntu25.04] "virsh attach-interface" requires a reboot to reflect the attached interfaces on the guest
This bug is awaiting verification that the linux/6.14.0-32.32 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-plucky-linux' to 'verification-done-plucky-linux'.
If the problem still exists, change the tag 'verification-needed-plucky-
linux' to 'verification-failed-plucky-linux'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-plucky-linux-v2 verification-needed-plucky-linux
--
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:
Fix Committed
Status in Release Notes for Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Plucky:
Fix Committed
Status in linux source package in Questing:
Invalid
Bug description:
[ Impact ]
powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes for IO
add
IO hotplug add event is handled in the user space with drmgr tool.
After the device is enabled, the user space uses /sys/kernel/dlpar
interface with “dt add index ” to update the device tree.
The kernel interface (dlpar_hp_dt_add()) finds the parent node for
the specified ‘drc_index’ from ibm,drc-info property. The recent FW
provides this property from 2017 onwards. But KVM guest code in
some releases is still using the older SLOF firmware which has
ibm,drc-indexes property instead of ibm,drc-info.
If the ibm,drc-info is not available, this patch adds changes to
search ‘drc_index’ from the indexes array in ibm,drc-indexes
property to support old FW.
[ Fix ]
Backport from linux-next commit:
- 41a1452759a8b1 powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes
for IO add
[ Test Plan ]
Perform a virsh attach-device on an L2 VM (on a Power instance) and
verify that the corresponding hotplug operation does go through.
[ Regression Potential ]
The patch introduces a fallback mechanism that scans ibm,drc-indexes
only when ibm,drc-info is missing, minimizing disruption to existing
behavior. However, in malformed or ambiguous device trees, the
fallback logic might match unintended nodes, potentially
misconfiguring the hotplug target.
---
== Comment: #2 - Amit Machhiwal - 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 0x)
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 0x
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@8002001
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 p
[Kernel-packages] [Bug 2111231] Re: Documentation update for [Ubuntu25.04] "virsh attach-interface" requires a reboot to reflect the attached interfaces on the guest
** Changed in: ubuntu-power-systems
Status: Triaged => Fix Committed
--
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:
Fix Committed
Status in Release Notes for Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Plucky:
Fix Committed
Status in linux source package in Questing:
Invalid
Bug description:
[ Impact ]
powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes for IO
add
IO hotplug add event is handled in the user space with drmgr tool.
After the device is enabled, the user space uses /sys/kernel/dlpar
interface with “dt add index ” to update the device tree.
The kernel interface (dlpar_hp_dt_add()) finds the parent node for
the specified ‘drc_index’ from ibm,drc-info property. The recent FW
provides this property from 2017 onwards. But KVM guest code in
some releases is still using the older SLOF firmware which has
ibm,drc-indexes property instead of ibm,drc-info.
If the ibm,drc-info is not available, this patch adds changes to
search ‘drc_index’ from the indexes array in ibm,drc-indexes
property to support old FW.
[ Fix ]
Backport from linux-next commit:
- 41a1452759a8b1 powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes
for IO add
[ Test Plan ]
Perform a virsh attach-device on an L2 VM (on a Power instance) and
verify that the corresponding hotplug operation does go through.
[ Regression Potential ]
The patch introduces a fallback mechanism that scans ibm,drc-indexes
only when ibm,drc-info is missing, minimizing disruption to existing
behavior. However, in malformed or ambiguous device trees, the
fallback logic might match unintended nodes, potentially
misconfiguring the hotplug target.
---
== Comment: #2 - Amit Machhiwal - 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 0x)
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 0x
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@8002001
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
--
[Kernel-packages] [Bug 2111231] Re: Documentation update for [Ubuntu25.04] "virsh attach-interface" requires a reboot to reflect the attached interfaces on the guest
** Changed in: linux (Ubuntu Plucky)
Status: In Progress => Fix Committed
--
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:
Fix Committed
Status in linux source package in Questing:
Invalid
Bug description:
[ Impact ]
powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes for IO
add
IO hotplug add event is handled in the user space with drmgr tool.
After the device is enabled, the user space uses /sys/kernel/dlpar
interface with “dt add index ” to update the device tree.
The kernel interface (dlpar_hp_dt_add()) finds the parent node for
the specified ‘drc_index’ from ibm,drc-info property. The recent FW
provides this property from 2017 onwards. But KVM guest code in
some releases is still using the older SLOF firmware which has
ibm,drc-indexes property instead of ibm,drc-info.
If the ibm,drc-info is not available, this patch adds changes to
search ‘drc_index’ from the indexes array in ibm,drc-indexes
property to support old FW.
[ Fix ]
Backport from linux-next commit:
- 41a1452759a8b1 powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes
for IO add
[ Test Plan ]
Perform a virsh attach-device on an L2 VM (on a Power instance) and
verify that the corresponding hotplug operation does go through.
[ Regression Potential ]
The patch introduces a fallback mechanism that scans ibm,drc-indexes
only when ibm,drc-info is missing, minimizing disruption to existing
behavior. However, in malformed or ambiguous device trees, the
fallback logic might match unintended nodes, potentially
misconfiguring the hotplug target.
---
== Comment: #2 - Amit Machhiwal - 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 0x)
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 0x
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@8002001
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
---
[Kernel-packages] [Bug 2111231] Re: Documentation update for [Ubuntu25.04] "virsh attach-interface" requires a reboot to reflect the attached interfaces on the guest
Plucky patch sent to KTML:
- https://lists.ubuntu.com/archives/kernel-team/2025-July/161372.html
--
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:
[ Impact ]
powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes for IO
add
IO hotplug add event is handled in the user space with drmgr tool.
After the device is enabled, the user space uses /sys/kernel/dlpar
interface with “dt add index ” to update the device tree.
The kernel interface (dlpar_hp_dt_add()) finds the parent node for
the specified ‘drc_index’ from ibm,drc-info property. The recent FW
provides this property from 2017 onwards. But KVM guest code in
some releases is still using the older SLOF firmware which has
ibm,drc-indexes property instead of ibm,drc-info.
If the ibm,drc-info is not available, this patch adds changes to
search ‘drc_index’ from the indexes array in ibm,drc-indexes
property to support old FW.
[ Fix ]
Backport from linux-next commit:
- 41a1452759a8b1 powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes
for IO add
[ Test Plan ]
Perform a virsh attach-device on an L2 VM (on a Power instance) and
verify that the corresponding hotplug operation does go through.
[ Regression Potential ]
The patch introduces a fallback mechanism that scans ibm,drc-indexes
only when ibm,drc-info is missing, minimizing disruption to existing
behavior. However, in malformed or ambiguous device trees, the
fallback logic might match unintended nodes, potentially
misconfiguring the hotplug target.
---
== Comment: #2 - Amit Machhiwal - 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 0x)
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 0x
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@8002001
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
[Kernel-packages] [Bug 2111231] Re: Documentation update for [Ubuntu25.04] "virsh attach-interface" requires a reboot to reflect the attached interfaces on the guest
** Description changed:
+ [ Impact ]
+
+ powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes for IO add
+
+ IO hotplug add event is handled in the user space with drmgr tool.
+ After the device is enabled, the user space uses /sys/kernel/dlpar
+ interface with “dt add index ” to update the device tree.
+ The kernel interface (dlpar_hp_dt_add()) finds the parent node for
+ the specified ‘drc_index’ from ibm,drc-info property. The recent FW
+ provides this property from 2017 onwards. But KVM guest code in
+ some releases is still using the older SLOF firmware which has
+ ibm,drc-indexes property instead of ibm,drc-info.
+
+ If the ibm,drc-info is not available, this patch adds changes to
+ search ‘drc_index’ from the indexes array in ibm,drc-indexes
+ property to support old FW.
+
+ [ Fix ]
+
+ Backport from linux-next commit:
+ - 41a1452759a8b1 powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes
for IO add
+
+ [ Test Plan ]
+
+ Perform a virsh attach-device on an L2 VM (on a Power instance) and
+ verify that the corresponding hotplug operation does go through.
+
+ [ Regression Potential ]
+
+ The patch introduces a fallback mechanism that scans ibm,drc-indexes
+ only when ibm,drc-info is missing, minimizing disruption to existing
+ behavior. However, in malformed or ambiguous device trees, the fallback
+ logic might match unintended nodes, potentially misconfiguring the
+ hotplug target.
+
+ ---
+
== Comment: #2 - Amit Machhiwal - 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 0x)
-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 0x
-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@8002001
-Internal software error. Contact your service representative.
+ 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 0x)
+ 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 0x
+ 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@8002001
+ 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
+ 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,
[Kernel-packages] [Bug 2111231] Re: Documentation update for [Ubuntu25.04] "virsh attach-interface" requires a reboot to reflect the attached interfaces on the guest
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 - 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 0x)
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 0x
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@8002001
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 - 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 - 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 b
[Kernel-packages] [Bug 2111231] Re: Documentation update for [Ubuntu25.04] "virsh attach-interface" requires a reboot to reflect the attached interfaces on the guest
--- Comment From [email protected] 2025-06-30 01:58 EDT--- V2 version posted https://lore.kernel.org/linuxppc- dev/[email protected]/ -- 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: Triaged Status in linux source package in Plucky: Triaged Status in linux source package in Questing: Triaged Bug description: == Comment: #2 - Amit Machhiwal - 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 0x) 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 0x 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@8002001 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 - 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 - 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
[Kernel-packages] [Bug 2111231] Re: Documentation update for [Ubuntu25.04] "virsh attach-interface" requires a reboot to reflect the attached interfaces on the guest
Thx, on our side we still plan to integrate the fix, once it got upstream
accepted.
(Lowering the importance to Medium now.)
** Changed in: ubuntu-power-systems
Importance: High => Medium
** Changed in: linux (Ubuntu Plucky)
Importance: High => Medium
** Changed in: linux (Ubuntu Questing)
Importance: High => Medium
--
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:
Triaged
Status in linux source package in Plucky:
Triaged
Status in linux source package in Questing:
Triaged
Bug description:
== Comment: #2 - Amit Machhiwal - 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 0x)
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 0x
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@8002001
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 - 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 - 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 t
[Kernel-packages] [Bug 2111231] Re: Documentation update for [Ubuntu25.04] "virsh attach-interface" requires a reboot to reflect the attached interfaces on the guest
It got documented in the plucky/25.04 release notes under known issues:
https://discourse.ubuntu.com/t/plucky-puffin-release-notes/48687#p-120902-ppc64el-93
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
** Changed in: ubuntu-release-notes
Status: New => Fix Released
** Changed in: ubuntu-release-notes
Assignee: (unassigned) => Frank Heimes (fheimes)
--
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:
Triaged
Status in linux source package in Plucky:
Triaged
Status in linux source package in Questing:
Triaged
Bug description:
== Comment: #2 - Amit Machhiwal - 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 0x)
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 0x
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@8002001
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 - 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 - 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
[Kernel-packages] [Bug 2111231] Re: Documentation update for [Ubuntu25.04] "virsh attach-interface" requires a reboot to reflect the attached interfaces on the guest
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin2504
--
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 linux package in Ubuntu:
Triaged
Status in linux source package in Plucky:
Triaged
Status in linux source package in Questing:
Triaged
Bug description:
== Comment: #2 - Amit Machhiwal - 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 0x)
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 0x
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@8002001
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 - 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 - 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
[Kernel-packages] [Bug 2111231] Re: Documentation update for [Ubuntu25.04] "virsh attach-interface" requires a reboot to reflect the attached interfaces on the guest
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Status: New => Triaged
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage
(ubuntu-power-triage)
** Changed in: linux (Ubuntu Questing)
Importance: Undecided => High
** Changed in: linux (Ubuntu Plucky)
Importance: Undecided => High
** Changed in: ubuntu-power-systems
Importance: Undecided => High
--
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 linux package in Ubuntu:
Triaged
Status in linux source package in Plucky:
Triaged
Status in linux source package in Questing:
Triaged
Bug description:
== Comment: #2 - Amit Machhiwal - 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 0x)
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 0x
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@8002001
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 - 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 - 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
[Kernel-packages] [Bug 2111231] Re: Documentation update for [Ubuntu25.04] "virsh attach-interface" requires a reboot to reflect the attached interfaces on the guest
** Also affects: linux (Ubuntu Plucky)
Importance: Undecided
Status: New
--
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 linux package in Ubuntu:
Triaged
Status in linux source package in Plucky:
Triaged
Status in linux source package in Questing:
Triaged
Bug description:
== Comment: #2 - Amit Machhiwal - 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 0x)
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 0x
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@8002001
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 - 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 - 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"
[Kernel-packages] [Bug 2111231] Re: Documentation update for [Ubuntu25.04] "virsh attach-interface" requires a reboot to reflect the attached interfaces on the guest
Apart from the kernel, does the powerpc-utils need to be changed as
well? If it does, need to file a bug against powerpc-utils (Ubuntu).
** Changed in: linux (Ubuntu Plucky)
Status: New => Triaged
** Also affects: linux (Ubuntu Questing)
Importance: Undecided
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
Status: Triaged
--
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 linux package in Ubuntu:
Triaged
Status in linux source package in Plucky:
Triaged
Status in linux source package in Questing:
Triaged
Bug description:
== Comment: #2 - Amit Machhiwal - 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 0x)
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 0x
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@8002001
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 - 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 - 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 d
[Kernel-packages] [Bug 2111231] Re: Documentation update for [Ubuntu25.04] "virsh attach-interface" requires a reboot to reflect the attached interfaces on the guest
** Changed in: linux (Ubuntu Plucky)
Assignee: (unassigned) => Massimiliano Pellizzer (mpellizzer)
--
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 linux package in Ubuntu:
Triaged
Status in linux source package in Plucky:
Triaged
Status in linux source package in Questing:
Triaged
Bug description:
== Comment: #2 - Amit Machhiwal - 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 0x)
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 0x
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@8002001
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 - 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 - 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 in
