From: Christian Borntraeger <borntraeger@de.ibm.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>,
Li Zhang <zhlcindy@gmail.com>,
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 16:40:48 +0200 [thread overview]
Message-ID: <519B8770.9030109@de.ibm.com> (raw)
In-Reply-To: <87y5b8bkt3.fsf@codemonkey.ws>
On 21/05/13 14:04, Anthony Liguori wrote:
> "Daniel P. Berrange" <berrange@redhat.com> 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:
>>>> 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.
>>>
>>> We are getting the default changed to 'pseries', at least for cases
>>> where pseries support is compiled in, which isn't necessarily
>>> always. That will of course not satisfy the Freescale guys.
>>>
>>> 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.
>
> We've talked in the past about having an accelerator specific machine
> default. I think this is a perfectly reasonable thing to do and would
> solve the problem for ARM and for PPC.
If we get such thing, then virtio-ccw might also be the right default for kvm
on s390.
Christian
next prev parent reply other threads:[~2013-05-21 14:41 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 [this message]
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=519B8770.9030109@de.ibm.com \
--to=borntraeger@de.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 \
--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).