About emulator thread pinning in Red Hat OpenStack Platform

Solution Verified - Updated -

Issue

  • About the configuration of emulator thread pinning in Red Hat OpenStack Platform.

  • About the impact of using virsh emulatorpin in virtual environments, particularly in Red Hat OpenStack Platform with NFV.

  • How nova behaves in Red Hat OpenStack Platform 10 and above, and how administrators should place qemu-kvm's emulator threads to avoid spurious packet loss, especially when isolcpus is used.

  • In the instance log:

unable to map backing store for guest RAM: Cannot allocate memory

Environment

  • Red Hat OpenStack Platform 10 (RHOSP)
  • Red Hat OpenStack Platform 13 (RHOSP)
  • Red Hat OpenStack Platform 15 (RHOSP)
  • Red Hat OpenStack Platform 16 (RHOSP)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content