From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:60069) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UfAwL-00013c-De for qemu-devel@nongnu.org; Wed, 22 May 2013 11:27:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UfAwG-0004Hg-2A for qemu-devel@nongnu.org; Wed, 22 May 2013 11:26:57 -0400 Received: from mail-ie0-x22c.google.com ([2607:f8b0:4001:c03::22c]:60942) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UfAwF-0004HR-TU for qemu-devel@nongnu.org; Wed, 22 May 2013 11:26:51 -0400 Received: by mail-ie0-f172.google.com with SMTP id 16so5549925iea.3 for ; Wed, 22 May 2013 08:26:51 -0700 (PDT) Message-ID: <519CE3AE.6070301@gmail.com> Date: Wed, 22 May 2013 23:26:38 +0800 From: Li Zhang MIME-Version: 1.0 References: <519B2E24.40104@gmail.com> <20130521083953.GB31290@redhat.com> <20130521095527.GB29303@iris.ozlabs.ibm.com> <20130521100136.GE31290@redhat.com> <871u90z3mk.fsf@codemonkey.ws> <519BAAFA.6030101@redhat.com> <20130521174225.GV31290@redhat.com> <87sj1gt843.fsf@codemonkey.ws> In-Reply-To: <87sj1gt843.fsf@codemonkey.ws> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [Qemu-devel] [libvirt] [qemu-devel] Default machine type setting for ppc64 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Peter Maydell , libvir-list@redhat.com, "qemu-devel@nongnu.org" , Alexey Kardashevskiy , Paul Mackerras , Pradipta Kumar Banerjee On 2013年05月22日 04:01, Anthony Liguori wrote: > "Daniel P. Berrange" writes: > >> On Tue, May 21, 2013 at 11:12:26AM -0600, Eric Blake wrote: >>> I have also argued in the past that it would be useful for libvirt to >>> support the idea of a template, where you can specify a domain XML that >>> inherits defaults from the template. We've already done things like >>> this for networking, nwfilter, and even secret management (in domain >>> XML, you declare that you are using a named network object, and that >>> network object serves as the template instead of you having to hard-code >>> all the elements into your domain XML), so we have a design to base it >>> on. But until someone adds such a feature for libvirt, then OpenStack >>> should be passing explicit XML to libvirt, and tracking defaults at the >>> OpenStack layer. >> I don't think the idea of a template belongs in libvirt. > This is fine. But the conversation started with a statement that it's > QEMU's job to define reasonable defaults and libvirt just exposes > those. > > But in QEMU, we punt this problem by letting a user globally override > this default. libvirt hides this ability from the end user. > > So either it's libvirt's problem to solve, or you should expose the > ability to set the global setting within QEMU. We can't just point our > fingers at each other and hope the problem goes away :-) Hi Anthony, Currently, to resolve this problem, can we set 'pseries' as default? Because mac99 doesn't work at all on our platform. Thanks. :) -- Li > > Regards, > > Anthony Liguori > >> Creating basic >> XML structure with relevant defaults pre-filled for a particular usecase >> is something that the libvirt-designer library is aiming to take care of >> for applications. >> >> 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 :|