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 ===
We saw VM booting very slowly with the following two settings in the guest config file:
  1. cpuset
  2. vhost-user

It seems this problem happened on 4.11.0-17.el7a.aarch64 kernel, but not with kernel 4.11.0-10.el7a.aarch64. We also found that, at least on arm1 (a Gigabyte machine owned by network team) machine, lower index of physical cores (e.g. 6, 7, 8, 9) will cause the problem. But a larger index numbers allow VM to boot successfully.

==== Setting Details ====
1. cpuset
  <vcpu placement='static' cpuset='6-9'>4</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='6'/>
    <vcpupin vcpu='1' cpuset='7'/>
    <vcpupin vcpu='2' cpuset='8'/>
    <vcpupin vcpu='3' cpuset='9'/>
  </cputune>
2. vhost user
    <interface type='vhostuser'>
      <mac address='00:be:ef:00:ba:be'/>
      <source type='unix' path='/usr/local/var/run/openvswitch/vhost1' mode='client'/>
      <model type='virtio'/>
      <driver queues='4'>
        <host mrg_rxbuf='off'/>
      </driver>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/>
    </interface>

We haven't seen this problem after a clean installation on failed machines. I am cc'ing the original reporter. If he can confirm that it has be resolved, we can close this BZ.

Yes, this has cleared up and I have not seen it again.