OpenStack Compute (nova)

  1. Bug #1741230
  2. Comment #6

Comment 6 for bug 1741230

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/530965
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=8bc7b950b7c0a3c80cdd120fe4df97c14848c344
Submitter: Zuul
Branch: master

commit 8bc7b950b7c0a3c80cdd120fe4df97c14848c344
Author: Marcin Juszkiewicz <email address hidden>
Date: Wed Jan 3 17:44:27 2018 +0100

    libvirt: use 'host-passthrough' as default on AArch64

    Nova is assuming 'host-model' for KVM/QEMU setup.

    On AArch64 it results in "libvirtError: unsupported configuration: CPU
    mode 'host-model' for aarch64 kvm domain on aarch64 host is not
    supported by hypervisor" message.

    AArch64 lacks 'host-model' support because neither libvirt nor QEMU
    are able to tell what the host CPU model exactly is. And there is no
    CPU description code for ARM(64) at this point.

    So instead we fallback to 'host-passthrough' to get VM instances
    running. This will completely break live migration, *unless* all the
    Compute nodes (running libvirtd) have *identical* CPUs.

    Small summary: https://marcin.juszkiewicz.com.pl/2018/01/04/today-i-was-fighting-with-nova-no-idea-who-won/

    Closes-bug: #1741230

    Co-authored-by: Kevin Zhao <email address hidden>
    Co-authored-by: Marcin Juszkiewicz <email address hidden>

    Change-Id: Iafb5f1790d68489db73b9f0549333108c6426a00