From: Muriel <mucawhite@gmail.com>
To: xen-devel@lists.xensource.com
Subject: VM hangs after live migration
Date: Wed, 12 Jan 2011 10:41:44 +0100 [thread overview]
Message-ID: <4D2D7758.8050203@gmail.com> (raw)
Hi all,
i'm not sure that this is the right place to write but i hope you can
help me.
I have many vm on Xenserver 5.5 and starting with kernel 2.6.32.15 i had
many problems with the live migration:
- with 2.6.32.16 and higher the vm hang after migration (no console output)
- 2.6.32.26 and higher have this kernel bug:
kernel BUG at /build/buildd/linux-2.6.32/arch/x86/xen/spinlock.c:343!
invalid opcode: 0000 [#1] SMP
After some research on the mailing list i tried to apply this patch:
http://xen.1045712.n5.nabble.com/PATCH-xen-events-do-not-unmask-polled-ipis-on-restore-td3241695.html
to the kernel 2.6.32.27 and now:
- when i try to migrate the vm from a member of the pool to another
everything works fine;
- when i try to migrate the vm from a member of the pool to the master
the vm hangs (exactly as the 2.6.32.16).
Any suggestions?
Muriel
next reply other threads:[~2011-01-12 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 9:41 Muriel [this message]
2011-01-12 10:20 ` VM hangs after live migration Ian Campbell
2011-01-12 13:58 ` Muriel
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=4D2D7758.8050203@gmail.com \
--to=mucawhite@gmail.com \
--cc=xen-devel@lists.xensource.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).