From: Stefan Priebe <s.priebe@profihost.ag>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] setting migrate_downtime results in halted vm
Date: Thu, 27 Dec 2012 22:54:55 +0100 [thread overview]
Message-ID: <50DCC3AF.7020802@profihost.ag> (raw)
Hello list,
i'm using qemu 1.3 and migration works fine if i do not set
migrate_downtime.
If i set migrate_downtime to 1s or 0.5s or 0.3s the VM halts immediatly
i cannot even connect to the qmp socket anymore and migration takes 5-10
minutes or never finishes.
I see high cpu usage on source vm while it hangs.
VM was for all tests IDLE and was using 1GB of 4GB mem.
Do you have any ideas what happens here?
Greets,
Stefan
next reply other threads:[~2012-12-27 21:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 21:54 Stefan Priebe [this message]
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
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=50DCC3AF.7020802@profihost.ag \
--to=s.priebe@profihost.ag \
--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 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).