From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "Ryan Harper" <ryan.harper@canonical.com>,
"Serge Hallyn" <serge.hallyn@canonical.com>,
quintela@redhat.com, Libvirt <libvir-list@redhat.com>,
"Serge Hallyn" <serge.hallyn@ubuntu.com>,
"Markus Armbruster" <armbru@redhat.com>,
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 v4] Add machine parameter qemu-kvm-migration for live migrate compatibility with qemu-kvm
Date: Sun, 05 Oct 2014 15:30:23 +0200 [thread overview]
Message-ID: <543147EF.3040905@redhat.com> (raw)
In-Reply-To: <20141005124852.GA21294@redhat.com>
Il 05/10/2014 14:48, Michael S. Tsirkin ha scritto:
> In fact, if the pc_piix bits are dropped from the patch,
> you get a generic patchset that does exactly what you ask,
> correct?
>
> Downstream can then enable qemu-kvm compatibility by adding:
>
> -global cirrus-vga.vgamem_mb=16 -global pit-common.qemu-kvm-migration=on
> -global PIIX4_PM.qemu-kvm-migration=on
Yes.
Paolo
next prev parent reply other threads:[~2014-10-05 13:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 19:34 [Qemu-devel] [PATCH v4] Add machine parameter qemu-kvm-migration for live migrate compatibility with qemu-kvm Alex Bligh
2014-09-22 19:34 ` Alex Bligh
2014-09-28 15:30 ` Michael S. Tsirkin
2014-09-28 20:33 ` Alex Bligh
2014-09-29 7:02 ` Markus Armbruster
2014-10-05 7:00 ` Paolo Bonzini
2014-10-05 10:26 ` Alex Bligh
2014-10-05 12:26 ` Paolo Bonzini
2014-10-05 12:48 ` Michael S. Tsirkin
2014-10-05 13:30 ` Paolo Bonzini [this message]
2014-09-29 10:08 ` Michael S. Tsirkin
2014-09-29 10:13 ` Alex Bligh
2014-09-29 14:52 ` Serge E. Hallyn
2014-10-04 16:29 ` Alex Bligh
2014-09-24 8:05 ` Markus Armbruster
2014-09-24 8:29 ` Alex Bligh
2014-09-24 8:38 ` Michael Tokarev
2014-09-25 8:02 ` Dr. David Alan Gilbert
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=543147EF.3040905@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=armbru@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).