Re: [patch 2/2] target-i386: block migration and savevm if invariant tsc is exposed

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Il 28/04/2014 21:23, Eduardo Habkost ha scritto:
> Makes sense.  Basically "-cpu host,migratable=yes" is close to
> libvirt's host-model and Alex Graf's proposed "-cpu best".  Should we
> call it "-cpu best" and drop migratability of "-cpu host"?

"-cpu best" is different from the modes above. It means "use the best
existing CPU model (from the pre-defined table) that can run on this
host".

Yes, it's not exactly the same.  In practice the behavior should be close.

And it would have the same ambiguities we found on "-cpu host": if a CPU
model in the table have invtsc enabled, should it be considered a
candidate for "-cpu best", or not?

No CPU model in the table should have invtsc enabled. :)

Paolo
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux