All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Glauber Costa <glommer@redhat.com>
Cc: Jan Kiszka <jan.kiszka@web.de>,
	Anthony Liguori <aliguori@us.ibm.com>,
	kvm@vger.kernel.org, avi@redhat.com, markmc@redhat.com
Subject: Re: [PATCH 3/9] change order of kvm_init call.
Date: Mon, 27 Jul 2009 19:28:17 +0100	[thread overview]
Message-ID: <20090727182817.GB15020@redhat.com> (raw)
In-Reply-To: <20090727182008.GH4776@poweredge.glommer>

On Mon, Jul 27, 2009 at 03:20:08PM -0300, Glauber Costa wrote:
> On Mon, Jul 27, 2009 at 08:10:24PM +0200, Jan Kiszka wrote:
> > 
> > I think we should simply resolves this the way upstream does: Do not
> > start if modules are missing and -no-kvm is omitted - or even switch
> > over to -enable-kvm as I think you already suggested in some other
> > thread. Then we can either fail or succeed, but not fall back more or
> > less silently. This falling back of qemu-kvm to tcg is a constant source
> > of confusion anyway.
> 
> switching to --enable-kvm would be my preferred solution, but guys from
> mgmt tools may not like it.

Totally agree that it should never ever fallback to a  different mode than
the one requested, since falling  back from KVM to QEMU simply means the 
user doesn't discover the problem till their  VM install has wasted an 
hour of their time. Personally I would vote for --accelmode qemu|kvm|kqemu 
since it is more future proof, but I'm not too bothered if people prefer 
to have --enable-kvm on the grounds that kqemu is being killed off. 
libvirt just needs a reliable way to request one of qemu, kvm, or kqemu, 
and either get an error message, or have the requested mode work.

Regards,
Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

  reply	other threads:[~2009-07-27 18:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-20 23:10 [PATCH 0/9] More integration with qemu.git Glauber Costa
2009-07-20 23:10 ` [PATCH 1/9] require --enable-kvm Glauber Costa
2009-07-20 23:10   ` [PATCH 2/9] embed kvm_create_context into kvm_init Glauber Costa
2009-07-20 23:10     ` [PATCH 3/9] change order of kvm_init call Glauber Costa
2009-07-20 23:10       ` [PATCH 4/9] use qemu version of kvm initialization Glauber Costa
2009-07-20 23:10         ` [PATCH 5/9] fold second pass " Glauber Costa
2009-07-20 23:10           ` [PATCH 6/9] remove kvm_in* functions Glauber Costa
2009-07-20 23:10             ` [PATCH 7/9] reuse env stop and stopped states Glauber Costa
2009-07-20 23:10               ` [PATCH 8/9] kvm_send_ipi Glauber Costa
2009-07-20 23:10                 ` [PATCH 9/9] remove kvm_abi variable Glauber Costa
2009-07-21  6:11             ` [PATCH 6/9] remove kvm_in* functions Gleb Natapov
2009-07-21 12:23               ` Glauber Costa
2009-07-21 12:18                 ` Gleb Natapov
2009-07-26 18:59       ` [PATCH 3/9] change order of kvm_init call Jan Kiszka
2009-07-27 17:38         ` Glauber Costa
2009-07-27 17:49           ` Anthony Liguori
2009-07-27 18:00             ` Glauber Costa
2009-07-27 18:10               ` Jan Kiszka
2009-07-27 18:20                 ` Glauber Costa
2009-07-27 18:28                   ` Daniel P. Berrange [this message]
2009-07-27 18:38                     ` Glauber Costa
2009-07-27 18:44                       ` Daniel P. Berrange
2009-07-27 19:55                         ` Glauber Costa
2009-07-27 18:34               ` Anthony Liguori

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=20090727182817.GB15020@redhat.com \
    --to=berrange@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=glommer@redhat.com \
    --cc=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --cc=markmc@redhat.com \
    /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.