Description of problem: An Error log display when run virt-install with cpuset argument in non-numa host. Version-Release number of selected component (if applicable): virt-install-1.2.1-6.el7.noarch How reproducible: 100% Steps to Reproduce: 1. Run virt-install command with "--vcpus cpuset=auto" in non-numa host. # virt-install --vcpus cpuset=auto --name cpusettest --memory 1024 --disk none --location http://download.englab.nay.redhat.com/pub/rhel/rel-eng/RHEL-7.1-20150219.1/compose/Server/x86_64/os ERROR Not setting cpuset: Capabilities only show <= 1 cell. Not NUMA capable Actual Results: "ERROR Not setting cpuset: Capabilities only show <= 1 cell. Not NUMA capable" is printed out. but the guest is installed successfully. Expected results: It should not report an Error in debug logs. Additional info:
Upstream commit: commit a8110c6cd709f0d439f8d714cd51b1d3d1b84925 Author: Pavel Hrdina <phrdina> Date: Mon Nov 2 18:03:33 2015 +0100 virt-install: report warning for cpuset=auto on non-NUMA host Currently we report an error but continue with installation, we should report warning instead of error. Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1263903 Signed-off-by: Pavel Hrdina <phrdina>
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
I can reproduce this bug with package: virt-manager-1.2.1-8.el7.noarch virt-install-1.2.1-8.el7.noarch Steps are the same as description above. Then try to verify with new build: virt-manager-1.4.0-1.el7.noarch virt-install-1.4.0-1.el7.noarch Steps: 1. Run virt-install command with "--vcpus cpuset=auto" in non-numa host. # virt-install --vcpus cpuset=auto --name cpusettest --memory 1024 --disk none --location http://download.eng.pek2.redhat.com/pub/rhel/rel-eng/RHEL-6.8-20160414.0/compose/Server/x86_64/os/ Results: 1. There is not error report numa error in debug logs and guest can be installed successfully. According to the result above in the latest version of virt-manager, move this bug from ON_QA to VERIFIED.
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://rhn.redhat.com/errata/RHBA-2016-2269.html