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:
While trying to launch a VM on RHEL 7, with the memory pinning to specific domain, I am getting the following error

error: Failed to start domain VM1
error: internal error: process exited while connecting to monitor: kvm_init_vcpu failed: Cannot allocate memory

XML Snippet: 
<vcpu placement='static'>2</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='8'/>
    <vcpupin vcpu='1' cpuset='9'/>
  </cputune>
  <numatune>
    <memory mode='strict' nodeset='1'/>
  </numatune>

If I replace the nodeset with '0', the VM was launching properly.
I have sufficient memory for both the NUMA nodes & all the NICs were attached to the NUMA node 1.
[root@localhost ~]# virsh freecell 0
0: 63849676 KiB

[root@localhost ~]# virsh freecell 1
1: 64732832 KiB


Version-Release number of selected component (if applicable):
[root@localhost ~]# virsh --version
1.1.1

qemu version: 1.5.3

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

*** This bug has been marked as a duplicate of bug 1010885 ***