qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Li Zhang <zhlcindy@gmail.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	libvir-list@redhat.com,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	anthony@codemonkey.ws, Paul Mackerras <paulus@au1.ibm.com>,
	Pradipta Kumar Banerjee <bpradip@in.ibm.com>
Subject: Re: [Qemu-devel] [qemu-devel][libvirt] Default machine type setting for ppc64
Date: Tue, 21 May 2013 23:00:55 +0800	[thread overview]
Message-ID: <519B8C27.8090107@gmail.com> (raw)
In-Reply-To: <20130521092507.GC31290@redhat.com>

On 2013年05月21日 17:25, Daniel P. Berrange wrote:
> On Tue, May 21, 2013 at 05:02:51PM +0800, Li Zhang wrote:
>> On 2013年05月21日 16:45, Peter Maydell wrote:
>>> On 21 May 2013 09:39, Daniel P. Berrange <berrange@redhat.com> wrote:
>>>> Libvirt has always had support for specifying what machine type to use.
>>>> This discussion is simply about what machine type to default to, if the
>>>> user hasn't explicitly asked for one.
>>>>
>>>> QEMU has the notion of a default machine for each target, and that is
>>>> what libvirt uses if the user hasn't specified a machine.  It is not
>>>> libvirt's job to override QEMU's notion of the default machine here,
>>> Agreed; thanks for the clarification.
>>>
>>>> so if the 'mac99' machine type isn't suitable as the default either
>>>> QEMU needs to change that for the ppc target, or the user needs to
>>>> explicitly specify their desired machine type.
>>> OK, that makes sense. So is the problem here just configuration
>>> or is it the next layer above libvirt not being configurable?
>> Currently, the next layer above libvirt is not configurable.
>> It is dependent on this default setting. Users also expect
>> to start one VM successfully by default.
> What is the application above libvirt you are using ? It clearly
> needs to be fixed if it is to use non-x86 archs successfully.

Sorry for replying late. The applications are openstack and ovirt.

Thanks.
-- Li

>
> Daniel

  reply	other threads:[~2013-05-21 15:01 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 [this message]
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
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=519B8C27.8090107@gmail.com \
    --to=zhlcindy@gmail.com \
    --cc=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 \
    /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).