From: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
Paolo Bonzini <pbonzini@redhat.com>,
Paul Mackerras <paulus@samba.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Alexander Graf <agraf@suse.com>
Subject: Re: [Qemu-devel] machines and versions - why so many?
Date: Tue, 24 Jun 2014 15:38:41 +0300 [thread overview]
Message-ID: <1403613521.20031.4.camel@localhost.localdomain> (raw)
In-Reply-To: <53A89F11.5060003@suse.de>
On Mon, 2014-06-23 at 23:41 +0200, Andreas Färber wrote:
> Am 23.06.2014 23:35, schrieb Alexey Kardashevskiy:
> > Looks like I must copy PC_COMPAT_X_X as PSERIES_COMPAT_X_X starting 1.6 (or
> > 1.7 - whichever starts supporting migration well enough on pseries) because
> > pretty much of what they do is tweaking PCI devices and we can have all of
> > these devices on pseries. And then keep an eye on what is happening in PC
> > world to copy same tweaks to pseries as they come. Is that correct?
>
> Please don't. There's a series by Marcel on the list converting those PC
> macros to QOM.
Actually, I think you are referring to is Eduardo's series :)
http://lists.gnu.org/archive/html/qemu-devel/2014-06/msg03155.html
Thanks,
Marcel
> You already have a QOM sPAPR machine, so you should just
> derive new legacy types as needed and override things there.
>
> Also, -machine *is* the global mechanism we have to tell QEMU which
> version you want, it's a shorthand for setting a list of global
> properties. Don't forget that QEMU can be used without libvirt, so the
> knowledge of which properties to set for which version is kept in QEMU.
>
> Cheers,
> Andreas
>
next prev parent reply other threads:[~2014-06-24 12:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 14:15 [Qemu-devel] machines and versions - why so many? Alexey Kardashevskiy
2014-06-23 14:59 ` Paolo Bonzini
2014-06-23 21:35 ` Alexey Kardashevskiy
2014-06-23 21:41 ` Andreas Färber
2014-06-23 22:33 ` Alexey Kardashevskiy
2014-06-24 5:21 ` Paolo Bonzini
2014-06-24 11:15 ` Andreas Färber
2014-06-24 13:05 ` Alexey Kardashevskiy
2014-06-24 12:38 ` Marcel Apfelbaum [this message]
2014-06-23 21:41 ` Peter Maydell
2014-06-24 5:15 ` Paolo Bonzini
2014-06-24 5:37 ` Alexey Kardashevskiy
2014-06-24 8:17 ` Markus Armbruster
2014-06-24 9:10 ` Alexey Kardashevskiy
2014-06-24 11:22 ` Andreas Färber
2014-06-24 12:56 ` Alexey Kardashevskiy
2014-06-23 15:16 ` Markus Armbruster
2014-06-24 1:06 ` Alexey Kardashevskiy
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=1403613521.20031.4.camel@localhost.localdomain \
--to=marcel.apfelbaum@gmail.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.com \
--cc=aik@ozlabs.ru \
--cc=marcel.a@redhat.com \
--cc=paulus@samba.org \
--cc=pbonzini@redhat.com \
--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).