From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:54992) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uepdj-0002iW-Pk for qemu-devel@nongnu.org; Tue, 21 May 2013 12:42:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Uepde-0003TY-MA for qemu-devel@nongnu.org; Tue, 21 May 2013 12:42:19 -0400 Received: from mail-oa0-f48.google.com ([209.85.219.48]:49930) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uepde-0003TJ-Hz for qemu-devel@nongnu.org; Tue, 21 May 2013 12:42:14 -0400 Received: by mail-oa0-f48.google.com with SMTP id i4so1105351oah.21 for ; Tue, 21 May 2013 09:42:14 -0700 (PDT) From: Anthony Liguori In-Reply-To: <20130521100136.GE31290@redhat.com> References: <519B2E24.40104@gmail.com> <20130521083953.GB31290@redhat.com> <20130521095527.GB29303@iris.ozlabs.ibm.com> <20130521100136.GE31290@redhat.com> Date: Tue, 21 May 2013 11:42:11 -0500 Message-ID: <871u90z3mk.fsf@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [Qemu-devel] [qemu-devel][libvirt] Default machine type setting for ppc64 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Daniel P. Berrange" , Paul Mackerras Cc: libvir-list@redhat.com, Peter Maydell , Pradipta Kumar Banerjee , Li Zhang , "qemu-devel@nongnu.org" "Daniel P. Berrange" 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 :|