mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-10-31 18:33:11 +00:00
7e0a310498
For backward compatibility with older versions of libvirt CPU models in our CPU map are mostly immutable. We only changed them in a few specific cases after showing it was safe. Sometimes QEMU developers realize a specific feature should not be part of a particular (or any) CPU model because it can never be enabled automatically without further configuration. But we couldn't follow them because doing so would break migration to older libvirt. If QEMU drops feature F from CPU model M because F could not be enabled automatically anyway, asking for M would never enable F. Even with older QEMU versions. Naively removing F from libvirt's definition of M would seem to work nicely on a single host. Libvirt would consider M to be compatible with hosts CPU that do not support F. However, trying to migrate domains using M without explicitly enabling or disabling F could fail, because older libvirt would think F was enabled (it is part of M there), but QEMU reports it as disabled once started. Thus we can remove such feature from a libvirt's CPU model, but we have to make sure any CPU definition using the affected model will always explicitly mention the state of the removed feature. https://bugzilla.redhat.com/show_bug.cgi?id=1798004 Signed-off-by: Jiri Denemark <jdenemar@redhat.com> Reviewed-by: Tim Wiederhake <twiederh@redhat.com> |
||
|---|---|---|
| .. | ||
| cpu_arm_data.h | ||
| cpu_arm.c | ||
| cpu_arm.h | ||
| cpu_map.c | ||
| cpu_map.h | ||
| cpu_ppc64_data.h | ||
| cpu_ppc64.c | ||
| cpu_ppc64.h | ||
| cpu_s390.c | ||
| cpu_s390.h | ||
| cpu_x86_data.h | ||
| cpu_x86.c | ||
| cpu_x86.h | ||
| cpu.c | ||
| cpu.h | ||
| meson.build | ||