From: Daniel Bareiro <daniel-listas@gmx.net>
To: KVM General <kvm@vger.kernel.org>
Subject: VM terminates when doing a live migration
Date: Sat, 21 May 2011 22:21:03 -0300 [thread overview]
Message-ID: <20110522012103.GB2699@defiant.freesoftware> (raw)
Hi all!
I'm doing some testing with KVM Live Migration. SS01 (VMHost) has Debian
GNU/Linux 6.0.1 and Defiant (VMHost) has Debian GNU/Linux 5.0.8. Defiant
has Linux 2.6.32-15~bpo50+1 and 0.12.5+dfsg-3~bpo50+2, and SS01 has
Linux 2.6.32-31 and 0.12.5+dfsg-5+squeeze1. Both instalation are 32-bit,
but the kernel in SS01 is amd64 and the kernel in Defiant is 686.
Migration from Defiant to SS01 is completed successfully, but when
trying to migrate a VM from SS01 to Defiant, the VM terminates
(segfault?). This is due to the difference in the kernel of each VMHost?
Thanks in advance for your replies.
Regards,
Daniel
[1] http://www.linux-kvm.org/page/Migration
--
Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37
Powered by Debian GNU/Linux Lenny - Linux user #188.598
next reply other threads:[~2011-05-22 1:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-22 1:21 Daniel Bareiro [this message]
2011-05-22 3:39 ` VM terminates when doing a live migration Michael Stroucken
2011-05-22 6:41 ` Daniel Bareiro
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=20110522012103.GB2699@defiant.freesoftware \
--to=daniel-listas@gmx.net \
--cc=dbareiro@gmx.net \
--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