RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Boot guest with hmat=on and two numa nodes, set vcpus for both nodes, qemu refuse to start and print error message.

Version-Release number of selected component (if applicable):
qemu-kvm-4.2.0-25.module+el8.2.1+6985+9fd9d514
kernel-4.18.0-193.7.1.el8_2.x86_64

How reproducible:
always

Steps to Reproduce:
1.  
# /usr/libexec/qemu-kvm -M pc,hmat=on -numa node,cpus=0-1 -numa node,cpus=2-3 -smp 4
qemu-kvm: -numa node,cpus=2-3: The initiator of CPU NUMA node 1 should be itself


If set initiator for node 1 as the error message says, still hit it.

# /usr/libexec/qemu-kvm -M pc,hmat=on -numa node,cpus=0-1 -numa node,cpus=2-3,initiator=1 -smp 4
qemu-kvm: -numa node,cpus=2-3,initiator=1: The initiator of CPU NUMA node 1 should be itself
 

Actual results:
QEMU quit with error message.

Expected results:
QEMU can start without error.

Additional info:
Reproducible on rhel8.3-av, qemu-kvm-5.0.0-0.module+el8.3.0+6620+5d5e1420.

Amnon - there isn't a NUMA specific qemu-kvm subcomponent, but the work seems to be someone from your team.

Bulk update: Move RHEL-AV bugs to RHEL9. If necessary to resolve in RHEL8, then clone to the current RHEL8 release.

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Works for me on RHEL8.6 with

   qemu-kvm-6.2.0-1.module+el8.6.0+13725+61ae1949.x86_64

qemu-kvm -m 4G -object memory-backend-ram,id=z,size=4G -M pc,hmat=on -numa node,cpus=0-1,memdev=z -numa node,cpus=2-3 -smp 4

Tested on rhel9.0, the issue is gone too. So change to CURRENTRELEASE.

qemu-kvm-6.2.0-1.el9
5.14.0-39.el9.x86_64

# /usr/libexec/qemu-kvm -M pc,hmat=on -m 4G -object memory-backend-ram,id=mem0,size=2G -object memory-backend-ram,id=mem1,size=2G -numa node,cpus=0-1,memdev=mem0 -numa node,cpus=2-3,memdev=mem1 -smp 4
VNC server running on ::1:5900