| 2019-02-22 06:49:46 |
bugproxy |
bug |
|
|
added bug |
| 2019-02-22 06:49:49 |
bugproxy |
tags |
|
architecture-ppc64le bugnameltc-175674 severity-high targetmilestone-inin--- |
|
| 2019-02-22 06:49:50 |
bugproxy |
attachment added |
|
Guest XML https://bugs.launchpad.net/bugs/1817258/+attachment/5240874/+files/santwana_ubuntu.xml |
|
| 2019-02-22 06:50:04 |
bugproxy |
attachment added |
|
Host sosreport https://bugs.launchpad.net/bugs/1817258/+attachment/5240875/+files/sosreport-ltcgen3-20190221002259.tar.xz |
|
| 2019-02-22 06:50:05 |
bugproxy |
ubuntu: assignee |
|
Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) |
|
| 2019-02-22 06:50:09 |
bugproxy |
affects |
ubuntu |
numactl (Ubuntu) |
|
| 2019-02-26 11:26:56 |
Andrew Cloke |
bug task added |
|
ubuntu-power-systems |
|
| 2019-02-26 16:57:44 |
Joshua Powers |
bug |
|
|
added subscriber Joshua Powers |
| 2019-02-27 07:32:58 |
Andrew Cloke |
summary |
genesis : "numastat" doesn't display correct information for the guest. |
"numastat" doesn't display correct information for the guest. |
|
| 2019-02-27 07:33:37 |
Andrew Cloke |
ubuntu-power-systems: importance |
Undecided |
High |
|
| 2019-02-27 07:34:11 |
Andrew Cloke |
ubuntu-power-systems: assignee |
|
Canonical Server Team (canonical-server) |
|
| 2019-02-28 10:40:56 |
Christian Ehrhardt |
numactl (Ubuntu): status |
New |
Fix Released |
|
| 2019-02-28 10:41:01 |
Christian Ehrhardt |
nominated for series |
|
Ubuntu Bionic |
|
| 2019-02-28 10:41:01 |
Christian Ehrhardt |
bug task added |
|
numactl (Ubuntu Bionic) |
|
| 2019-02-28 10:41:01 |
Christian Ehrhardt |
nominated for series |
|
Ubuntu Cosmic |
|
| 2019-02-28 10:41:01 |
Christian Ehrhardt |
bug task added |
|
numactl (Ubuntu Cosmic) |
|
| 2019-02-28 10:49:37 |
Christian Ehrhardt |
numactl (Ubuntu Cosmic): status |
New |
Triaged |
|
| 2019-02-28 10:49:40 |
Christian Ehrhardt |
numactl (Ubuntu Bionic): status |
New |
Triaged |
|
| 2019-02-28 11:00:02 |
Frank Heimes |
ubuntu-power-systems: status |
New |
In Progress |
|
| 2019-02-28 11:03:45 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~paelzer/ubuntu/+source/numactl/+git/numactl/+merge/363777 |
|
| 2019-02-28 11:04:12 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~paelzer/ubuntu/+source/numactl/+git/numactl/+merge/363778 |
|
| 2019-02-28 11:44:06 |
Christian Ehrhardt |
numactl (Ubuntu Bionic): status |
Triaged |
In Progress |
|
| 2019-02-28 11:44:07 |
Christian Ehrhardt |
numactl (Ubuntu Cosmic): status |
Triaged |
In Progress |
|
| 2019-02-28 11:44:09 |
Christian Ehrhardt |
numactl (Ubuntu Bionic): assignee |
|
Christian Ehrhardt (paelzer) |
|
| 2019-02-28 11:44:11 |
Christian Ehrhardt |
numactl (Ubuntu Cosmic): assignee |
|
Christian Ehrhardt (paelzer) |
|
| 2019-02-28 12:15:46 |
Christian Ehrhardt |
description |
== Comment: #0 - SANTWANA SAMANTRAY <santwana.samantray@in.ibm.com> - 2019-02-20 23:48:43 ==
---Problem Description---
numastat doesn't display correct information for kvm guests.
The guest is configured with vcpupin from the node8:
Snippet of the guest XML :
<vcpu placement='static' current='4'>8</vcpu>
<cputune>
<vcpupin vcpu='0' cpuset='64'/>
<vcpupin vcpu='1' cpuset='65'/>
<vcpupin vcpu='2' cpuset='66'/>
<vcpupin vcpu='3' cpuset='67'/>
<emulatorpin cpuset='64-67'/>
</cputune>
<numatune>
<memory mode='strict' nodeset='8'/>
</numatune>
== Host Details ==
# lscpu
Architecture: ppc64le
Byte Order: Little Endian
CPU(s): 128
On-line CPU(s) list: 0-127
Thread(s) per core: 4
Core(s) per socket: 16
Socket(s): 2
NUMA node(s): 6
Model: 2.2 (pvr 004e 1202)
Model name: POWER9, altivec supported
CPU max MHz: 3800.0000
CPU min MHz: 2300.0000
L1d cache: 32K
L1i cache: 32K
L2 cache: 512K
L3 cache: 10240K
NUMA node0 CPU(s): 0-63
NUMA node8 CPU(s): 64-127
NUMA node252 CPU(s):
NUMA node253 CPU(s):
NUMA node254 CPU(s):
NUMA node255 CPU(s):
After starting the guest, the numastat doesn't display the guest process to be running in node8.
# numastat -c qemu-system-ppc64
Per-node process memory usage (in MBs) for PID 5738 (qemu-system-ppc)
Node 0 Node 8 Node 252 Node 253 Node 254 Node 255 Total
------ ------ -------- -------- -------- -------- -----
Huge 0 0 0 0 0 0 0
Heap 0 0 0 0 0 0 14
Stack 14 0 0 0 0 0 0
Private 936 0 0 0 0 0 3064
------- ------ ------ -------- -------- -------- -------- -----
Total 936 0 0 0 0 0 3079
# service numad status
* numad.service - numad - The NUMA daemon that manages application locality.
Loaded: loaded (/lib/systemd/system/numad.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2019-02-21 00:43:54 EST; 20s ago
Docs: man:numad
Process: 8091 ExecStart=/usr/bin/numad $DAEMON_ARGS -i 15 (code=exited, status=0/SUCCESS)
Main PID: 8092 (numad)
Tasks: 2 (limit: 19660)
CGroup: /system.slice/numad.service
`-8092 /usr/bin/numad -i 15
Feb 21 00:43:54 ltcgen3 systemd[1]: Starting numad - The NUMA daemon that manages application locality....
Feb 21 00:43:54 ltcgen3 systemd[1]: Started numad - The NUMA daemon that manages application locality..
---uname output---
Linux ltcgen3 4.15.0-1016-ibm-gt #18-Ubuntu SMP Thu Feb 7 16:58:31 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = Witherspoon
== Versions Installed ==
qemu 1:2.11+dfsg-1ubuntu7.8-1ibm3
qemu-kvm 1:2.11+dfsg-1ubuntu7.9
qemu-system-ppc 1:2.11+dfsg-1ubuntu7.8-1ibm3
libvirt0:ppc64el 4.0.0-1ubuntu8.6
libnuma-dev:ppc64el 2.0.11-2.1
libnuma1:ppc64el 2.0.11-2.1
numactl 2.0.11-2.1
numad 0.5+20150602-5
---Debugger---
A debugger is not configured
---Steps to Reproduce---
1. Configure the guest with vcpu pinning and memory binding to one of the numa node.
<cputune>
<vcpupin vcpu='0' cpuset='64'/>
<vcpupin vcpu='1' cpuset='65'/>
<vcpupin vcpu='2' cpuset='66'/>
<vcpupin vcpu='3' cpuset='67'/>
<emulatorpin cpuset='64-67'/>
</cputune>
<numatune>
<memory mode='strict' nodeset='8'/>
</numatune>
2. Start the guest.
3. Check the "numastat" for the guest details.
4. The output doesn't display any data for desired node.
Contact Information = Santwana Samantray/santwana.samantray@in.ibm.com
== Comment: #1 - SANTWANA SAMANTRAY <santwana.samantray@in.ibm.com> - 2019-02-20 23:49:58 ==
== Comment: #4 - SEETEENA THOUFEEK <sthoufee@in.ibm.com> - 2019-02-22 00:40:37 ==
I am not able to replicate in upstream code
We need to cherry pick this patch in numactl 2.0.11-2.1 level.
https://github.com/numactl/numactl/commit/b608687037d873ad82d6318f231b3d6612e8601d
root@ltcgen3:~/numactl# ./numastat -c qemu-system-ppc64
Per-node process memory usage (in MBs) for PID 53294 (qemu-system-ppc)
Node 0 Node 8 Node 252 Node 253 Node 254 Node 255 Total
------ ------ -------- -------- -------- -------- ------
Huge 0 0 0 0 0 0 0
Heap 0 28 0 0 0 0 28
Stack 0 0 0 0 0 0 0
Private 0 103727 0 0 0 0 103727
------- ------ ------ -------- -------- -------- -------- ------
Total 0 103755 0 0 0 0 103755
--------------------------------------------------------------------------------------------------- |
Please test the PPA [1] if it would suit your needs.
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3671
[Impact]
* Some less common numa hierarchies break numactl
* backport upstream change to fix that
- https://github.com/numactl/numactl/commit/b60868703
[Test Case]
* You have to create an "affected" Numa topology
E.g. on a full mem stacked P9 create a guest like:
<vcpu placement='static' current='4'>8</vcpu>
<cputune>
<vcpupin vcpu='0' cpuset='64'/>
<vcpupin vcpu='1' cpuset='65'/>
<vcpupin vcpu='2' cpuset='66'/>
<vcpupin vcpu='3' cpuset='67'/>
<emulatorpin cpuset='64-67'/>
</cputune>
<numatune>
<memory mode='strict' nodeset='8'/>
</numatune>
* Then after starting that numactl will fail to show it's data, for
example:
# numastat -c qemu-system-ppc64
Per-node process memory usage (in MBs) for PID 5738 (qemu-system-ppc)
Node 0 Node 8 ...
------ ------ ...
Huge 0 0 ...
Heap 0 0 ...
Stack 14 0 ...
Private 936 0 ...
------- ------ ------ ...
Total 936 0 ...
(more details on the Host used below)
[Regression Potential]
* The change is rather small just skipping nodes not matching the
expected numbers (important to not crash). If anything then I can
think of a regression where it would skip a numa node that it
would need to access. But I have seen none such case in my tests, so
I hope it will be fine.
[Other Info]
* n/a
---
== Comment: #0 - SANTWANA SAMANTRAY <santwana.samantray@in.ibm.com> - 2019-02-20 23:48:43 ==
---Problem Description---
numastat doesn't display correct information for kvm guests.
The guest is configured with vcpupin from the node8:
Snippet of the guest XML :
<vcpu placement='static' current='4'>8</vcpu>
<cputune>
<vcpupin vcpu='0' cpuset='64'/>
<vcpupin vcpu='1' cpuset='65'/>
<vcpupin vcpu='2' cpuset='66'/>
<vcpupin vcpu='3' cpuset='67'/>
<emulatorpin cpuset='64-67'/>
</cputune>
<numatune>
<memory mode='strict' nodeset='8'/>
</numatune>
== Host Details ==
# lscpu
Architecture: ppc64le
Byte Order: Little Endian
CPU(s): 128
On-line CPU(s) list: 0-127
Thread(s) per core: 4
Core(s) per socket: 16
Socket(s): 2
NUMA node(s): 6
Model: 2.2 (pvr 004e 1202)
Model name: POWER9, altivec supported
CPU max MHz: 3800.0000
CPU min MHz: 2300.0000
L1d cache: 32K
L1i cache: 32K
L2 cache: 512K
L3 cache: 10240K
NUMA node0 CPU(s): 0-63
NUMA node8 CPU(s): 64-127
NUMA node252 CPU(s):
NUMA node253 CPU(s):
NUMA node254 CPU(s):
NUMA node255 CPU(s):
After starting the guest, the numastat doesn't display the guest process to be running in node8.
# numastat -c qemu-system-ppc64
Per-node process memory usage (in MBs) for PID 5738 (qemu-system-ppc)
Node 0 Node 8 Node 252 Node 253 Node 254 Node 255 Total
------ ------ -------- -------- -------- -------- -----
Huge 0 0 0 0 0 0 0
Heap 0 0 0 0 0 0 14
Stack 14 0 0 0 0 0 0
Private 936 0 0 0 0 0 3064
------- ------ ------ -------- -------- -------- -------- -----
Total 936 0 0 0 0 0 3079
# service numad status
* numad.service - numad - The NUMA daemon that manages application locality.
Loaded: loaded (/lib/systemd/system/numad.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2019-02-21 00:43:54 EST; 20s ago
Docs: man:numad
Process: 8091 ExecStart=/usr/bin/numad $DAEMON_ARGS -i 15 (code=exited, status=0/SUCCESS)
Main PID: 8092 (numad)
Tasks: 2 (limit: 19660)
CGroup: /system.slice/numad.service
`-8092 /usr/bin/numad -i 15
Feb 21 00:43:54 ltcgen3 systemd[1]: Starting numad - The NUMA daemon that manages application locality....
Feb 21 00:43:54 ltcgen3 systemd[1]: Started numad - The NUMA daemon that manages application locality..
---uname output---
Linux ltcgen3 4.15.0-1016-ibm-gt #18-Ubuntu SMP Thu Feb 7 16:58:31 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = Witherspoon
== Versions Installed ==
qemu 1:2.11+dfsg-1ubuntu7.8-1ibm3
qemu-kvm 1:2.11+dfsg-1ubuntu7.9
qemu-system-ppc 1:2.11+dfsg-1ubuntu7.8-1ibm3
libvirt0:ppc64el 4.0.0-1ubuntu8.6
libnuma-dev:ppc64el 2.0.11-2.1
libnuma1:ppc64el 2.0.11-2.1
numactl 2.0.11-2.1
numad 0.5+20150602-5
---Debugger---
A debugger is not configured
---Steps to Reproduce---
1. Configure the guest with vcpu pinning and memory binding to one of the numa node.
<cputune>
<vcpupin vcpu='0' cpuset='64'/>
<vcpupin vcpu='1' cpuset='65'/>
<vcpupin vcpu='2' cpuset='66'/>
<vcpupin vcpu='3' cpuset='67'/>
<emulatorpin cpuset='64-67'/>
</cputune>
<numatune>
<memory mode='strict' nodeset='8'/>
</numatune>
2. Start the guest.
3. Check the "numastat" for the guest details.
4. The output doesn't display any data for desired node.
Contact Information = Santwana Samantray/santwana.samantray@in.ibm.com
== Comment: #1 - SANTWANA SAMANTRAY <santwana.samantray@in.ibm.com> - 2019-02-20 23:49:58 ==
== Comment: #4 - SEETEENA THOUFEEK <sthoufee@in.ibm.com> - 2019-02-22 00:40:37 ==
I am not able to replicate in upstream code
We need to cherry pick this patch in numactl 2.0.11-2.1 level.
https://github.com/numactl/numactl/commit/b608687037d873ad82d6318f231b3d6612e8601d
root@ltcgen3:~/numactl# ./numastat -c qemu-system-ppc64
Per-node process memory usage (in MBs) for PID 53294 (qemu-system-ppc)
Node 0 Node 8 Node 252 Node 253 Node 254 Node 255 Total
------ ------ -------- -------- -------- -------- ------
Huge 0 0 0 0 0 0 0
Heap 0 28 0 0 0 0 28
Stack 0 0 0 0 0 0 0
Private 0 103727 0 0 0 0 103727
------- ------ ------ -------- -------- -------- -------- ------
Total 0 103755 0 0 0 0 103755
--------------------------------------------------------------------------------------------------- |
|
| 2019-02-28 12:15:54 |
Christian Ehrhardt |
description |
Please test the PPA [1] if it would suit your needs.
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3671
[Impact]
* Some less common numa hierarchies break numactl
* backport upstream change to fix that
- https://github.com/numactl/numactl/commit/b60868703
[Test Case]
* You have to create an "affected" Numa topology
E.g. on a full mem stacked P9 create a guest like:
<vcpu placement='static' current='4'>8</vcpu>
<cputune>
<vcpupin vcpu='0' cpuset='64'/>
<vcpupin vcpu='1' cpuset='65'/>
<vcpupin vcpu='2' cpuset='66'/>
<vcpupin vcpu='3' cpuset='67'/>
<emulatorpin cpuset='64-67'/>
</cputune>
<numatune>
<memory mode='strict' nodeset='8'/>
</numatune>
* Then after starting that numactl will fail to show it's data, for
example:
# numastat -c qemu-system-ppc64
Per-node process memory usage (in MBs) for PID 5738 (qemu-system-ppc)
Node 0 Node 8 ...
------ ------ ...
Huge 0 0 ...
Heap 0 0 ...
Stack 14 0 ...
Private 936 0 ...
------- ------ ------ ...
Total 936 0 ...
(more details on the Host used below)
[Regression Potential]
* The change is rather small just skipping nodes not matching the
expected numbers (important to not crash). If anything then I can
think of a regression where it would skip a numa node that it
would need to access. But I have seen none such case in my tests, so
I hope it will be fine.
[Other Info]
* n/a
---
== Comment: #0 - SANTWANA SAMANTRAY <santwana.samantray@in.ibm.com> - 2019-02-20 23:48:43 ==
---Problem Description---
numastat doesn't display correct information for kvm guests.
The guest is configured with vcpupin from the node8:
Snippet of the guest XML :
<vcpu placement='static' current='4'>8</vcpu>
<cputune>
<vcpupin vcpu='0' cpuset='64'/>
<vcpupin vcpu='1' cpuset='65'/>
<vcpupin vcpu='2' cpuset='66'/>
<vcpupin vcpu='3' cpuset='67'/>
<emulatorpin cpuset='64-67'/>
</cputune>
<numatune>
<memory mode='strict' nodeset='8'/>
</numatune>
== Host Details ==
# lscpu
Architecture: ppc64le
Byte Order: Little Endian
CPU(s): 128
On-line CPU(s) list: 0-127
Thread(s) per core: 4
Core(s) per socket: 16
Socket(s): 2
NUMA node(s): 6
Model: 2.2 (pvr 004e 1202)
Model name: POWER9, altivec supported
CPU max MHz: 3800.0000
CPU min MHz: 2300.0000
L1d cache: 32K
L1i cache: 32K
L2 cache: 512K
L3 cache: 10240K
NUMA node0 CPU(s): 0-63
NUMA node8 CPU(s): 64-127
NUMA node252 CPU(s):
NUMA node253 CPU(s):
NUMA node254 CPU(s):
NUMA node255 CPU(s):
After starting the guest, the numastat doesn't display the guest process to be running in node8.
# numastat -c qemu-system-ppc64
Per-node process memory usage (in MBs) for PID 5738 (qemu-system-ppc)
Node 0 Node 8 Node 252 Node 253 Node 254 Node 255 Total
------ ------ -------- -------- -------- -------- -----
Huge 0 0 0 0 0 0 0
Heap 0 0 0 0 0 0 14
Stack 14 0 0 0 0 0 0
Private 936 0 0 0 0 0 3064
------- ------ ------ -------- -------- -------- -------- -----
Total 936 0 0 0 0 0 3079
# service numad status
* numad.service - numad - The NUMA daemon that manages application locality.
Loaded: loaded (/lib/systemd/system/numad.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2019-02-21 00:43:54 EST; 20s ago
Docs: man:numad
Process: 8091 ExecStart=/usr/bin/numad $DAEMON_ARGS -i 15 (code=exited, status=0/SUCCESS)
Main PID: 8092 (numad)
Tasks: 2 (limit: 19660)
CGroup: /system.slice/numad.service
`-8092 /usr/bin/numad -i 15
Feb 21 00:43:54 ltcgen3 systemd[1]: Starting numad - The NUMA daemon that manages application locality....
Feb 21 00:43:54 ltcgen3 systemd[1]: Started numad - The NUMA daemon that manages application locality..
---uname output---
Linux ltcgen3 4.15.0-1016-ibm-gt #18-Ubuntu SMP Thu Feb 7 16:58:31 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = Witherspoon
== Versions Installed ==
qemu 1:2.11+dfsg-1ubuntu7.8-1ibm3
qemu-kvm 1:2.11+dfsg-1ubuntu7.9
qemu-system-ppc 1:2.11+dfsg-1ubuntu7.8-1ibm3
libvirt0:ppc64el 4.0.0-1ubuntu8.6
libnuma-dev:ppc64el 2.0.11-2.1
libnuma1:ppc64el 2.0.11-2.1
numactl 2.0.11-2.1
numad 0.5+20150602-5
---Debugger---
A debugger is not configured
---Steps to Reproduce---
1. Configure the guest with vcpu pinning and memory binding to one of the numa node.
<cputune>
<vcpupin vcpu='0' cpuset='64'/>
<vcpupin vcpu='1' cpuset='65'/>
<vcpupin vcpu='2' cpuset='66'/>
<vcpupin vcpu='3' cpuset='67'/>
<emulatorpin cpuset='64-67'/>
</cputune>
<numatune>
<memory mode='strict' nodeset='8'/>
</numatune>
2. Start the guest.
3. Check the "numastat" for the guest details.
4. The output doesn't display any data for desired node.
Contact Information = Santwana Samantray/santwana.samantray@in.ibm.com
== Comment: #1 - SANTWANA SAMANTRAY <santwana.samantray@in.ibm.com> - 2019-02-20 23:49:58 ==
== Comment: #4 - SEETEENA THOUFEEK <sthoufee@in.ibm.com> - 2019-02-22 00:40:37 ==
I am not able to replicate in upstream code
We need to cherry pick this patch in numactl 2.0.11-2.1 level.
https://github.com/numactl/numactl/commit/b608687037d873ad82d6318f231b3d6612e8601d
root@ltcgen3:~/numactl# ./numastat -c qemu-system-ppc64
Per-node process memory usage (in MBs) for PID 53294 (qemu-system-ppc)
Node 0 Node 8 Node 252 Node 253 Node 254 Node 255 Total
------ ------ -------- -------- -------- -------- ------
Huge 0 0 0 0 0 0 0
Heap 0 28 0 0 0 0 28
Stack 0 0 0 0 0 0 0
Private 0 103727 0 0 0 0 103727
------- ------ ------ -------- -------- -------- -------- ------
Total 0 103755 0 0 0 0 103755
--------------------------------------------------------------------------------------------------- |
[Impact]
* Some less common numa hierarchies break numactl
* backport upstream change to fix that
- https://github.com/numactl/numactl/commit/b60868703
[Test Case]
* You have to create an "affected" Numa topology
E.g. on a full mem stacked P9 create a guest like:
<vcpu placement='static' current='4'>8</vcpu>
<cputune>
<vcpupin vcpu='0' cpuset='64'/>
<vcpupin vcpu='1' cpuset='65'/>
<vcpupin vcpu='2' cpuset='66'/>
<vcpupin vcpu='3' cpuset='67'/>
<emulatorpin cpuset='64-67'/>
</cputune>
<numatune>
<memory mode='strict' nodeset='8'/>
</numatune>
* Then after starting that numactl will fail to show it's data, for
example:
# numastat -c qemu-system-ppc64
Per-node process memory usage (in MBs) for PID 5738 (qemu-system-ppc)
Node 0 Node 8 ...
------ ------ ...
Huge 0 0 ...
Heap 0 0 ...
Stack 14 0 ...
Private 936 0 ...
------- ------ ------ ...
Total 936 0 ...
(more details on the Host used below)
[Regression Potential]
* The change is rather small just skipping nodes not matching the
expected numbers (important to not crash). If anything then I can
think of a regression where it would skip a numa node that it
would need to access. But I have seen none such case in my tests, so
I hope it will be fine.
[Other Info]
* n/a
---
== Comment: #0 - SANTWANA SAMANTRAY <santwana.samantray@in.ibm.com> - 2019-02-20 23:48:43 ==
---Problem Description---
numastat doesn't display correct information for kvm guests.
The guest is configured with vcpupin from the node8:
Snippet of the guest XML :
<vcpu placement='static' current='4'>8</vcpu>
<cputune>
<vcpupin vcpu='0' cpuset='64'/>
<vcpupin vcpu='1' cpuset='65'/>
<vcpupin vcpu='2' cpuset='66'/>
<vcpupin vcpu='3' cpuset='67'/>
<emulatorpin cpuset='64-67'/>
</cputune>
<numatune>
<memory mode='strict' nodeset='8'/>
</numatune>
== Host Details ==
# lscpu
Architecture: ppc64le
Byte Order: Little Endian
CPU(s): 128
On-line CPU(s) list: 0-127
Thread(s) per core: 4
Core(s) per socket: 16
Socket(s): 2
NUMA node(s): 6
Model: 2.2 (pvr 004e 1202)
Model name: POWER9, altivec supported
CPU max MHz: 3800.0000
CPU min MHz: 2300.0000
L1d cache: 32K
L1i cache: 32K
L2 cache: 512K
L3 cache: 10240K
NUMA node0 CPU(s): 0-63
NUMA node8 CPU(s): 64-127
NUMA node252 CPU(s):
NUMA node253 CPU(s):
NUMA node254 CPU(s):
NUMA node255 CPU(s):
After starting the guest, the numastat doesn't display the guest process to be running in node8.
# numastat -c qemu-system-ppc64
Per-node process memory usage (in MBs) for PID 5738 (qemu-system-ppc)
Node 0 Node 8 Node 252 Node 253 Node 254 Node 255 Total
------ ------ -------- -------- -------- -------- -----
Huge 0 0 0 0 0 0 0
Heap 0 0 0 0 0 0 14
Stack 14 0 0 0 0 0 0
Private 936 0 0 0 0 0 3064
------- ------ ------ -------- -------- -------- -------- -----
Total 936 0 0 0 0 0 3079
# service numad status
* numad.service - numad - The NUMA daemon that manages application locality.
Loaded: loaded (/lib/systemd/system/numad.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2019-02-21 00:43:54 EST; 20s ago
Docs: man:numad
Process: 8091 ExecStart=/usr/bin/numad $DAEMON_ARGS -i 15 (code=exited, status=0/SUCCESS)
Main PID: 8092 (numad)
Tasks: 2 (limit: 19660)
CGroup: /system.slice/numad.service
`-8092 /usr/bin/numad -i 15
Feb 21 00:43:54 ltcgen3 systemd[1]: Starting numad - The NUMA daemon that manages application locality....
Feb 21 00:43:54 ltcgen3 systemd[1]: Started numad - The NUMA daemon that manages application locality..
---uname output---
Linux ltcgen3 4.15.0-1016-ibm-gt #18-Ubuntu SMP Thu Feb 7 16:58:31 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = Witherspoon
== Versions Installed ==
qemu 1:2.11+dfsg-1ubuntu7.8-1ibm3
qemu-kvm 1:2.11+dfsg-1ubuntu7.9
qemu-system-ppc 1:2.11+dfsg-1ubuntu7.8-1ibm3
libvirt0:ppc64el 4.0.0-1ubuntu8.6
libnuma-dev:ppc64el 2.0.11-2.1
libnuma1:ppc64el 2.0.11-2.1
numactl 2.0.11-2.1
numad 0.5+20150602-5
---Debugger---
A debugger is not configured
---Steps to Reproduce---
1. Configure the guest with vcpu pinning and memory binding to one of the numa node.
<cputune>
<vcpupin vcpu='0' cpuset='64'/>
<vcpupin vcpu='1' cpuset='65'/>
<vcpupin vcpu='2' cpuset='66'/>
<vcpupin vcpu='3' cpuset='67'/>
<emulatorpin cpuset='64-67'/>
</cputune>
<numatune>
<memory mode='strict' nodeset='8'/>
</numatune>
2. Start the guest.
3. Check the "numastat" for the guest details.
4. The output doesn't display any data for desired node.
Contact Information = Santwana Samantray/santwana.samantray@in.ibm.com
== Comment: #1 - SANTWANA SAMANTRAY <santwana.samantray@in.ibm.com> - 2019-02-20 23:49:58 ==
== Comment: #4 - SEETEENA THOUFEEK <sthoufee@in.ibm.com> - 2019-02-22 00:40:37 ==
I am not able to replicate in upstream code
We need to cherry pick this patch in numactl 2.0.11-2.1 level.
https://github.com/numactl/numactl/commit/b608687037d873ad82d6318f231b3d6612e8601d
root@ltcgen3:~/numactl# ./numastat -c qemu-system-ppc64
Per-node process memory usage (in MBs) for PID 53294 (qemu-system-ppc)
Node 0 Node 8 Node 252 Node 253 Node 254 Node 255 Total
------ ------ -------- -------- -------- -------- ------
Huge 0 0 0 0 0 0 0
Heap 0 28 0 0 0 0 28
Stack 0 0 0 0 0 0 0
Private 0 103727 0 0 0 0 103727
------- ------ ------ -------- -------- -------- -------- ------
Total 0 103755 0 0 0 0 103755
--------------------------------------------------------------------------------------------------- |
|
| 2019-02-28 12:17:25 |
Christian Ehrhardt |
numactl (Ubuntu Bionic): status |
In Progress |
Incomplete |
|
| 2019-02-28 12:17:33 |
Christian Ehrhardt |
numactl (Ubuntu Bionic): assignee |
Christian Ehrhardt (paelzer) |
|
|
| 2019-02-28 12:17:40 |
Christian Ehrhardt |
numactl (Ubuntu Cosmic): assignee |
Christian Ehrhardt (paelzer) |
|
|
| 2019-02-28 12:17:41 |
Christian Ehrhardt |
numactl (Ubuntu Cosmic): status |
In Progress |
Incomplete |
|
| 2019-03-03 04:28:15 |
Mathew Hodson |
numactl (Ubuntu): importance |
Undecided |
High |
|
| 2019-03-03 04:28:18 |
Mathew Hodson |
numactl (Ubuntu Bionic): importance |
Undecided |
High |
|
| 2019-03-03 04:28:20 |
Mathew Hodson |
numactl (Ubuntu Cosmic): importance |
Undecided |
High |
|
| 2019-03-05 10:19:30 |
Christian Ehrhardt |
numactl (Ubuntu Bionic): status |
Incomplete |
Triaged |
|
| 2019-03-05 10:19:32 |
Christian Ehrhardt |
numactl (Ubuntu Cosmic): status |
Incomplete |
Triaged |
|
| 2019-03-05 18:42:25 |
Brian Murray |
numactl (Ubuntu Cosmic): status |
Triaged |
Fix Committed |
|
| 2019-03-05 18:42:28 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2019-03-05 18:42:31 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2019-03-05 18:42:35 |
Brian Murray |
tags |
architecture-ppc64le bugnameltc-175674 severity-high targetmilestone-inin--- |
architecture-ppc64le bugnameltc-175674 severity-high targetmilestone-inin--- verification-needed verification-needed-cosmic |
|
| 2019-03-05 18:44:52 |
Brian Murray |
numactl (Ubuntu Bionic): status |
Triaged |
Fix Committed |
|
| 2019-03-05 18:45:03 |
Brian Murray |
tags |
architecture-ppc64le bugnameltc-175674 severity-high targetmilestone-inin--- verification-needed verification-needed-cosmic |
architecture-ppc64le bugnameltc-175674 severity-high targetmilestone-inin--- verification-needed verification-needed-bionic verification-needed-cosmic |
|
| 2019-03-05 19:11:40 |
Andrew Cloke |
ubuntu-power-systems: status |
In Progress |
Fix Committed |
|
| 2019-03-19 16:19:56 |
bugproxy |
tags |
architecture-ppc64le bugnameltc-175674 severity-high targetmilestone-inin--- verification-needed verification-needed-bionic verification-needed-cosmic |
architecture-ppc64le bugnameltc-175674 severity-high targetmilestone-inin18041 verification-needed verification-needed-bionic verification-needed-cosmic |
|
| 2019-03-22 16:11:55 |
Christian Ehrhardt |
tags |
architecture-ppc64le bugnameltc-175674 severity-high targetmilestone-inin18041 verification-needed verification-needed-bionic verification-needed-cosmic |
architecture-ppc64le bugnameltc-175674 severity-high targetmilestone-inin18041 verification-done verification-done-bionic verification-done-cosmic |
|
| 2019-04-25 08:50:17 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2019-04-25 09:00:23 |
Launchpad Janitor |
numactl (Ubuntu Cosmic): status |
Fix Committed |
Fix Released |
|
| 2019-04-25 10:02:23 |
Launchpad Janitor |
numactl (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2019-04-25 10:35:37 |
Frank Heimes |
ubuntu-power-systems: status |
Fix Committed |
Fix Released |
|
