Re: -enable-kvm - can it be a required option?

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

 



On 03/17/2010 03:18 PM, Michael Tokarev wrote:
What I mean is: if asked to enable kvm but kvm
can't be initialized for some reason (lack of
virt extensions on the cpu, permission denied
and so on), can we stop with a fatal error
instead of continuing in emulated mode?

What I've been thinking, is that we should make kvm enablement a -cpu option. Something like:

-cpu host,accel=kvm
-cpu host,accel=tcg
-cpu host,accel=kvm:tcg

(1) would be KVM only, (2) would be TCG only, (3) would be KVM falling back to TCG.

What's nice about this approach, is that we already pull CPU model definitions from a global config file which means that you could tweak this parameter to your liking.

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

[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