All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: "Daniel P. Berrange" <berrange@redhat.com>,
	Paul Mackerras <paulus@au1.ibm.com>
Cc: libvir-list@redhat.com, Peter Maydell <peter.maydell@linaro.org>,
	Pradipta Kumar Banerjee <bpradip@in.ibm.com>,
	Li Zhang <zhlcindy@gmail.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [qemu-devel][libvirt] Default machine type setting for ppc64
Date: Tue, 21 May 2013 11:42:11 -0500	[thread overview]
Message-ID: <871u90z3mk.fsf@codemonkey.ws> (raw)
In-Reply-To: <20130521100136.GE31290@redhat.com>

"Daniel P. Berrange" <berrange@redhat.com> writes:

> On Tue, May 21, 2013 at 07:55:27PM +1000, Paul Mackerras wrote:
>> On Tue, May 21, 2013 at 09:39:53AM +0100, Daniel P. Berrange wrote:
>> I think libvirt needs some more sensible way to ask qemu what its
>> capabilities are.  Currently it has no way to ask qemu "what machines
>> can you emulate with kvm acceleration?"  If the user has asked for a
>> KVM domain then the default machine should be one that can be provided
>> by KVM.  At present it isn't, on PowerPC.
>
> If QEMU can provide more intelligent info in this respect, then
> libvirt can use it. We're doing the best we can with picking
> defaults given the info QEMU currently provides us.

Thinking about this a little more.

OpenStack pushes a lot of configuration to the nodes themselves instead
of making things dynamic and exposing APIs (think host network
configuration).

QEMU actually does allow a user to change the default machine type via
the global config file so in theory you could do this with OpenStack.

However, since libvirt uses -nouserconfig, this doesn't work in
practice.

Perhaps the right thing to do for OpenStack is to allow for a user
specified configuration file to select things like the default hardware
models/machine types?  Then this could become node configuration instead
of dynamic configuration.

I think it could be useful for general users too.  Every domain requires
a lot of the same boiler plate bits.  I think a lot of configurations
would benefit from being able to set global domain options.

Regards,

Anthony Liguori

>
>
> Daniel
> -- 
> |: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
> |: http://libvirt.org              -o-             http://virt-manager.org :|
> |: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
> |: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

  parent reply	other threads:[~2013-05-21 16:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-21  8:19 [Qemu-devel] [qemu-devel][libvirt] Default machine type setting for ppc64 Li Zhang
2013-05-21  8:24 ` [Qemu-devel] [libvirt] " Li Zhang
2013-05-21  8:31 ` [Qemu-devel] [qemu-devel][libvirt] " Peter Maydell
2013-05-21  8:39   ` Daniel P. Berrange
2013-05-21  8:45     ` Peter Maydell
2013-05-21  9:02       ` Li Zhang
2013-05-21  9:24         ` Peter Maydell
2013-05-21  9:25         ` Daniel P. Berrange
2013-05-21 15:00           ` Li Zhang
2013-05-21  9:55     ` Paul Mackerras
2013-05-21 10:01       ` Daniel P. Berrange
2013-05-21 10:22         ` Peter Maydell
2013-05-21 12:04         ` Anthony Liguori
2013-05-21 12:15           ` Peter Maydell
2013-05-21 14:40           ` Christian Borntraeger
2013-05-21 16:42         ` Anthony Liguori [this message]
2013-05-21 17:12           ` [Qemu-devel] [libvirt] [qemu-devel] " Eric Blake
2013-05-21 17:42             ` Daniel P. Berrange
2013-05-21 20:01               ` Anthony Liguori
2013-05-22 15:26                 ` Li Zhang
2013-05-21 15:17       ` [Qemu-devel] [qemu-devel][libvirt] " Li Zhang
2013-05-21  8:45   ` Li Zhang

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=871u90z3mk.fsf@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=berrange@redhat.com \
    --cc=bpradip@in.ibm.com \
    --cc=libvir-list@redhat.com \
    --cc=paulus@au1.ibm.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=zhlcindy@gmail.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.