** Description changed: + [Impact] + + * virsh nodecpumap --pretty --pretty shows wrong result on machine with + many cores + + * Since admin and scripts might rely on those they should be fixed. + Not only are they not nice, they are depending on the case even wrong + sometimes. + + * an example is like: + virsh nodecpumap --pretty + CPUs present: 120 + CPUs online: 120 + CPU map: 0-119,192,196,199,258,262,264,267,269-270,272-273,276-278,284-286,290-291,293-294,296,301-302,304,307-310,314,316,318,320,322,325-326,331-334,338,340-342,802-803,805,807-809,813-814,816-818,821-822,825,828-829,831,833,836 + + + [Test Case] + + * Go to a huge machine with many CPUs (a virtual machine with faked vcpus + might help, but stay aware of issues with 2nd level virtualization) + + * run "virsh nodecpumap --pretty" + + * Tests with extra splits into numa nodes can be done, but are not + necessary to show the effect + + [Regression Potential] + + * Fix is upstream quite while now without further changes which should + make it safe. + + * Also since the code is restricted to "virsh nodecpumap" and not reused + any potential regression should be limited to that sub-command which is + nice for some use-cases but not a core function in general. + + [Other Info] + + * n/a + + + ----- original report ------ + + Please cherry pick this issue. https://bugzilla.redhat.com/show_bug.cgi?id=1329819 commit 3a703b8120d9f996840bd315b6f74c45a7e98aad
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659769 Title: virsh nodecpumap --pretty shows unwanted cpu map output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1659769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
