Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/libvirt-real-time. Description: The CPU pinning feature added to the ability to assigned guest virtual CPUs to dedicated host CPUs, providing guarantees for CPU time and improved worst case latency for CPU scheduling. The real time feature builds on that work to provide stronger guarantees for worst case schedular latency for vCPUs. Specification URL (additional information): None
*** Bug 1273876 has been marked as a duplicate of this bug. ***
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Verified on openstack-nova-api.noarch 1:14.0.0-0.20160929203854.59653c6.el7ost openstack-nova-cert.noarch 1:14.0.0-0.20160929203854.59653c6.el7ost openstack-nova-common.noarch 1:14.0.0-0.20160929203854.59653c6.el7ost openstack-nova-compute.noarch 1:14.0.0-0.20160929203854.59653c6.el7ost openstack-nova-conductor.noarch 1:14.0.0-0.20160929203854.59653c6.el7ost openstack-nova-console.noarch 1:14.0.0-0.20160929203854.59653c6.el7ost openstack-nova-novncproxy.noarch 1:14.0.0-0.20160929203854.59653c6.el7ost openstack-nova-scheduler.noarch 1:14.0.0-0.20160929203854.59653c6.el7ost Logs ===== Please check "attachment 1210569 [details]" for details.
Updating information about the automation used - https://review.gerrithub.io/#/c/298301/1/rhostest_tempest_plugin/tests/scenario/test_libvirt_realtime_instance.py
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/RHEA-2016-2948.html