All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Alex Bligh <alex@alex.org.uk>
Cc: "Ryan Harper" <ryan.harper@canonical.com>,
	"Serge Hallyn" <serge.hallyn@canonical.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Libvirt <libvir-list@redhat.com>,
	"Serge Hallyn" <serge.hallyn@ubuntu.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"Alexander Graf" <agraf@suse.de>,
	"quintela@redhat.com" <quintela@redhat.com>,
	"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:42:17 +0200	[thread overview]
Message-ID: <53D7A4B9.40901@redhat.com> (raw)
In-Reply-To: <EB8D6950-7177-460A-A7BD-802D8A81B91C@alex.org.uk>

Il 29/07/2014 15:39, Alex Bligh ha scritto:
>> > 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.
> This would be my preference (or in Ubuntu's case, add it to the ipxe-qemu
> package) but I think it should only be used when the legacy machine type
> is used or it will break inbound migrations from other 14.04 machines
> started with 128k ROMs (AIUI).

"-M pc" and its alias "-M pc-i440fx-2.0" doesn't use pxe-virtio.rom at
all (at least upstream).  Does Ubuntu 14.04 have efi-virtio.rom?

It would break "-M pc-1.0" started on older 14.04, but I think that's
acceptable.

Paolo

  reply	other threads:[~2014-07-29 13:42 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
2014-07-29 13:39               ` Alex Bligh
2014-07-29 13:42                 ` Paolo Bonzini [this message]
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=53D7A4B9.40901@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.