Re: [Qemu-devel] [PATCH v4 15/18] target-i386: Set migratable=yes by default

2014-05-16 Thread Marcelo Tosatti
On Wed, Apr 30, 2014 at 01:48:42PM -0300, Eduardo Habkost wrote: > Having only migratable flags reported by default on the "host" CPU model > is safer for the following reasons: > > * Existing users may expect "-cpu host" to be migration-safe, if they >take care of always using compatible hos

Re: [Qemu-devel] [PATCH v4 15/18] target-i386: Set migratable=yes by default

2014-05-15 Thread Eduardo Habkost
On Thu, May 15, 2014 at 10:07:12PM +0200, Andreas Färber wrote: > Am 30.04.2014 18:48, schrieb Eduardo Habkost: > > Having only migratable flags reported by default on the "host" CPU model > > is safer for the following reasons: > > > > * Existing users may expect "-cpu host" to be migration-safe

Re: [Qemu-devel] [PATCH v4 15/18] target-i386: Set migratable=yes by default

2014-05-15 Thread Andreas Färber
Am 30.04.2014 18:48, schrieb Eduardo Habkost: > Having only migratable flags reported by default on the "host" CPU model > is safer for the following reasons: > > * Existing users may expect "-cpu host" to be migration-safe, if they >take care of always using compatible host CPUs, host kernel

[Qemu-devel] [PATCH v4 15/18] target-i386: Set migratable=yes by default

2014-04-30 Thread Eduardo Habkost
Having only migratable flags reported by default on the "host" CPU model is safer for the following reasons: * Existing users may expect "-cpu host" to be migration-safe, if they take care of always using compatible host CPUs, host kernels, and QEMU versions. * Users who don't care aboug m