WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Source code about live migration

To: Yangyang <yangyangbm@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Source code about live migration
From: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
Date: Fri, 3 Jun 2011 17:30:22 +0100
Cc:
Delivery-date: Fri, 03 Jun 2011 09:32:37 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=yJ6lhKWz07BGw6q9KIT1mOqjGE8+H2t51vIBUmKmlFY=; b=v+ulWvJwMpeixrN6RILUDgnenUU6Phl6eB86/S5S33AkSgTdVZLBAf+jlYus6ZQeWf qU9WRxq6VQ8AGpO7Uq5v5vKSqMJWsrZhpS4MqOO2Qcr+QMoWYXw84KZac9EWYZxJIuP2 c1TaT3opfu6Vk0hlL6E+2oV7EdxaZVWv05WyY=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=E6jC6ZOsithxGiar/XX7OpVP0oXQiZvVquOvlD36GhBLcOI7VbxKU0PIw8Da4ZZBxI ywbfrj9QD9WOzT4cGd5+CQ0bsW/It+KZPRffhdt00gi4uBmjlSZu7gi1BAzMVZlVFb1y P6f2UF02elp4C0LsAN5JjEP87YS+rSP7v+S1E=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BANLkTikhht7QNz6XkWwBjX=bPZ2dyDGVbw@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1307028844001-4448457.post@xxxxxxxxxxxxx> <BANLkTimOu=e23d1eHhn41jQnRPhc9qbQSg@xxxxxxxxxxxxxx> <BANLkTikhht7QNz6XkWwBjX=bPZ2dyDGVbw@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
There was some analysis of it done in this paper:

http://portal.acm.org/citation.cfm?id=1251223

A PDF can be found here:

http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.138.4067&rep=rep1&type=pdf

This paper was written several years ago, so it's probably worth
looking at again.

Peace,
 -George

On Fri, Jun 3, 2011 at 2:32 PM, Yangyang <yangyangbm@xxxxxxxxx> wrote:
> Thanks, George. That helps.
> I am trying the resource allocation of Xen on live migration. For example,
> the amount of CPU, bandwidth allocated to do the migration process.
> Have a good day.
>
> On Fri, Jun 3, 2011 at 6:26 AM, George Dunlap <dunlapg@xxxxxxxxx> wrote:
>>
>> The source code for live migration is in
>> xen.hg/tools/libxc/xc_domain_save.c and
>> xen.hg/tools/libxc/xc_domain_restore.c.
>>
>> I'm not sure what you mean by "check the resource allocation on it",
>> so I can't tell you if someone else has done it.
>>
>>  -George
>>
>> On Thu, Jun 2, 2011 at 4:34 PM, Yangyang <ywu009@xxxxxxx> wrote:
>> > Hi,All
>> > I'm trying to find out the xen source code responsible for live
>> > migration
>> > and check the resource allocation on it. Has anyone ever done this
>> > before
>> > and give me some hint?
>> >
>> > --
>> > View this message in context:
>> > http://xen.1045712.n5.nabble.com/Source-code-about-live-migration-tp4448457p4448457.html
>> > Sent from the Xen - Dev mailing list archive at Nabble.com.
>> >
>> > _______________________________________________
>> > Xen-devel mailing list
>> > Xen-devel@xxxxxxxxxxxxxxxxxxx
>> > http://lists.xensource.com/xen-devel
>> >
>
>
>
> --
> Regards.
> -Yangyang Wu
> CS PhD@FIU
> http://visa.cs.fiu.edu/~yangyang
>
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>