From: Wen Congyang <wency@cn.fujitsu.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen devel <xen-devel@lists.xen.org>
Subject: question about migration
Date: Thu, 24 Dec 2015 10:29:52 +0800 [thread overview]
Message-ID: <567B58A0.7010201@cn.fujitsu.com> (raw)
Hi Andrew Cooper:
I rebase the COLO codes to the newest upstream xen, and test it. I found
a problem in the test, and I can reproduce this problem via the migration.
How to reproduce:
1. xl cr -p hvm_nopv
2. xl migrate hvm_nopv 192.168.3.1
The migration successes, but the vm doesn't run in the target machine.
You can get the reason from 'xl dmesg':
(XEN) HVM2 restore: VMCE_VCPU 1
(XEN) HVM2 restore: TSC_ADJUST 0
(XEN) HVM2 restore: TSC_ADJUST 1
(d2) HVM Loader
(d2) Detected Xen v4.7-unstable
(d2) Get guest memory maps[128] failed. (-38)
(d2) *** HVMLoader bug at e820.c:39
(d2) *** HVMLoader crashed.
The reason is that:
We don't call xc_domain_set_memory_map() in the target machine.
When we create a hvm domain:
libxl__domain_build()
libxl__build_hvm()
libxl__arch_domain_construct_memmap()
xc_domain_set_memory_map()
Should we migrate the guest memory from source machine to target machine?
Thanks
Wen Congyang
next reply other threads:[~2015-12-24 2:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 2:29 Wen Congyang [this message]
2015-12-24 12:36 ` question about migration Andrew Cooper
2015-12-25 0:55 ` Wen Congyang
2015-12-29 10:57 ` Andrew Cooper
2015-12-25 1:45 ` Wen Congyang
2015-12-25 3:06 ` Wen Congyang
2015-12-29 12:46 ` Andrew Cooper
2016-01-04 15:31 ` Ian Jackson
2016-01-04 15:44 ` Ian Campbell
2016-01-04 15:48 ` Ian Campbell
2016-01-04 16:38 ` Andrew Cooper
2016-01-04 17:46 ` Ian Jackson
2016-01-04 18:05 ` Andrew Cooper
2016-01-05 15:40 ` Ian Jackson
2016-01-05 17:39 ` Andrew Cooper
2016-01-05 18:17 ` Ian Jackson
2016-01-06 10:21 ` Ian Campbell
2015-12-29 11:24 ` Andrew Cooper
2016-01-04 10:28 ` Paul Durrant
2016-01-04 10:36 ` Andrew Cooper
2016-01-04 11:08 ` Paul Durrant
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=567B58A0.7010201@cn.fujitsu.com \
--to=wency@cn.fujitsu.com \
--cc=andrew.cooper3@citrix.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.