qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Serge Hallyn <serge.hallyn@ubuntu.com>
Cc: "Ryan Harper" <ryan.harper@canonical.com>,
	"Serge Hallyn" <serge.hallyn@canonical.com>,
	"quintela@redhat.com" <quintela@redhat.com>,
	Libvirt <libvir-list@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"Alexander Graf" <agraf@suse.de>, "Alex Bligh" <alex@alex.org.uk>,
	"Cole Robinson" <crobinso@redhat.com>,
	"Amit Shah" <amit.shah@redhat.com>,
	"Bruce Rogers" <brogers@suse.com>,
	"Andreas Färber" <afaerber@suse.de>,
	"Serge E. Hallyn" <serge@hallyn.com>
Subject: Re: [Qemu-devel] [PATCH] [RFC] Add machine type pc-1.0-qemu-kvm for live migrate compatibility with qemu-kvm
Date: Tue, 29 Jul 2014 15:35:53 +0200	[thread overview]
Message-ID: <53D7A339.8000208@redhat.com> (raw)
In-Reply-To: <20140729132743.GA2217@ubuntumail>

Il 29/07/2014 15:27, Serge Hallyn ha scritto:
> Quoting Paolo Bonzini (pbonzini@redhat.com):
>> Il 29/07/2014 15:03, Serge E. Hallyn ha scritto:
>>>
>>> And from there I think the thing to do will be to introduce a transient
>>> alternate package that has the pc-1.0 alias pointing ot pc-1.0-qemu-kvm
>>
>> This should be done in the main package, too.
> 
> That seems like a problem, unless I"m misunderstanding something.  If we do
> that in the main package, then anyone running a pc-1.0 system under the
> qemu package won't be able to migrate.  Wouldn't it be better to have
> pc-1.0 alias by default point to the pc-1.0-qemu machine type?

You'd break that for people who have already upgraded from 12.04 and
14.04 and are keeping the old machine type.  You'd fix it for people who
are upgrading now.

I think providing a smoother upgrade path is worthwhile, even if it
annoys someone else.

Unfortunately the only solution is a lot of testing *before* a release,
and in fact this is why 2.1 was delayed by a migration problem.  Once
the release is out, you'll have to make someone unhappy.

>>> and depends on the legacy pxe rom.
>>
>> If you can make the pxe-virtio.rom file 64k or less, then that would be
>> a good idea for 14.04 in general.  Newer machine types use
>> efi-virtio.rom, so you won't break "-M pc" migration.
> 
> Hm.  No idea offhand how I'd do that, but it sounds worth looking into.

I'm not sure either.  You could simply package the 12.04 ipxe ROMs into
14.04, and add a note about getting the sources for GPL friendliness.

Paolo

  reply	other threads:[~2014-07-29 13:36 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22 18:43 [Qemu-devel] [PATCH] [RFC] Add machine type pc-1.0-qemu-kvm for live migrate compatibility with qemu-kvm Alex Bligh
2014-07-25 16:01 ` Alex Bligh
2014-07-26  7:38   ` Paolo Bonzini
2014-07-27 13:09 ` Alex Bligh
2014-07-27 14:10 ` Andreas Färber
2014-07-27 17:04   ` Alex Bligh
2014-07-27 21:03 ` Alex Bligh
2014-07-29  4:16   ` Serge Hallyn
2014-07-29  7:31     ` Alex Bligh
2014-07-29 13:03       ` Serge E. Hallyn
2014-07-29 13:15         ` Alex Bligh
2014-07-29 13:21         ` Paolo Bonzini
2014-07-29 13:27           ` Serge Hallyn
2014-07-29 13:35             ` Paolo Bonzini [this message]
2014-07-29 13:39               ` Alex Bligh
2014-07-29 13:42                 ` Paolo Bonzini
2014-07-29 13:56                   ` Alex Bligh
2014-07-29 14:00                     ` Paolo Bonzini
2014-07-29 15:05                       ` Alex Bligh
2014-07-29 13:41               ` Serge Hallyn
2014-07-29 13:38           ` Alex Bligh
2014-07-29 13:41             ` Serge Hallyn
2014-08-04 13:34       ` Michael S. Tsirkin
2014-08-04 15:08         ` Serge Hallyn
2014-08-04 15:26           ` Michael S. Tsirkin
2014-08-04 15:38             ` Serge Hallyn
2014-08-04 15:47               ` Alex Bligh
2014-08-04 16:13                 ` 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=53D7A339.8000208@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=alex@alex.org.uk \
    --cc=amit.shah@redhat.com \
    --cc=brogers@suse.com \
    --cc=crobinso@redhat.com \
    --cc=libvir-list@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=ryan.harper@canonical.com \
    --cc=serge.hallyn@canonical.com \
    --cc=serge.hallyn@ubuntu.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).