From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Alexandre DERUMIER <aderumier@odiso.com>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] setting migrate_downtime results in halted vm (qemu 1.3)
Date: Sat, 29 Dec 2012 16:25:08 +0100 [thread overview]
Message-ID: <50DF0B54.5020102@redhat.com> (raw)
In-Reply-To: <50DF09E5.7040309@profihost.ag>
Il 29/12/2012 16:19, Stefan Priebe ha scritto:
>>
>>
>> I suppose it will be between 05e72dc5812a9f461fc2c606dff2572909eafc39
>> and aa723c23147e93fef8475bd80fd29e633378c34d.
>>
>> Probably at 2dddf6f4133975af62e64cb6406ec1239491fa89, which was supposed
>> to be placed before switching to the migration thread (or even squashed
>> in it) but ended up much earlier when the project moved from me to Juan.
>
> You mean by bisecting between qemu 1.2 and 1.3? I retested qemu 1.2 and
> it wasn't 100% working for me there too. It worked fine until
> migrate_downtime 1s it breaks / vm just halts when i set it to 2s with
> qemu 1.2. So i don't really know where to start bisecting. As i have NO
> version where it worked perfectly. Except Qemu 1.3 with the patches
> backported from 1.4 this works fine.
Bisect between the two commits I gave above. There probably will a
place when it starts failing reliably.
Paolo
next prev parent reply other threads:[~2012-12-29 15:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 21:54 [Qemu-devel] setting migrate_downtime results in halted vm Stefan Priebe
2012-12-28 7:05 ` [Qemu-devel] setting migrate_downtime results in halted vm (qemu 1.3) Alexandre DERUMIER
2012-12-28 17:53 ` Paolo Bonzini
2012-12-28 19:03 ` Stefan Priebe
2012-12-29 14:00 ` Paolo Bonzini
2012-12-29 14:05 ` Stefan Priebe
2012-12-29 14:58 ` Paolo Bonzini
2012-12-29 15:19 ` Stefan Priebe
2012-12-29 15:25 ` Paolo Bonzini [this message]
2012-12-31 13:25 ` Stefan Priebe
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=50DF0B54.5020102@redhat.com \
--to=pbonzini@redhat.com \
--cc=aderumier@odiso.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=s.priebe@profihost.ag \
/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).