On 03/02/2010 12:25 PM, Glauber Costa wrote:
On Tue, Mar 02, 2010 at 01:31:05AM -0300, Marcelo Tosatti wrote:
On Fri, Feb 26, 2010 at 05:12:19PM -0300, Glauber Costa wrote:
This option deprecates --enable-kvm. It is a more flexible option,
that makes use of qemu-opts, and allow us to pass on options to enable or
disable kernel irqchip, for example.
Signed-off-by: Glauber Costa<glommer@xxxxxxxxxx>
Really have to replace -enable-kvm? Can't you keep compatibility for it?
We don't have to , but I'd rather deprecate it. I don't feel strongly, though.
It needs to stay.
For enabling/disabling, if you don't like -enable-kvm, I'd suggest
thinking about modeling it through CPU. For instance:
-cpu host,accel=kvm|tcg|kvm,tcg
Since we already specify CPU's in a global config, if you took this
approach, it would make it possible to tweak the default kvm vs. tcg
selection within the config file so a user could control whether vms
were created with tcg or kvm by default or whether it tried kvm and then
fell back to tcg.
Regards,
Anthony Liguori
--
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
--
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
