From: David Markey <admin@dmarkey.com>
To: "Martinx - ジェームズ" <thiagocmartinsc@gmail.com>
Cc: David Markey <david.markey@citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"xen-users@lists.xensource.com" <xen-users@lists.xensource.com>
Subject: Re: Re: [Xen-users] XCP/XenServer Migration utility now available at xen.org
Date: Mon, 15 Mar 2010 17:43:44 +0000 [thread overview]
Message-ID: <6894a6471003151043o5ba7bf03kc8be41b7ae007626@mail.gmail.com> (raw)
In-Reply-To: <6b7f6eb1003121142x3f3ac6c7u6175c2ca3ddb283f@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1330 bytes --]
If anyone has feature requests, direct them here.
The next feature i'll be working on is supporting kernels loaded from the
Dom0. The kernel images will have to be copied to the XenServer/XCP Dom0.
2010/3/12 Martinx - ジェームズ <thiagocmartinsc@gmail.com>
> Really COOL!!! I'm doing all this work manually until now!
>
>
> On 12 March 2010 15:33, David Markey <david.markey@citrix.com> wrote:
>
>> Hi all,
>>
>> A new python based migration utility for migrating your xend virtual
>> machines to XCP is now available at:
>>
>> http://www.xen.org/products/cloud_projects.html
>>
>> It can generate XVAs from your xend based HVM and paravirtualised virtual
>> machines.
>> It can also steam your VM directly to a XenServer/XCP host over HTTP or
>> HTTPS.
>>
>> Please read the README for pointers and guidelines on how to prepare your
>> VMs for migration to XCP. Most PV based virtual machines will need some
>> preparation work.
>>
>>
>> Thanks to Stephen Spector and Dave Scott!
>>
>> Enjoy,
>>
>> David
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
>>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
[-- Attachment #1.2: Type: text/html, Size: 2340 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-03-15 17:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 18:33 XCP/XenServer Migration utility now available at xen.org David Markey
2010-03-12 19:42 ` [Xen-users] " Martinx - ジェームズ
2010-03-15 17:43 ` David Markey [this message]
2010-03-15 18:13 ` Martinx - ジェームズ
2010-03-15 18:17 ` [Xen-devel] " David Markey
2010-03-15 18:31 ` Re: [Xen-users] " Martinx - ジェームズ
2010-03-15 18:39 ` David Markey
2010-03-15 18:46 ` [Xen-devel] " Martinx - ジェームズ
2010-03-15 18:55 ` Re: [Xen-users] " David Markey
2010-03-15 20:14 ` Martinx - ジェームズ
2010-03-15 20:24 ` David Markey
2010-03-15 20:30 ` [Xen-devel] " Marco Sinhoreli
2010-03-15 20:33 ` Marco Sinhoreli
2010-03-15 20:38 ` David Markey
2010-03-15 20:40 ` Re: [Xen-users] " Martinx - ジェームズ
2010-03-15 20:36 ` David Markey
2010-03-15 18:41 ` [Xen-devel] " Martinx - ジェームズ
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=6894a6471003151043o5ba7bf03kc8be41b7ae007626@mail.gmail.com \
--to=admin@dmarkey.com \
--cc=david.markey@citrix.com \
--cc=thiagocmartinsc@gmail.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).