From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Yu-An(Victor) Chen" Subject: Re: Patching error while setting up COLO Date: Thu, 25 Feb 2016 19:38:32 -0800 Message-ID: References: <56CEC006.2050005@cn.fujitsu.com> <1456396297.6225.191.camel@citrix.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7264344451137287895==" Return-path: In-Reply-To: <1456396297.6225.191.camel@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: Ian Campbell Cc: Changlong Xie , Wen Congyang , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org --===============7264344451137287895== Content-Type: multipart/alternative; boundary=001a113ab5d2825508052ca40888 --001a113ab5d2825508052ca40888 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Changlong, Thanks for the reply! So I am trying to follow your new instructions, but when I am trying to do this: cd ~/colo-proxy/; git checkout 405527cbfa9f I got the following error: "error: pathspec '405527cbfa9f' did not match any file(s) known to git." I assume it is just a typo? Thank you! Victor On Thu, Feb 25, 2016 at 2:31 AM, Ian Campbell wrote: > On Thu, 2016-02-25 at 16:49 +0800, Changlong Xie wrote: > > Sorry for this. Since we have no privilege to update the Wiki for a lon= g > > time so most contents of this page are dated : ( > > Anyone can be granted access, it is only a manual process because of > spammers. Please create an account and then fill in the form at: > > https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__xenproject.org_comp= onent_content_article_100-2Dmisc_145-2Drequest-2Dto-2Dbe-2Dmade-2Da-2Dwiki-= 2Deditor.html&d=3DCwIFaQ&c=3DclK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r= =3DIitX1U91-NhsQt0q4MJOLQ&m=3DVnnj3Mx_nu951rfkiPcsuwuboBSLRcYYu30Uho1r7kw&s= =3D81rG3g_B23OhGxLWYNA7Hs6cFJy4VxE2Sdqhr0qe7Ds&e=3D > > > > > Anyway i'll write down detail steps here for colo on XEN. > > > > [Requirements] > > - Hardware > > There is at least one directly connected nic to forward the network > > requests from primary to secondary vm. The directly connected nic must > > not be used by any other purpose. If your guest has more than one nic, > > you should have directly connected nic for each guest nic. If you don't > > have enouth directly connected nic, you can use vlan. > > > > - Dom0 > > 1. Kernel with dom0 support > > 2. kernel module > > nf_conntrack > > nf_conntrack_ipv4 > > nf_nat > > libnl-tools >=3D 3.0. > > *Note*: If your host os has OEM-released xen tools, *MUST* uninstall it > > first. > > > > - Guest > > Only HVM guest(without pv extensions) is supported now. If you want to > > use OEM released guest os, please use SUSE=EF=BC=88we use "SUSE Linux > > Enterprise Server 11" currently=EF=BC=89. REDHAT and Ubuntu is not supp= orted > > now because I don't find any way to disable pv extensions. If you want > > to use REDHAT or Ubuntu, you need to build the newest kernel which has > > the parameter xen_nopv. > > > > > > [SETUP] > > - Network link topology > > ref: > https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__wiki.xenproject.org= _wiki_COLO-5F-2D-5FCoarse-5FGrain-5FLock-5FStepping&d=3DCwIFaQ&c=3DclK7kQUT= WtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=3DIitX1U91-NhsQt0q4MJOLQ&m=3DVnnj3Mx_= nu951rfkiPcsuwuboBSLRcYYu30Uho1r7kw&s=3D-vAQ55Sl3YGAa0EmRYKB2pvrRVa_D6nLQCN= iOGz7IeI&e=3D > > > > - Test environment prepare > > > > On both Primary/Secondary hosts: > > 1. > > cd ~ > > git clone > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__github.com_wencong= yang_colo-2Dproxy&d=3DCwIFaQ&c=3DclK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_g= I&r=3DIitX1U91-NhsQt0q4MJOLQ&m=3DVnnj3Mx_nu951rfkiPcsuwuboBSLRcYYu30Uho1r7k= w&s=3DuS-WmNmGEeeyytonbMxBCcbSHRzQJXUa6_pvkiGEPh4&e=3D > > git clone > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__github.com_macrosh= eep_iptables.git&d=3DCwIFaQ&c=3DclK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI= &r=3DIitX1U91-NhsQt0q4MJOLQ&m=3DVnnj3Mx_nu951rfkiPcsuwuboBSLRcYYu30Uho1r7kw= &s=3DZycjXRwwoyK_M8zU4CS8QsVaLWXzjx8mwtlEEIRlY_I&e=3D > > git clone > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__github.com_torvald= s_linux&d=3DCwIFaQ&c=3DclK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=3DIitX= 1U91-NhsQt0q4MJOLQ&m=3DVnnj3Mx_nu951rfkiPcsuwuboBSLRcYYu30Uho1r7kw&s=3DTeB7= X5i8Ua7jemThOaxH4oNER5ZMCcs1dyqUxZVIWPY&e=3D > > git clone > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__github.com_wencong= yang_qemu-2Dcolo&d=3DCwIFaQ&c=3DclK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI= &r=3DIitX1U91-NhsQt0q4MJOLQ&m=3DVnnj3Mx_nu951rfkiPcsuwuboBSLRcYYu30Uho1r7kw= &s=3D2kSeFd9-e3hISEJ1QZB1uzfVs8TxQwFQ_Rt4EuySfu8&e=3D > > git clone > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__github.com_wencong= yang_xen&d=3DCwIFaQ&c=3DclK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=3DIit= X1U91-NhsQt0q4MJOLQ&m=3DVnnj3Mx_nu951rfkiPcsuwuboBSLRcYYu30Uho1r7kw&s=3DztS= kYn_Z-t4_vnCdkHl09RzW8LaD9nnkeebyhac3a_0&e=3D > > > > 2. Prepare host kernel for Dom0 > > colo-proxy kernel module need cooperate with linux kernel. You should > > patch kernel with ~/colo-proxy/colo-patch-for-kernel.patch > > 1) cd ~/colo-proxy/; git checkout 405527cbfa9f > > 2) cd ~/linux/; git checkout v4.0; git am > > ~/colo-proxy/colo-patch-for-kernel.patch > > 3) cp /boot/config-3.0.76-0.11-xen .config; make menuconfig to config > > your kernel support Dom0. > > Ref: > https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__wiki.xenproject.org= _wiki_Mainline-5FLinux-5FKernel-5FConfigs&d=3DCwIFaQ&c=3DclK7kQUTWtAVEOVIgv= i0NU5BOUHhpN0H8p7CSfnc_gI&r=3DIitX1U91-NhsQt0q4MJOLQ&m=3DVnnj3Mx_nu951rfkiP= csuwuboBSLRcYYu30Uho1r7kw&s=3D3A6be8ZmUe1yTPFuGHZp3fD_LAtyo_5MW2jdVrBSDcs&e= =3D > > 4) make -j8; make modules_install; make install > > 5) reboot > > > > 3. build colo-proxy > > 1) cd ~/colo-proxy/; git checkout 405527cbfa9f; make; make install > > > > 4. build iptables > > 1) cd iptables; ./autogen.sh; ./configure --prefix=3D/usr/ > > --libdir=3D/usr/lib64; make; make install > > > > 5. build qemu-colo > > 1) cd ~/qemu-colo/; git checkout colo-xen-v2 > > 2) > > path_to_xen_source=3D~/xen > > ./configure --enable-xen --target-list=3Dx86_64-softmmu \ > > --extra-cflags=3D"-I$path_to_xen_source/tools/include > > -I$path_to_xen_source/tools/libxc -I$path_to_xen_source/tools/xenstore"= \ > > --extra-ldflags=3D"-L$path_to_xen_source/tools/libxc > > -L$path_to_xen_source/tools/xenstore" > > make -j4 > > > > 6. build xen > > 1) cd ~/xen/; git checkout colo_v10 > > 2) > > ./autogen.sh > > ./configure --enable-debug > > touch tools/libxl/libxlu_disk_l.l > > touch tools/libxl/libxlu_cfg_l.l > > make dist-xen -j8 > > make dist-tools -j8 > > make install-xen -j8 > > make install-tools -j8 > > > > 7. configure /boot/grub/menu.list to support xen, then reboot > > > > [ Run COLO ] > > > > 1. > > on primary: > > rm -f /var/log/xen/* > > rm -f /var/lib/xen/userdata-d.* > > service xencommons start > > modprobe nf_conntrack_ipv4 > > modprobe xt_PMYCOLO sec_dev=3Deth1 > > > > on secondary: > > rm -f /var/log/xen/* > > rm -f /var/lib/xen/userdata-d.* > > service xencommons start > > modprobe xt_SECCOLO > > active_disk=3D/mnt/ramfs/active_disk.img > > hidden_disk=3D/mnt/ramfs/hidden_disk.img > > local_img=3D/root/xie/suse-64hvm.img > > tmp_disk_size=3D`./qemu-colo/qemu-img info $local_img |grep 'virtual si= ze' > > > awk '{print $3}'` > > rm -rf /mnt/ramfs/* > > umount /mnt/ramfs/ > > rm -rf /mnt/ramfs/ > > mkdir /mnt/ramfs > > function create_image() > > { > > /root/xie/xen/tools/qemu-xen-dir/qemu-img create -f qcow2 $1 > > $tmp_disk_size > > } > > function prepare_temp_images() > > { > > grep -q "^none /mnt/ramfs ramfs" /proc/mounts > > if [[ $? -ne 0 ]]; then > > mount -t ramfs none /mnt/ramfs/ -o size=3D2G > > fi > > > > if [[ ! -e $active_disk ]]; then > > create_image $active_disk > > fi > > > > if [[ ! -e $hidden_disk ]]; then > > create_image $hidden_disk > > fi > > } > > prepare_temp_images > > > > 2. on primary > > xl cr hvm_nopv_colo > > sleep 10 > > xl pause hvm_nopv_colo > > xl remus -c -u hvm_nopv_colo 192.168.3.2 > > > > hvm_nopv_colo attached. > > > > > > That's all, good luck ; ) > > > > Thanks > > -Xie > > > > > Victor > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Xen-devel mailing list > > > Xen-devel@lists.xen.org > > > > https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__lists.xen.org_xen-2= Ddevel&d=3DCwIFaQ&c=3DclK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=3DIitX1= U91-NhsQt0q4MJOLQ&m=3DVnnj3Mx_nu951rfkiPcsuwuboBSLRcYYu30Uho1r7kw&s=3Dpwe0F= v2-rSmRy2SSYtNS48UnU0Dh911PUXDso8uG0nU&e=3D > > > > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xen.org > > > https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__lists.xen.org_xen-2= Ddevel&d=3DCwIFaQ&c=3DclK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=3DIitX1= U91-NhsQt0q4MJOLQ&m=3DVnnj3Mx_nu951rfkiPcsuwuboBSLRcYYu30Uho1r7kw&s=3Dpwe0F= v2-rSmRy2SSYtNS48UnU0Dh911PUXDso8uG0nU&e=3D > --001a113ab5d2825508052ca40888 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Changlong,

Thanks for the reply!

So I am trying to follow your new instructions, but w= hen I am trying to do this:

=C2=A0cd ~/colo-proxy/; git checkout 405527cbfa9f

I got the following error:

"error: pathspec '405527cbfa9f' did not match any file(s) = known to git."

<= /span>
I assume it is just a typ= o? Thank you!

=
Victor

On Thu, Feb 25, 2016 at= 2:31 AM, Ian Campbell <ian.campbell@citrix.com> wrote= :
On Thu, 2016-02-25 at = 16:49 +0800, Changlong Xie wrote:
> Sorry for this. Since we have no privilege to update the Wiki for a lo= ng
> time so most contents of this page are dated : (

Anyone can be granted access, it is only a manual process because of=
spammers. Please create an account and then fill in the form at:
https://urldefense.proofpoin= t.com/v2/url?u=3Dhttp-3A__xenproject.org_component_content_article_100-2Dmi= sc_145-2Drequest-2Dto-2Dbe-2Dmade-2Da-2Dwiki-2Deditor.html&d=3DCwIFaQ&a= mp;c=3DclK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=3DIitX1U91-NhsQt0q= 4MJOLQ&m=3DVnnj3Mx_nu951rfkiPcsuwuboBSLRcYYu30Uho1r7kw&s=3D81rG3g_B= 23OhGxLWYNA7Hs6cFJy4VxE2Sdqhr0qe7Ds&e=3D

>
> Anyway i'll write down detail steps here for colo on XEN.
>
> [Requirements]
> - Hardware
> There is at least one directly connected nic to forward the network > requests from primary to secondary vm. The directly connected nic must=
> not be used by any other purpose. If your guest has more than one nic,=
> you should have directly connected nic for each guest nic. If you don&= #39;t
> have enouth directly connected nic, you can use vlan.
>
> - Dom0
> 1. Kernel with dom0 support
> 2. kernel module
> =C2=A0=C2=A0=C2=A0=C2=A0nf_conntrack
> =C2=A0=C2=A0=C2=A0=C2=A0nf_conntrack_ipv4
> =C2=A0=C2=A0=C2=A0=C2=A0nf_nat
> =C2=A0=C2=A0=C2=A0=C2=A0libnl-tools >=3D 3.0.
> *Note*: If your host os has OEM-released xen tools, *MUST* uninstall i= t
> first.
>
> - Guest
> Only HVM guest(without pv extensions) is supported now. If you want to=
> use OEM released guest os, please use SUSE=EF=BC=88we use "SUSE L= inux
> Enterprise Server 11" currently=EF=BC=89. REDHAT and Ubuntu is no= t supported
> now because I don't find any way to disable pv extensions. If you = want
> to use REDHAT or Ubuntu, you need to build the newest kernel which has=
> the parameter xen_nopv.
>
>
> [SETUP]
> - Network link topology
> ref: https://urldefense.proofpoint.com/v2/url?= u=3Dhttp-3A__wiki.xenproject.org_wiki_COLO-5F-2D-5FCoarse-5FGrain-5FLock-5F= Stepping&d=3DCwIFaQ&c=3DclK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI= &r=3DIitX1U91-NhsQt0q4MJOLQ&m=3DVnnj3Mx_nu951rfkiPcsuwuboBSLRcYYu30= Uho1r7kw&s=3D-vAQ55Sl3YGAa0EmRYKB2pvrRVa_D6nLQCNiOGz7IeI&e=3D >
> -=C2=A0=C2=A0Test environment prepare
>
> On both Primary/Secondary hosts:
> 1.
> cd ~
> git clone ht= tps://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__github.com_wencongyang= _colo-2Dproxy&d=3DCwIFaQ&c=3DclK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSf= nc_gI&r=3DIitX1U91-NhsQt0q4MJOLQ&m=3DVnnj3Mx_nu951rfkiPcsuwuboBSLRc= YYu30Uho1r7kw&s=3DuS-WmNmGEeeyytonbMxBCcbSHRzQJXUa6_pvkiGEPh4&e=3D<= /a>
> git clone https://ur= ldefense.proofpoint.com/v2/url?u=3Dhttps-3A__github.com_macrosheep_iptables= .git&d=3DCwIFaQ&c=3DclK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&= ;r=3DIitX1U91-NhsQt0q4MJOLQ&m=3DVnnj3Mx_nu951rfkiPcsuwuboBSLRcYYu30Uho1= r7kw&s=3DZycjXRwwoyK_M8zU4CS8QsVaLWXzjx8mwtlEEIRlY_I&e=3D
> git clone https://urldefense.= proofpoint.com/v2/url?u=3Dhttps-3A__github.com_torvalds_linux&d=3DCwIFa= Q&c=3DclK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=3DIitX1U91-NhsQ= t0q4MJOLQ&m=3DVnnj3Mx_nu951rfkiPcsuwuboBSLRcYYu30Uho1r7kw&s=3DTeB7X= 5i8Ua7jemThOaxH4oNER5ZMCcs1dyqUxZVIWPY&e=3D
> git clone https://ur= ldefense.proofpoint.com/v2/url?u=3Dhttps-3A__github.com_wencongyang_qemu-2D= colo&d=3DCwIFaQ&c=3DclK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&= ;r=3DIitX1U91-NhsQt0q4MJOLQ&m=3DVnnj3Mx_nu951rfkiPcsuwuboBSLRcYYu30Uho1= r7kw&s=3D2kSeFd9-e3hISEJ1QZB1uzfVs8TxQwFQ_Rt4EuySfu8&e=3D
> git clone https://urldefense= .proofpoint.com/v2/url?u=3Dhttps-3A__github.com_wencongyang_xen&d=3DCwI= FaQ&c=3DclK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=3DIitX1U91-Nh= sQt0q4MJOLQ&m=3DVnnj3Mx_nu951rfkiPcsuwuboBSLRcYYu30Uho1r7kw&s=3DztS= kYn_Z-t4_vnCdkHl09RzW8LaD9nnkeebyhac3a_0&e=3D
>
> 2. Prepare host kernel for Dom0
> colo-proxy kernel module need cooperate with linux kernel. You should<= br> > patch kernel with ~/colo-proxy/colo-patch-for-kernel.patch
> 1) cd ~/colo-proxy/; git checkout 405527cbfa9f
> 2) cd ~/linux/; git checkout v4.0; git am
> ~/colo-proxy/colo-patch-for-kernel.patch
> 3) cp /boot/config-3.0.76-0.11-xen=C2=A0=C2=A0.config; make menuconfig= to config
> your kernel support Dom0.
> Ref: https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__wi= ki.xenproject.org_wiki_Mainline-5FLinux-5FKernel-5FConfigs&d=3DCwIFaQ&a= mp;c=3DclK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=3DIitX1U91-NhsQt0q= 4MJOLQ&m=3DVnnj3Mx_nu951rfkiPcsuwuboBSLRcYYu30Uho1r7kw&s=3D3A6be8Zm= Ue1yTPFuGHZp3fD_LAtyo_5MW2jdVrBSDcs&e=3D
> 4) make -j8; make modules_install; make install=
> 5) reboot
>
> 3. build colo-proxy
> 1) cd ~/colo-proxy/; git checkout 405527cbfa9f; make; make install
>
> 4. build iptables
> 1) cd iptables; ./autogen.sh; ./configure --prefix=3D/usr/
> --libdir=3D/usr/lib64; make; make install
>
> 5. build qemu-colo
> 1) cd ~/qemu-colo/; git checkout colo-xen-v2
> 2)
> path_to_xen_source=3D~/xen
> ./configure --enable-xen --target-list=3Dx86_64-softmmu \
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0--extra-cflags=3D"-I$path_to_xen_source/tools/include
> -I$path_to_xen_source/tools/libxc -I$path_to_xen_source/tools/xenstore= " \
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0--extra-ldflags=3D"-L$path_to_xen_source/tools/libxc
> -L$path_to_xen_source/tools/xenstore"
> make -j4
>
> 6. build xen
> 1) cd ~/xen/; git checkout colo_v10
> 2)
> ./autogen.sh
> ./configure --enable-debug
> touch tools/libxl/libxlu_disk_l.l
> touch tools/libxl/libxlu_cfg_l.l
> make dist-xen -j8
> make dist-tools -j8
> make install-xen -j8
> make install-tools -j8
>
> 7. configure /boot/grub/menu.list to support xen, then reboot
>
> [ Run COLO ]
>
> 1.
> on primary:
> rm -f /var/log/xen/*
> rm -f /var/lib/xen/userdata-d.*
> service xencommons start
> modprobe nf_conntrack_ipv4
> modprobe xt_PMYCOLO sec_dev=3Deth1
>
> on secondary:
> rm -f /var/log/xen/*
> rm -f /var/lib/xen/userdata-d.*
> service xencommons start
> modprobe xt_SECCOLO
> active_disk=3D/mnt/ramfs/active_disk.img
> hidden_disk=3D/mnt/ramfs/hidden_disk.img
> local_img=3D/root/xie/suse-64hvm.img
> tmp_disk_size=3D`./qemu-colo/qemu-img info $local_img |grep 'virtu= al size'
> > awk=C2=A0=C2=A0'{print $3}'`
> rm -rf /mnt/ramfs/*
> umount /mnt/ramfs/
> rm -rf /mnt/ramfs/
> mkdir /mnt/ramfs
> function create_image()
> {
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0/root/xie/xen/tools/qemu-xen-dir/qemu-im= g create -f qcow2 $1
> $tmp_disk_size
> }
> function prepare_temp_images()
> {
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0grep -q "^none /mnt/ramfs ramfs&quo= t; /proc/mounts
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0if [[ $? -ne 0 ]]; then
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0mount -t ramfs n= one /mnt/ramfs/ -o size=3D2G
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0fi
>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0if [[ ! -e $active_disk ]]; then
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0create_image $ac= tive_disk
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0fi
>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0if [[ ! -e $hidden_disk ]]; then
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0create_image $hi= dden_disk
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0fi
> }
> prepare_temp_images
>
> 2. on primary
> xl cr hvm_nopv_colo
> sleep 10
> xl pause hvm_nopv_colo
> xl remus -c -u hvm_nopv_colo 192.168.3.2
>
> hvm_nopv_colo attached.
>
>
> That's all, good luck ; )
>
> Thanks
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0-Xie
>
> > Victor
> >
> >
> >
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xen.or= g
> > https://urlde= fense.proofpoint.com/v2/url?u=3Dhttp-3A__lists.xen.org_xen-2Ddevel&d=3D= CwIFaQ&c=3DclK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=3DIitX1U91= -NhsQt0q4MJOLQ&m=3DVnnj3Mx_nu951rfkiPcsuwuboBSLRcYYu30Uho1r7kw&s=3D= pwe0Fv2-rSmRy2SSYtNS48UnU0Dh911PUXDso8uG0nU&e=3D
> >
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org=
> https://urldefense.proo= fpoint.com/v2/url?u=3Dhttp-3A__lists.xen.org_xen-2Ddevel&d=3DCwIFaQ&= ;c=3DclK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=3DIitX1U91-NhsQt0q4M= JOLQ&m=3DVnnj3Mx_nu951rfkiPcsuwuboBSLRcYYu30Uho1r7kw&s=3Dpwe0Fv2-rS= mRy2SSYtNS48UnU0Dh911PUXDso8uG0nU&e=3D

--001a113ab5d2825508052ca40888-- --===============7264344451137287895== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9y Zy94ZW4tZGV2ZWwK --===============7264344451137287895==--