Hide Forgot
Description of problem: I have vm with numactl package and after poweroff and poweron vm numactl -H does not show me any information about numa node. If I reinstall numactl package(yum erase numactl && yum install numactl), it show me normal information(that my vm has one numa node and information about node memory and cpu). Version-Release number of selected component (if applicable): 3.10.0-327.13.1.el7.ppc64le numactl-2.0.9-6.el7_2.ppc64le numactl-libs-2.0.9-6.el7_2.ppc64le How reproducible: always Steps to Reproduce: 1. Install on vm numactl package 2. Poweroff and poweron vm 3. run numactl -H Actual results: nohing Expected results: available: 1 nodes (0) node 0 cpus: 0 node 0 size: 1024 MB node 0 free: 368 MB node distances: node 0 0: 10 Additional info: Before package reinstall: [root@dhcp167-130 ~]# numactl -H nothing After package reinstall: [root@dhcp167-130 ~]# yum erase numactl -y && yum install numactl -y [root@dhcp167-130 ~]# numactl -H available: 1 nodes (0) node 0 cpus: 0 node 0 size: 1024 MB node 0 free: 368 MB node distances: node 0 0: 10
Created attachment 1133662 [details] sosreport I do not sure what logs you need, so I just attach sosreport. If you need any other information I will glad to help you.
Hi Artyom, in which point you made the sosreport? When numactl -H output was empty or after restart?
1) Installed package and checked numactl -H - output exists 2) Poweroff, poweron VM and checked numactl -H - output does not exist 3) Reinstall package and checked numactl -H - output exists 4) ran sosreport command If you need it on some other point of time give me know.
*** Bug 1678561 has been marked as a duplicate of this bug. ***
Hi Leos, I remember to reproduce this bug on a LPAR machine. And after rebasing, it is fixed. I will try to fetch one LPAR to reproduce it. Also set need info from reporter.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2156
Maybe it was connected to the fact that I poweroff it via oVirt, so it just destroyed the VM instance.