From: "Daniel P. Berrange" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: libvir-list@redhat.com,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Li Zhang <zhlcindy@gmail.com>,
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 09:39:53 +0100 [thread overview]
Message-ID: <20130521083953.GB31290@redhat.com> (raw)
In-Reply-To: <CAFEAcA9rVfUOYuwmrAaQkd1rF8EiMmk_BLuGBab1CtpfzW5OnQ@mail.gmail.com>
On Tue, May 21, 2013 at 09:31:26AM +0100, Peter Maydell wrote:
> On 21 May 2013 09:19, Li Zhang <zhlcindy@gmail.com> wrote:
> > We encounter this problem in openstack which always use
> > default machine type. Currently, QEMU sets mac99 as default
> > setting for ppc64 but it doesn't work on our platform at all.
> >
> > I tried to fix this in libvirt which it is not acceptable because
> > libvirt only considers to get default setting from QEMU.
>
> This will need to be fixed for ARM -- the whole idea of there
> being a sensible "default machine type" and it being the one
> QEMU starts by default is pretty x86-centric. libvirt needs
> to have support for specifying which machine to use.
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,
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.
Regards,
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 :|
next prev parent reply other threads:[~2013-05-21 8:40 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 [this message]
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
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=20130521083953.GB31290@redhat.com \
--to=berrange@redhat.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 \
--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 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).