qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Priebe <s.priebe@profihost.ag>
To: Paolo Bonzini <pbonzini@redhat.com>
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: Fri, 28 Dec 2012 20:03:56 +0100	[thread overview]
Message-ID: <50DDED1C.2020208@profihost.ag> (raw)
In-Reply-To: <50DDDCB2.1060403@redhat.com>

Hi Paolo,

Am 28.12.2012 18:53, schrieb Paolo Bonzini:
> Il 28/12/2012 08:05, Alexandre DERUMIER ha scritto:
>> Hi list,
>> After discuss with Stefan Yesterday here some more info:
>>
>> (this is for stable qemu 1.3, it was working fine with qemu 1.2)
>>
>> The problem seem that whesettings a migrate_set_downtime to 1sec,
>>
>> the transfert of the vm seem to send all the memory of the vm in 1 step, and not by increment.
>> So the downtime is really huge , 90000ms for 1GB memory.
>
> Can you try commit bde54c08b4854aceee3dee25121a2b835cb81166?

i cherry picked that one on top of 1.3 sadly it does not help. VM halts, 
monitor socket is no longer available kvm process is running with 100% 
CPU on source side.

Greets,
Stefan

  reply	other threads:[~2012-12-28 19:04 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 [this message]
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
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=50DDED1C.2020208@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=aderumier@odiso.com \
    --cc=pbonzini@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 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).