From: "Martinx - ジェームズ" <thiagocmartinsc@gmail.com>
To: Marco Sinhoreli <msinhore@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:40:18 -0300 [thread overview]
Message-ID: <6b7f6eb1003151340p1087a3d8l88de3e5de14e1c2b@mail.gmail.com> (raw)
In-Reply-To: <20fe3cf61003151333j7ccf3c07t33bc69daef571eff@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 8067 bytes --]
Of course! In fact, you can migrate ANY Linux from <-> to whatever you want.
On 15 March 2010 17:33, Marco Sinhoreli <msinhore@gmail.com> wrote:
> Other doubt: Could I migrate a KVM VM to XCP?
>
>
> On Mon, Mar 15, 2010 at 5:30 PM, Marco Sinhoreli <msinhore@gmail.com>wrote:
>
>> Hi David,
>>
>> Could I migrate a Citrix XenServer VM to XCP as well?
>>
>> Cheers,
>>
>>
>> 2010/3/15 David Markey <admin@dmarkey.com>
>>
>>> No im afraid not.
>>>
>>> YOU have to make these changes to menu.lst and fstab before migration.
>>>
>>> If your VMs are the exact same, this should be easily scripted. i.e.
>>>
>>> vmdisk="/dev/xen/vm1root"
>>>
>>> mount $vmdisk /mnt/tmp
>>>
>>> sed -i.bak -e 's/xvda1/xvda/g' -e 's/xvda2/xvdb/g' /mnt/tmp/etc/fstab
>>> /mnt/tmp/etc/fstab
>>>
>>> umount /mnt/tmp
>>>
>>>
>>>
>>>
>>>
>>>
>>> 2010/3/15 Martinx - ジェームズ <thiagocmartinsc@gmail.com>
>>>
>>>> So, your script can make a new partition scheme and a new fstab for my
>>>> VMs before stream it to the XenServer?
>>>> Because I have more than 100 VMs to copy! :-/
>>>>
>>>>
>>>> 2010/3/15 David Markey <admin@dmarkey.com>
>>>>
>>>>> Wow, what a pain :)
>>>>>
>>>>>
>>>>>
>>>>> 2010/3/15 Martinx - ジェームズ <thiagocmartinsc@gmail.com>
>>>>>
>>>>>> Yeah! Sure!
>>>>>>
>>>>>> Today I'm doing this work manually... I mean, to copy a VM from open
>>>>>> source Xen to the XenServer I do:
>>>>>>
>>>>>> 1- stop the VM on my debian dom0;
>>>>>> 2- mount its root file system under /mnt/source;
>>>>>> 3- export it via NFS;
>>>>>> 4- At the XenServer, I boot the sysrescuecd (a live system);
>>>>>> 5- fdisk the /dev/sda;
>>>>>> 6- create the LVM volumes;
>>>>>> 7- mount /dev/vg01/root under /mnt/target;
>>>>>> 8- mount /dev/sda1 under /mnt/target/boot;
>>>>>> 9- mount the debian dom0 nfs server under /mnt/source;
>>>>>> 10- cp /mnt/source/* /mnt/target/
>>>>>> 11- edit the /etc/fstab and the grub's menu;
>>>>>> 12- shutdown the VM;
>>>>>> 13- Convert it from HVM to PVM;
>>>>>> 14- start the VM;
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>> Thiago
>>>>>>
>>>>>> 2010/3/15 David Markey <admin@dmarkey.com>
>>>>>>
>>>>>>> If you change xvda1 to xvda, change xvda2 to xvdb it will work fine.
>>>>>>>
>>>>>>> Change references in /boot/grub/menu.lst of xvda1 to xvda
>>>>>>>
>>>>>>> Change references in /etc/fstab of xvda1 to xvda, and xvda2 to xvdb.
>>>>>>>
>>>>>>>
>>>>>>> Understand?
>>>>>>>
>>>>>>>
>>>>>>> 2010/3/15 Martinx - ジェームズ <thiagocmartinsc@gmail.com>
>>>>>>>
>>>>>>>> Exactly!
>>>>>>>>
>>>>>>>> The first one is for my domU hosted at my open source Xen (powered
>>>>>>>> by Debian), the second fstab, is the new one, used for my guests hosted at
>>>>>>>> my XenServers.
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks!
>>>>>>>> Thiago
>>>>>>>>
>>>>>>>> 2010/3/15 David Markey <admin@dmarkey.com>
>>>>>>>>
>>>>>>>>> I'm confused,
>>>>>>>>>
>>>>>>>>> You supply 2 fstabs there, one using LVM, one without. Which one is
>>>>>>>>> it?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2010/3/15 Martinx - ジェームズ <thiagocmartinsc@gmail.com>
>>>>>>>>>
>>>>>>>>> Hi David!
>>>>>>>>>>
>>>>>>>>>> My Xen domU in my open source dom0 (Debian) have this
>>>>>>>>>> configuration file:
>>>>>>>>>>
>>>>>>>>>> ----
>>>>>>>>>> bootloader = '/usr/bin/pygrub'
>>>>>>>>>> extra = 'console=hvc0'
>>>>>>>>>> memory = '64'
>>>>>>>>>> disk = [
>>>>>>>>>> 'phy:/dev/HyperVG01/guest01-root,xvda1,w',
>>>>>>>>>> 'phy:/dev/HyperVG01/guest01-swap,xvda2,w',
>>>>>>>>>> ]
>>>>>>>>>> name = 'guest01'
>>>>>>>>>> vif = [ 'mac=00:01:64:4b:0d:2e, vifname=guest01-eth0,
>>>>>>>>>> bridge=eth0' ]
>>>>>>>>>> on_poweroff = 'destroy'
>>>>>>>>>> on_reboot = 'restart'
>>>>>>>>>> on_crash = 'restart'
>>>>>>>>>> ----
>>>>>>>>>>
>>>>>>>>>> My guest01 /etc/fstab file:
>>>>>>>>>>
>>>>>>>>>> proc /proc proc defaults 0 0
>>>>>>>>>> /dev/xvda1 / ext3 relatime,errors=remount-ro
>>>>>>>>>> 0 1
>>>>>>>>>> /dev/xvda2 none swap sw 0 0
>>>>>>>>>>
>>>>>>>>>> BUT, this is for open source Xen domU, within the XenServer, the
>>>>>>>>>> guest01 should be:
>>>>>>>>>>
>>>>>>>>>> proc /proc proc defaults 0 0
>>>>>>>>>> /dev/xvda1 /boot ext2 defaults 0 2
>>>>>>>>>> /dev/mapper/vdwuaf1-root / ext3 errors=remount-ro
>>>>>>>>>> 0 1
>>>>>>>>>> /dev/mapper/vdwuaf1-swap_1 none swap sw
>>>>>>>>>> 0 0
>>>>>>>>>>
>>>>>>>>>> And the partition table of the guest01:
>>>>>>>>>>
>>>>>>>>>> guest01:~# fdisk -lu /dev/xvda
>>>>>>>>>>
>>>>>>>>>> Disk /dev/xvda: 8589 MB, 8589934592 bytes
>>>>>>>>>> 255 heads, 63 sectors/track, 1044 cylinders, total 16777216
>>>>>>>>>> sectors
>>>>>>>>>> Units = sectors of 1 * 512 = 512 bytes
>>>>>>>>>> Disk identifier: 0x0009c181
>>>>>>>>>>
>>>>>>>>>> Device Boot Start End Blocks Id System
>>>>>>>>>> /dev/xvda1 * 63 498014 248976 83 Linux
>>>>>>>>>> /dev/xvda2 498015 16771859 8136922+ 8e Linux LVM
>>>>>>>>>>
>>>>>>>>>> You tool can recreate the partition scheme? Or it just copy the
>>>>>>>>>> domU as is?
>>>>>>>>>> I have many others domU like this to copy...
>>>>>>>>>>
>>>>>>>>>> Thanks!
>>>>>>>>>> Thiago
>>>>>>>>>>
>>>>>>>>>> 2010/3/15 David Markey <admin@dmarkey.com>
>>>>>>>>>>
>>>>>>>>>> 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
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
>>>
>>>
>>
>>
>> --
>> Marco Sinhoreli
>>
>
>
>
> --
> Marco Sinhoreli
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
[-- Attachment #1.2: Type: text/html, Size: 13658 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 20:40 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
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 ` Martinx - ジェームズ [this message]
2010-03-15 20:36 ` Re: [Xen-users] " 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=6b7f6eb1003151340p1087a3d8l88de3e5de14e1c2b@mail.gmail.com \
--to=thiagocmartinsc@gmail.com \
--cc=david.markey@citrix.com \
--cc=msinhore@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).