From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: -enable-kvm - can it be a required option? Date: Wed, 17 Mar 2010 15:56:26 -0500 Message-ID: <4BA141FA.3060004@codemonkey.ws> References: <4BA13903.40106@msgid.tls.msk.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: KVM list To: Michael Tokarev Return-path: Received: from mail-pw0-f46.google.com ([209.85.160.46]:62484 "EHLO mail-pw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751700Ab0CQU4a (ORCPT ); Wed, 17 Mar 2010 16:56:30 -0400 Received: by pwi5 with SMTP id 5so130594pwi.19 for ; Wed, 17 Mar 2010 13:56:29 -0700 (PDT) In-Reply-To: <4BA13903.40106@msgid.tls.msk.ru> Sender: kvm-owner@vger.kernel.org List-ID: 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