qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PULL 00/34]  migration thread and queue
Date: Fri, 21 Dec 2012 15:27:18 +0100	[thread overview]
Message-ID: <50D471C6.7000105@redhat.com> (raw)
In-Reply-To: <87ehikmeqj.fsf@codemonkey.ws>

Il 21/12/2012 01:27, Anthony Liguori ha scritto:
> #!/bin/sh
> 
> gzip -d -c lidb.ssmall.img.gz | \
>     ~/build/qemu/x86_64-softmmu/qemu-system-x86_64 -cdrom \
>     ~/isos/OCDC-lucid-Test-Drive-20110523_140333.iso -enable-kvm -m 2G \
>     -incoming exec:dd
> 
> With lidb.ssmall.img.gz being generated from a 'migrate exec:dd of=...'
> from qemu.git just a week or two ago.

So it breaks *incoming* migration, which would restrict the problem to
the beginning of the patch (reorganization of the RAM block list).
Everything else touches only outgoing migration.

However, I tested bidirectional migration between origin/master and
Juan's branch and it passed

  x86_64-softmmu/qemu-system-x86_64 \
    -drive if=virtio,cache=none,file=/../images/jeos-17-64.qcow2 \
    -vnc :1 -incoming "exec:cat foo" --enable-kvm

I also tested both my and Juan's branches and they both pass all
migration tests.

> I can't bisect tonight but can attempt to tomorrow.  How has this been
> tested?

Indeed old->new and new->old migration wasn't tested AFAIK.  Not by me
at least.

Paolo

> I'm a little concerned here about the timing.  With the Christmas
> and New Years holiday we're pretty darn close to soft freeze for 1.4.
> 
> Has this series gone through a full autotest run with multiple guests?

  parent reply	other threads:[~2012-12-21 14:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-20 23:02 [Qemu-devel] [PULL 00/34] migration thread and queue Juan Quintela
2012-12-21  0:27 ` Anthony Liguori
2012-12-21  1:39   ` Juan Quintela
2012-12-21 12:35     ` Juan Quintela
2012-12-21 13:35       ` Anthony Liguori
2012-12-21 12:36     ` Paolo Bonzini
2012-12-21 13:20       ` Juan Quintela
2012-12-21 13:39       ` Anthony Liguori
2012-12-21 13:48         ` Paolo Bonzini
2012-12-21 17:21     ` Juan Quintela
2012-12-21  8:25   ` Paolo Bonzini
2012-12-21 14:14   ` Anthony Liguori
2012-12-21 14:27   ` Paolo Bonzini [this message]
2012-12-22  2:22 ` Anthony Liguori
  -- strict thread matches above, loose matches on Subject: below --
2012-12-21 19:41 Juan Quintela
2012-12-27 15:30 ` Alexandre DERUMIER
2012-12-27 15:44   ` Paolo Bonzini
2012-12-27 15:51     ` Alexandre DERUMIER
2012-12-27 16:08       ` Paolo Bonzini
2012-12-27 16:32         ` Alexandre DERUMIER

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=50D471C6.7000105@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=anthony@codemonkey.ws \
    --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 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).