qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Li Zhang <zhlcindy@gmail.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	libvir-list@redhat.com,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Alexey Kardashevskiy <aik@au1.ibm.com>,
	Paul Mackerras <paulus@au1.ibm.com>,
	Pradipta Kumar Banerjee <bpradip@in.ibm.com>
Subject: Re: [Qemu-devel] [libvirt] [qemu-devel] Default machine type setting for ppc64
Date: Wed, 22 May 2013 23:26:38 +0800	[thread overview]
Message-ID: <519CE3AE.6070301@gmail.com> (raw)
In-Reply-To: <87sj1gt843.fsf@codemonkey.ws>

On 2013年05月22日 04:01, Anthony Liguori wrote:
> "Daniel P. Berrange" <berrange@redhat.com> 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 :|

  reply	other threads:[~2013-05-22 15:27 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
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 [this message]
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=519CE3AE.6070301@gmail.com \
    --to=zhlcindy@gmail.com \
    --cc=aik@au1.ibm.com \
    --cc=anthony@codemonkey.ws \
    --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 \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).