From: Juan Quintela <quintela@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL 00/34] migration thread and queue
Date: Fri, 21 Dec 2012 02:39:54 +0100 [thread overview]
Message-ID: <87d2y4qj2t.fsf@elfo.mitica> (raw)
In-Reply-To: <87ehikmeqj.fsf@codemonkey.ws> (Anthony Liguori's message of "Thu, 20 Dec 2012 18:27:16 -0600")
Anthony Liguori <anthony@codemonkey.ws> wrote:
> Juan Quintela <quintela@redhat.com> writes:
>
>> Hi
>>
>> Changes for yesterday:
>> - Paolo Acked the series
>> - Rebaso on top of today git (only conflicts were due to header re-shuffle)
>>
>> Please pull.
>>
>> [20121219]
>>
>> This is my queue for migration-thread and patches associated. This
>> integrates review comments & code for Paolo. This is the subset from
>> both approachs that we agreed with. rest of patches need more review
>> and are not here.
>
> This breaks migration. Here's my test case:
>
> #!/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.
>
> I can't bisect tonight but can attempt to tomorrow. How has this been
> tested?
I have tested with tcp, load/not-load with guests form 4GB to 16GB RAM.
Will test tomorrow with your test case. I didn't tested exec:, though.
>
> 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?
Will re-test tomorrow with autotest.
Sorry, Juan.
next prev parent reply other threads:[~2012-12-21 1:40 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 [this message]
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
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=87d2y4qj2t.fsf@elfo.mitica \
--to=quintela@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
/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.