From: Serge Hallyn <serge.hallyn@ubuntu.com>
To: Alex Bligh <alex@alex.org.uk>
Cc: "Ryan Harper" <ryan.harper@canonical.com>,
"Alexander Graf" <agraf@suse.de>,
"quintela@redhat.com" <quintela@redhat.com>,
Libvirt <libvir-list@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Amit Shah" <amit.shah@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
"Serge E. Hallyn" <serge@hallyn.com>
Subject: Re: [Qemu-devel] [libvirt] [PATCH v3 2/2] Add configure option --enable-pc-1-0-qemu-kvm
Date: Tue, 23 Sep 2014 00:12:13 +0000 [thread overview]
Message-ID: <20140923001213.GL8796@ubuntumail> (raw)
In-Reply-To: <C0E544C4-D1A9-4301-AA7B-1239573078D0@alex.org.uk>
Quoting Alex Bligh (alex@alex.org.uk):
>
> On 22 Sep 2014, at 20:10, Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> > I'm arguing against special-casing pc-1.0. Just apply the patch to
> > Ubuntu downstream and call it a day.
> >
> > It's perfectly normal for machine types to be part of the downstream
> > (not so secret) sauce.
>
> Well, I've just sent through a version that works as a machine
> parameter instead. If upstream doesn't like this, I'd prefer
> downstream took v2 of the patch (which makes -M pc-1.0 work)
> instead. That's also what Serge tested.
Yeah, prefer v2 as well. Sorry if that means wasted time on your
part.
Though I'm also thinking I prefer to have pc-1.0-precise defined in
both precise's qemu-kvm 1.0, and later qemu 2.x, and requiring some
purely-on-precise action to switch the machine type from pc-1.0 to
pc-1.0-precise before migrating to trusty/later.
But as I mentioned elsewhere there's still the concerns of (a) how
much other still (like virito-net) will still break, and (b) the
practical issues of how to ship the old roms.
-serge
next prev parent reply other threads:[~2014-09-23 0:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-21 14:38 [Qemu-devel] [PATCH v3 0/2] Add machine type pc-1.0-qemu-kvm for live migrate compatibility with qemu-kvm Alex Bligh
2014-09-21 14:38 ` [Qemu-devel] [PATCH v3 1/2] " Alex Bligh
2014-09-22 11:50 ` Michael S. Tsirkin
2014-09-22 12:28 ` Alex Bligh
2014-09-22 12:38 ` Michael S. Tsirkin
2014-09-21 14:38 ` [Qemu-devel] [PATCH v3 2/2] Add configure option --enable-pc-1-0-qemu-kvm Alex Bligh
2014-09-22 11:36 ` Michael S. Tsirkin
2014-09-22 11:42 ` [Qemu-devel] [libvirt] " Daniel P. Berrange
2014-09-22 11:53 ` Michael S. Tsirkin
2014-09-22 15:24 ` Markus Armbruster
2014-09-22 15:36 ` Michael S. Tsirkin
2014-09-22 15:47 ` Serge Hallyn
2014-09-22 15:44 ` Paolo Bonzini
2014-09-22 17:30 ` Alex Bligh
2014-09-22 19:10 ` Paolo Bonzini
2014-09-22 19:36 ` Alex Bligh
2014-09-23 0:12 ` Serge Hallyn [this message]
2014-09-22 11:50 ` [Qemu-devel] " Alex Bligh
2014-09-22 12:10 ` Michael S. Tsirkin
2014-09-22 13:05 ` Alex Bligh
2014-09-22 15:45 ` Andreas Färber
2014-09-22 16:54 ` Alex Bligh
2014-09-22 17:26 ` Markus Armbruster
2014-09-23 3:46 ` Michael S. Tsirkin
2014-09-23 3:44 ` Michael S. Tsirkin
2014-09-22 15:32 ` Markus Armbruster
2014-09-22 17:21 ` Michael S. Tsirkin
2014-09-23 7:59 ` Markus Armbruster
2014-09-23 8:24 ` Michael S. Tsirkin
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=20140923001213.GL8796@ubuntumail \
--to=serge.hallyn@ubuntu.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=alex@alex.org.uk \
--cc=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=libvir-list@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=ryan.harper@canonical.com \
--cc=serge@hallyn.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).