From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: amit.shah@redhat.com, quintela@redhat.com, qemu-devel@nongnu.org,
dgilbert@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/3] migration: Fixups for VMDESC submission
Date: Thu, 05 Mar 2015 10:24:10 -0300 [thread overview]
Message-ID: <1425561850.2464.1@smtp.corp.redhat.com> (raw)
In-Reply-To: <1424696203-76895-1-git-send-email-agraf@suse.de>
Just for the record, I've tested it using the virt-test reproducer and
indeed the problem is fixed with this patchset. I'm sorry for the delay!
Thanks :)
On Mon, Feb 23, 2015 at 9:56 AM, Alexander Graf <agraf@suse.de> wrote:
> After the vmdesc self-describing JSON blob landed upstream, some
> people
> noticed their self-written scripts around migration to fail.
>
> This patch set aims at making the transition to the new VMDESC
> containing
> migration format as smooth as possible for everyone involved.
>
> Alexander Graf (3):
> migration: Read JSON VM description on incoming migration
> migration: Allow to suppress vmdesc submission
> pc: Disable vmdesc submission for old machines
>
> hw/core/machine.c | 20 ++++++++++++++++++++
> hw/i386/pc_piix.c | 1 +
> hw/i386/pc_q35.c | 1 +
> include/hw/boards.h | 1 +
> qemu-options.hx | 3 ++-
> savevm.c | 36 ++++++++++++++++++++++++++++++++----
> 6 files changed, 57 insertions(+), 5 deletions(-)
>
> --
> 1.7.12.4
>
prev parent reply other threads:[~2015-03-05 13:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 12:56 [Qemu-devel] [PATCH v2 0/3] migration: Fixups for VMDESC submission Alexander Graf
2015-02-23 12:56 ` [Qemu-devel] [PATCH v2 1/3] migration: Read JSON VM description on incoming migration Alexander Graf
2015-03-04 11:50 ` Dr. David Alan Gilbert
2015-02-23 12:56 ` [Qemu-devel] [PATCH v2 2/3] migration: Allow to suppress vmdesc submission Alexander Graf
2015-02-23 12:56 ` [Qemu-devel] [PATCH v2 3/3] pc: Disable vmdesc submission for old machines Alexander Graf
2015-03-04 11:53 ` Dr. David Alan Gilbert
2015-03-05 13:24 ` Lucas Meneghel Rodrigues [this message]
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=1425561850.2464.1@smtp.corp.redhat.com \
--to=lmr@redhat.com \
--cc=agraf@suse.de \
--cc=amit.shah@redhat.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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.