From: Anthony Liguori <anthony@codemonkey.ws>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: KVM list <kvm@vger.kernel.org>
Subject: Re: -enable-kvm - can it be a required option?
Date: Wed, 17 Mar 2010 15:56:26 -0500 [thread overview]
Message-ID: <4BA141FA.3060004@codemonkey.ws> (raw)
In-Reply-To: <4BA13903.40106@msgid.tls.msk.ru>
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
prev parent reply other threads:[~2010-03-17 20:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 20:18 -enable-kvm - can it be a required option? Michael Tokarev
2010-03-17 20:56 ` Anthony Liguori [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BA141FA.3060004@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.