From: Ben Guthro <bguthro@virtualiron.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Jim Fehlig <jfehlig@novell.com>,
xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Re: Live Migration problems using xenapi with xm
Date: Thu, 08 Nov 2007 15:18:18 -0500 [thread overview]
Message-ID: <47336F0A.4070204@virtualiron.com> (raw)
In-Reply-To: <18227.20703.408652.301529@mariner.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 1357 bytes --]
I think I have hacked together something that seems to work...
HVM Live migration seems to succeed if I do the following:
a.) Ignore the fact that receive thinks it is a PV guest (force is_hvm
to return True)
b.) Modify XendDomainInfo.waitForDevices to ignore "vkbd" and "vfb"
devices for HVM guests
We don't really do much PV guest stuff here, so I'm not real sure what
the vfb, and vkbd are in the PV world...
However, I'm not sure that they are necessary in HVM (though please
correct me if I'm wrong)
I'd like to come up with a patch for this, but would like to hear
thoughts on what the right way to go about this is.
Should I ignore those devices in waitForDevices?
Should they not be there in the first place?
Ian Jackson wrote:
> Jim Fehlig writes ("Re: [Xen-devel] Re: Live Migration problems using xenapi with xm"):
>
>> I would suspect you are in uncharted territory. Currently I don't think
>> there are a lot of xenapi users. In the past I have generally had to
>> fix bugs or provide implementation for xenapi features previously not
>> consumed by my app. You are perhaps the first to attempt migration
>> (almost certainly of HVM guests) through xenapi.
>>
>
> Jim may well be right, I'm afraid. I've only just arrived so to speak
> but I think the implementation in xend certainly needs work.
>
> Thanks,
> Ian.
>
[-- Attachment #1.2: Type: text/html, Size: 1815 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2007-11-08 20:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 15:53 Live Migration problems using xenapi with xm Ben Guthro
2007-11-08 14:32 ` 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 [this message]
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=47336F0A.4070204@virtualiron.com \
--to=bguthro@virtualiron.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=jfehlig@novell.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.