From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] memory allocation of migration changed?
Date: Tue, 11 Feb 2014 15:54:23 +0100 [thread overview]
Message-ID: <52FA399F.6070802@profihost.ag> (raw)
Hello,
in the past (Qemu 1.5) a migration failed if there was not enogh memory
on the target host available directly at the beginning.
Now with Qemu 1.7 i've seen succeeded migrations but the kernel OOM
memory killer killing qemu processes. So the migration seems to takes
place without having anough memory on the target machine?
Could this be?
Greets,
Stefan
next reply other threads:[~2014-02-11 14:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 14:54 Stefan Priebe - Profihost AG [this message]
2014-02-11 15:44 ` [Qemu-devel] memory allocation of migration changed? Stefan Hajnoczi
2014-02-11 16:22 ` Peter Lieven
2014-02-11 18:32 ` Stefan Priebe
2014-02-14 14:59 ` Stefan Hajnoczi
2014-02-14 18:15 ` Stefan Priebe
2014-02-11 18:30 ` Stefan Priebe
2014-02-14 15:03 ` Stefan Hajnoczi
2014-02-14 18:16 ` Stefan Priebe
2014-02-24 15:00 ` Stefan Hajnoczi
2014-02-24 16:13 ` Eric Blake
2014-03-12 19:15 ` 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=52FA399F.6070802@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).