From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 42600] New: Live migration of very large vm get's stuck
Date: Wed, 18 Jan 2012 14:53:43 GMT [thread overview]
Message-ID: <bug-42600-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=42600
Summary: Live migration of very large vm get's stuck
Product: Virtualization
Version: unspecified
Kernel Version: 2.6.32-131.6.1.el6.x86_64
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: kvm
AssignedTo: virtualization_kvm@kernel-bugs.osdl.org
ReportedBy: florian.rustedt@unitedexperts.de
Regression: No
We have several high load Tomcat servers virtualized on Scientific Linux via
KVM.
Configuration is between 10 and 30 GB of RAM and between 8 and 12 cores per VM.
What i can see so far is, that after round about 20% of migration the progress
get's slower and slower and finally the migration runs into a timeout,
sometimes also with a broken source vm, means stuck and needs to be rebootet :(
Both hypervisor servers are connected via 1 GB interface, so bandwidth should
be fine.
The Hypervisors are Intel modular server blades with 2x6cores and 96GB of RAM,
connected to a shared storage.
>From theory i would asume two possible explanations:
1. dirty RAM is changing too frequently and migration is transfering slower
than the changes are differing in size
2. Too much CPU's and therefore running threads break down migration
performance
If one of theese explanations is true, this is not a bug, but a problem ;)
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next reply other threads:[~2012-01-18 14:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 14:53 bugzilla-daemon [this message]
2012-08-30 13:50 ` [Bug 42600] Live migration of very large vm get's stuck bugzilla-daemon
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=bug-42600-28872@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.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