Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

core: update cpuTopology on status changes #525

Merged
merged 1 commit into from
Jul 25, 2022

Commits on Jul 18, 2022

  1. core: update cpuTopology on status changes

    Previously, once the CPU topology was initialized in
    the VdsManager, it was not possible to change it without
    the restart of the engine. There are 2 use cases:
    
    1. When adding a new host, the manager is created, but no
    CPU topology has been reported yet. As a result, the host
    would act as if it does not support exclusive pinning until
    the engine is restarted.
    2. Changing the CPU topology of the host (not a common scenario,
    but happens during development when using hosts in a virtual machine).
    
    This patch updates the CPU topology in the VmManager if the state
    of the host changes and the CPU topology has not been initialized yet.
    
    Bug-Url: https://bugzilla.redhat.com/2104858
    ljelinkova committed Jul 18, 2022
    Configuration menu
    Copy the full SHA
    216132c View commit details
    Browse the repository at this point in the history