diff options
| author | Eduardo Habkost <ehabkost@redhat.com> | 2015-08-26 13:25:44 -0300 |
|---|---|---|
| committer | Eduardo Habkost <ehabkost@redhat.com> | 2015-10-27 16:12:15 -0200 |
| commit | 15e41345906d29a319cc9cdf566347bf79134d24 (patch) | |
| tree | 1969be5dbe7e4a673837ceecae316d49a5a0b8c2 /target-moxie | |
| parent | 712b4243c761cb6ab6a4367a160fd2a42e2d4b76 (diff) | |
| download | qemu-15e41345906d29a319cc9cdf566347bf79134d24.tar.gz qemu-15e41345906d29a319cc9cdf566347bf79134d24.tar.bz2 qemu-15e41345906d29a319cc9cdf566347bf79134d24.zip | |
target-i386: Enable "check" mode by default
Current default behavior of QEMU is to silently disable features that
are not supported by the host when a CPU model is requested in the
command-line. This means that in addition to risking breaking guest ABI
by default, we are silent about it.
I would like to enable "enforce" by default, but this can easily break
existing production systems because of the way libvirt makes assumptions
about CPU models today (this will change in the future, once QEMU
provide a proper interface for checking if a CPU model is runnable).
But there's no reason we should be silent about it. So, change
target-i386 to enable "check" mode by default so at least we have some
warning printed to stderr (and hopefully logged somewhere) when QEMU
disables a feature that is not supported by the host system.
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Diffstat (limited to 'target-moxie')
0 files changed, 0 insertions, 0 deletions