From: Ben Guthro <bguthro@virtualiron.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Live Migration problems using xenapi with xm
Date: Wed, 07 Nov 2007 10:53:33 -0500 [thread overview]
Message-ID: <4731DF7D.8000709@virtualiron.com> (raw)
I am seeing a problem when live migrating a guest under unstable when I
have xm configured to XenAPI.
If my xm-config.xml file has the XenAPI stuff commented out - live
migrate (xm migrate --live <domid> <dest IP>) seems to be working in my
test environment.
However, if I enable it - I get failures when migrating the same guest
(see dump from xend.log below.) They obviously go down quite different
code paths in these two cases.
Being somewhat new to the xm, and xenapi control stacks - I was hoping
someone might point me in the right direction to track down what might
be happening here...
Any help is appreciated.
Ben
Xend log snippet:
2007-11-07 09:01:35 15422] DEBUG (XendCheckpoint:88) [xc_save]:
/usr/lib64/xen/bin/xc_save 20 2 0 0 5
[2007-11-07 09:01:35 15422] INFO (XendCheckpoint:362) Saving memory
pages: iter 1 0%ERROR Internal error: Error when writing to state file
(5) (errno 104)
[2007-11-07 09:01:35 15422] INFO (XendCheckpoint:362) Save exit rc=1
[2007-11-07 09:01:36 15422] ERROR (XendCheckpoint:140) Save failed on
domain VS022 (2).
Traceback (most recent call last):
File "/usr/lib64/python/xen/xend/XendCheckpoint.py", line 108, in save
forkHelper(cmd, fd, saveInputHandler, False)
File "/usr/lib64/python/xen/xend/XendCheckpoint.py", line 350, in
forkHelper
raise XendError("%s failed" % string.join(cmd))
XendError: /usr/lib64/xen/bin/xc_save 20 2 0 0 5 failed
[2007-11-07 09:01:36 15422] DEBUG (XendDomainInfo:1856)
XendDomainInfo.resumeDomain(2)
[2007-11-07 09:01:36 15422] ERROR (xmlrpclib2:166) Internal error
handling VM.migrate
Traceback (most recent call last):
File "/usr/lib64/python/xen/util/xmlrpclib2.py", line 131, in
_marshaled_dispatch
response = self._dispatch(method, params)
File "/usr/lib64/python2.4/SimpleXMLRPCServer.py", line 406, in _dispatch
return func(*params)
File "/usr/lib64/python/xen/xend/XendAPI.py", line 221, in f
return func(self, *args, **kwargs)
File "/usr/lib64/python/xen/xend/XendAPI.py", line 256, in check_session
return func(self, session, *args, **kwargs)
File "/usr/lib64/python/xen/xend/XendAPI.py", line 312, in <lambda>
'VM', func, *args, **kwargs)
File "/usr/lib64/python/xen/xend/XendAPI.py", line 268, in _check_ref
return func(api, session, ref, *args, **kwargs)
File "/usr/lib64/python/xen/xend/XendAPI.py", line 1763, in VM_migrate
bool(live), resource, port)
File "/usr/lib64/python/xen/xend/XendDomain.py", line 1282, in
domain_migrate
XendCheckpoint.save(sock.fileno(), dominfo, True, live, dst)
File "/usr/lib64/python/xen/xend/XendCheckpoint.py", line 142, in save
dominfo.resumeDomain()
File "/usr/lib64/python/xen/xend/XendDomainInfo.py", line 1885, in
resumeDomain
if self.is_hvm():
File "/usr/lib64/python/xen/xend/XendDomainInfo.py", line 2139, in
__getattr__
raise AttributeError()
AttributeError
next reply other threads:[~2007-11-07 15:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 15:53 Ben Guthro [this message]
2007-11-08 14:32 ` Live Migration problems using xenapi with xm Ben Guthro
2007-11-08 16:22 ` Ian Jackson
2007-11-08 16:36 ` Ben Guthro
2007-11-08 18:02 ` Jim Fehlig
2007-11-08 18:09 ` Ian Jackson
2007-11-08 20:18 ` Ben Guthro
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=4731DF7D.8000709@virtualiron.com \
--to=bguthro@virtualiron.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 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.