From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Yu-An(Victor) Chen" Subject: Re: Patching error while setting up COLO Date: Wed, 16 Mar 2016 12:45:21 -0700 Message-ID: References: <56CEC006.2050005@cn.fujitsu.com> <1456396297.6225.191.camel@citrix.com> <56CFD26C.3000104@cn.fujitsu.com> <56CFDDAF.8060200@cn.fujitsu.com> <56D8161E.7010707@cn.fujitsu.com> <56D8EFBB.10407@cn.fujitsu.com> <56DCD58A.4080004@cn.fujitsu.com> <56E67814.3090301@cn.fujitsu.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7845065390845721746==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: Changlong Xie Cc: Wen Congyang , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org --===============7845065390845721746== Content-Type: multipart/alternative; boundary=001a1149a5481f9b82052e2fc149 --001a1149a5481f9b82052e2fc149 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, I have a question about the network setup with COLO. so in the colo page( http://wiki.xenproject.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping) it shows a network topology graph: master: br0: 192.168.0.33 eth1: 192.168.1.33 eth2: 192.168.2.33 slave: br0: 192.168.0.88 br1: no ip address eth1: 192.168.1.88 eth2: 192.168.2.88 Just from the master and slave configuration the page provided. I cannot see how the two servers are going to communicate with each other if the bridge's ip is different from both eth1 and eth2. can anybody provide a hint how this works? Thank you! Victor On Tue, Mar 15, 2016 at 11:06 PM, Yu-An(Victor) Chen wrote: > Hi Changlong, > > Thanks for the reply, the script works now. Now I have a question about > the network setup: according to the website > you > sent me, colo network interfaces between two servers should be set up lik= e > the following? is there any other detail regarding networking I might be > missing? Thank you! > > master: > br0: 192.168.0.33 > eth1: 192.168.1.33 > eth2: 192.168.2.33 > > slave: > br0: 192.168.0.88 > br1: no ip address > eth1: 192.168.1.88 > eth2: 192.168.2.88 > > > Victor > > On Mon, Mar 14, 2016 at 1:36 AM, Changlong Xie > wrote: > >> On 03/09/2016 06:57 AM, Yu-An(Victor) Chen wrote: >> >>> Sorry for the duplicated email Congyang, I forgot to replied all: >>> >>> Hi Congyang, >>> >>> Thank you for the hint, after building xen, your script works for >>> qemu-xen! >>> >>> so now I am trying to set up the secondary node with the script provide= d >>> by >>> Changlong in his first reply: >>> >>> -----------------------------------------------------------------------= ------------------------ >>> 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.imghidden_disk=3D/mnt/ramfs/hidde= n_disk.imglocal_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 >>> } >>> >>> -----------------------------------------------------------------------= ------------------------ >>> >>> I have question about for the codes below: >>> >>> >>> >>> >>> *active_disk=3D/mnt/ramfs/active_disk.imghidden_disk=3D/mnt/ramfs/hidde= n_disk.imglocal_img=3D/root/xie/suse-64hvm.img* >>> >>> Do I have to create my own image and put the img in that location? if s= o >>> what kind of img specifically? >>> >> >> The scripts will create "/mnt/ramfs/active_disk.img" and >> "/mnt/ramfs/hidden_disk.img" automaticly. You need create Domain U image= by >> yourself >> >> Thanks >> -Xie >> >> >>> because when I look into /mnt/ramfs, it is an empty directory. >>> >>> Thank you! >>> >>> On Sun, Mar 6, 2016 at 5:12 PM, Wen Congyang >>> wrote: >>> >>> On 03/05/2016 09:51 AM, Yu-An(Victor) Chen wrote: >>>> >>>>> Hi Congyang, >>>>> >>>>> Thanks for your reply, >>>>> >>>>> even with your script, and I modify the "path_to_xen_source" to point >>>>> >>>> where my xen directory is. I still got this error. >>>> >>>>> >>>>> ERROR: User requested feature xen >>>>> configure was not able to find it. >>>>> Install xen devel >>>>> >>>>> What do you think what I am missing? Thank you! >>>>> >>>> >>>> Do you build xen before? >>>> >>>> Thanks >>>> Wen Congyang >>>> >>>> >>>>> Victor >>>>> >>>>> >>>>> >>>>> On Thu, Mar 3, 2016 at 6:15 PM, Wen Congyang >>>> >>>> > wrote: >>>> >>>>> >>>>> On 03/04/2016 10:01 AM, Yu-An(Victor) Chen wrote: >>>>> > Hi, >>>>> > >>>>> > So I git clone >>>>> >>>> >>>> https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__github.com_wenc= ongyang_qemu-2Dxen.git&d=3DCwICaQ&c=3DclK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CS= fnc_gI&r=3DIitX1U91-NhsQt0q4MJOLQ&m=3D4j1T2HKL4uKodf62b4Tz1XtOvX81uAqCqfOcD= 90CRAY&s=3Ds0fo5ej8_vZ1PmOkDCuyIroS5Zi_KpDSHI8jqodSmrg&e=3D >>>> >>>>> > >>>>> > but i only see branch "con-xen-v2" instead of " colo-xen-v2" s= o >>>>> I >>>>> >>>> assume I use just use con-xen-v2. >>>> >>>>> > >>>>> > But then the following step: >>>>> > >>>>> > in both ~/qemu-colo and ~/qemu-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" >>>> >>>>> >>>>> >>>>> This command line is out of dated. The following is my building >>>>> >>>> scripts: >>>> >>>>> #! /bin/bash >>>>> >>>>> path_to_xen_source=3D/work/src/xen >>>>> #./configure --enable-xen --target-list=3Di386-softmmu \ >>>>> # --extra-cflags=3D"-I$path_to_xen_source/tools/inclu= de >>>>> >>>> -I$path_to_xen_source/tools/libxc/include >>>> -I$path_to_xen_source/tools/xenstore/include" \ >>>> >>>>> # --extra-ldflags=3D"-L$path_to_xen_source/tools/libx= c >>>>> >>>> -L$path_to_xen_source/tools/xenstore" >>>> >>>>> >>>>> extra_cflags=3D"" >>>>> extra_cflags+=3D" -DXC_WANT_COMPAT_EVTCHN_API=3D1" >>>>> extra_cflags+=3D" -DXC_WANT_COMPAT_GNTTAB_API=3D1" >>>>> extra_cflags+=3D" -DXC_WANT_COMPAT_MAP_FOREIGN_API=3D1" >>>>> extra_cflags+=3D" -I$path_to_xen_source/tools/include" >>>>> extra_cflags+=3D" -I$path_to_xen_source/tools/libs/toollog/inclu= de" >>>>> extra_cflags+=3D" -I$path_to_xen_source/tools/libs/evtchn/includ= e" >>>>> extra_cflags+=3D" -I$path_to_xen_source/tools/libs/gnttab/includ= e" >>>>> extra_cflags+=3D" >>>>> >>>> -I$path_to_xen_source/tools/libs/foreignmemory/include" >>>> >>>>> extra_cflags+=3D" -I$path_to_xen_source/tools/libxc/include" >>>>> extra_cflags+=3D" -I$path_to_xen_source/tools/xenstore/include" >>>>> extra_cflags+=3D" >>>>> -I$path_to_xen_source/tools/xenstore/compat/include" >>>>> extra_cflags+=3D" " >>>>> >>>>> extra_ldflags=3D"" >>>>> extra_ldflags+=3D" -L$path_to_xen_source/tools/libxc" >>>>> extra_ldflags+=3D" -L$path_to_xen_source/tools/xenstore" >>>>> extra_ldflags+=3D" -L$path_to_xen_source/tools/libs/evtchn" >>>>> extra_ldflags+=3D" -L$path_to_xen_source/tools/libs/gnttab" >>>>> extra_ldflags+=3D" -L$path_to_xen_source/tools/libs/foreignmemor= y" >>>>> extra_ldflags+=3D" >>>>> >>>> -Wl,-rpath-link=3D$path_to_xen_source/tools/libs/toollog" >>>> >>>>> extra_ldflags+=3D" >>>>> >>>> -Wl,-rpath-link=3D$path_to_xen_source/tools/libs/evtchn" >>>> >>>>> extra_ldflags+=3D" >>>>> >>>> -Wl,-rpath-link=3D$path_to_xen_source/tools/libs/gnttab" >>>> >>>>> extra_ldflags+=3D" >>>>> -Wl,-rpath-link=3D$path_to_xen_source/tools/libs/call" >>>>> extra_ldflags+=3D" >>>>> >>>> -Wl,-rpath-link=3D$path_to_xen_source/tools/libs/foreignmemory" >>>> >>>>> extra_ldflags+=3D" " >>>>> >>>>> ./configure --enable-xen --target-list=3Di386-softmmu \ >>>>> --extra-cflags=3D"$extra_cflags" \ >>>>> --extra-ldflags=3D"$extra_ldflags" >>>>> >>>>> if [[ $? -ne 0 ]]; then >>>>> exit 1 >>>>> fi >>>>> >>>>> #make -j8 && make clean >>>>> make -j8 >>>>> >>>>> You can find the newest building way in tools/Makefile(xen's >>>>> codes): >>>>> subdir-all-qemu-xen-dir: qemu-xen-dir-find >>>>> if test -d $(QEMU_UPSTREAM_LOC) ; then \ >>>>> source=3D$(QEMU_UPSTREAM_LOC); \ >>>>> else \ >>>>> source=3D.; \ >>>>> fi; \ >>>>> cd qemu-xen-dir; \ >>>>> if $$source/scripts/tracetool.py --check-backend --backe= nd >>>>> >>>> stderr ; then \ >>>> >>>>> >>>>> enable_trace_backend=3D'--enable-trace-backend=3Dstderr'; \ >>>> >>>>> else \ >>>>> enable_trace_backend=3D'' ; \ >>>>> fi ; \ >>>>> $$source/configure --enable-xen >>>>> --target-list=3Di386-softmmu \ >>>>> $(QEMU_XEN_ENABLE_DEBUG) \ >>>>> $$enable_trace_backend \ >>>>> --prefix=3D$(LIBEXEC) \ >>>>> --libdir=3D$(LIBEXEC_LIB) \ >>>>> --includedir=3D$(LIBEXEC_INC) \ >>>>> .... >>>>> >>>>> Thanks >>>>> Wen Congyang >>>>> >>>>> > >>>>> > >>>>> > I got the following error message: >>>>> > >>>>> > "ERROR: User requested feature xen >>>>> > configure was not able to find it. >>>>> > Install xen devel" >>>>> > >>>>> > I found out the the error came from just simply doing this: >>>>> > >>>>> > ./configure --enable-xen >>>>> > >>>>> > I am thinking the reason is because I did this step wrong: >>>>> > >>>>> > "path_to_xen_source=3D~/xen" >>>>> > >>>>> > Do I just simply copy and paste the above command into the >>>>> >>>> terminal and execute? >>>> >>>>> > >>>>> > Thank you! >>>>> > >>>>> > Victor >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > Thank you! >>>>> > >>>>> > On Thu, Mar 3, 2016 at 2:46 AM, Wen Congyang < >>>>> wency@cn.fujitsu.com >>>>> >>>> >>> wency@cn.fujitsu.com>>> wrote: >>>> >>>>> > >>>>> > On 03/03/2016 05:39 PM, Yu-An(Victor) Chen wrote: >>>>> > > Hi Changlong, >>>>> > > >>>>> > > Thanks for the reply, >>>>> > > >>>>> > > Again when I am trying to do the following: >>>>> > > >>>>> > > 5. build qemu-colo >>>>> > > 1) cd ~/qemu-colo/; *git checkout colo-xen-v2* >>>>> > > * >>>>> > > * >>>>> > > I got this error message *"error: pathspec 'colo-xen-v2' >>>>> did >>>>> >>>> not match any file(s) known to git."* Even if I do git fetch, I still >>>> get >>>> the same error. >>>> >>>>> > > >>>>> > > the qemu-colo I cloned from is provided by you >>>>> >>>> >>>> https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__github.com_wenc= ongyang_qemu-2Dcolo.git&d=3DCwICaQ&c=3DclK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7C= Sfnc_gI&r=3DIitX1U91-NhsQt0q4MJOLQ&m=3DMgaousw-OxgAf6f9NTOk2AidO8unmTx8nKwi= GLUCISU&s=3DTz2SiQ2gjQexttffgWiqgwj07qsfY4TpG4Hfcpo9Lco&e=3D >>>> >>>>> > >>>>> > >>>>> >>>> >>>> https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__github.com_wenc= ongyang_qemu-2Dxen&d=3DCwICaQ&c=3DclK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_= gI&r=3DIitX1U91-NhsQt0q4MJOLQ&m=3DMgaousw-OxgAf6f9NTOk2AidO8unmTx8nKwiGLUCI= SU&s=3Dz-KexB48-yzsD9EEJ5tC3p8tHRiRi7LoUiP-gF6kKX0&e=3D >>>> , not qemu-colo >>>> >>>>> > >>>>> > > >>>>> > > Thank you! >>>>> > > >>>>> > > Victor >>>>> > > >>>>> > > >>>>> > > >>>>> > > On Thu, Feb 25, 2016 at 9:07 PM, Changlong Xie < >>>>> >>>> xiecl.fnst@cn.fujitsu.com >>> xiecl.fnst@cn.fujitsu.com > >>> xiecl.fnst@cn.fujitsu.com >>> xiecl.fnst@cn.fujitsu.com >>> wrote: >>>> >>>>> > > >>>>> > > On 02/26/2016 12:55 PM, Yu-An(Victor) Chen wrote: >>>>> > > >>>>> > > Hi Changlong, >>>>> > > >>>>> > > Are you suggesting I should hold off on setting = up >>>>> >>>> COLO for now? >>>> >>>>> > > >>>>> > > >>>>> > > No, just following my steps. >>>>> > > >>>>> > > Thanks >>>>> > > -Xie >>>>> > > >>>>> > > >>>>> > > Thanks! >>>>> > > >>>>> > > Victor >>>>> > > >>>>> > > On Thu, Feb 25, 2016 at 8:19 PM, Changlong Xie < >>>>> >>>> xiecl.fnst@cn.fujitsu.com >>> xiecl.fnst@cn.fujitsu.com > >>> xiecl.fnst@cn.fujitsu.com >>> xiecl.fnst@cn.fujitsu.com >>> >>>> >>>>> > > wrote: >>>>> > > >>>>> > > On 02/26/2016 11:38 AM, Yu-An(Victor) Chen >>>>> wrote: >>>>> > > >>>>> > > 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! >>>>> > > >>>>> > > >>>>> > > Hi victor >>>>> > > >>>>> > > Please git clone >>>>> > > >>>>> >>>> >>>> https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__github.com_Pati= ng_colo-2Dproxy_tree_changlox&d=3DCwICaQ&c=3DclK7kQUTWtAVEOVIgvi0NU5BOUHhpN= 0H8p7CSfnc_gI&r=3DIitX1U91-NhsQt0q4MJOLQ&m=3DpCAkg_8tEQmGEZZoUlyePZjK7z-6aE= mp-n6UrQRLWo4&s=3DWw-EAIszC-zQuVcDc4XpigwVbMG_4t2SpTg2PV6HTjM&e=3D >>>> >>>>> > > *Notice* that, currently we implement colo >>>>> proxy >>>>> >>>> as a kernel module what >>>> >>>>> > > is a temporary measure. But further more we'= ll >>>>> >>>> intergrate it in qemu and >>>> >>>>> > > drop this one, so both qemu-colo and xen-col= o >>>>> >>>> will share the same proxy. >>>> >>>>> > > Please don't test this colo proxy now, there >>>>> >>>> maybe some bugs, but it's >>>> >>>>> > > acceptable. >>>>> > > >>>>> > > Thanks >>>>> > > -Xie >>>>> > > >>>>> > > >>>>> > > Victor >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> >>> >>> >>> >> >> > --001a1149a5481f9b82052e2fc149 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

I have a question about the network= setup with COLO.

so in the colo page(http= ://wiki.xenproject.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping)

it shows a network=C2=A0topology graph:
master: br0: 192.168.0.33 eth1: 192.168.1.33 eth2: 192.168.2.33 slave: br0: 192.168.0.88 br1: no ip address eth1: 192.168.1.88 eth2: 192.168.2.88

Just from the master and = slave configuration the page provided. I cannot see how the two servers are= going to communicate with each other if the bridge's ip is different f= rom both eth1 and eth2. can anybody provide a hint how this works? Thank yo= u!

Victor


On Tue, Mar 15, 2016 at 1= 1:06 PM, Yu-An(Victor) Chen <chen116@usc.edu> wrote:
Hi Changlong,

= Thanks for the reply, the script works now. Now I have a question about the= network setup: according to the website you sent = me, colo network interfaces between two servers should be set up like the f= ollowing? is there any other detail regarding networking I might be missing= ? Thank you!

master:
br0: 192.168.0.33
eth1: 192.168.1.33
eth2: 192.168.2.33

slave:
br0: 192.168.0.88
br1: no ip address
eth1: 192.168.1.88
eth2: 192.168.2.88

Victor

On Mon, Mar 14, 2016 at 1:36 AM, Changlong Xie <xiecl.fnst@cn.fu= jitsu.com> wrote:
On= 03/09/2016 06:57 AM, Yu-An(Victor) Chen wrote:
Sorry for the duplicated email Congyang, I forgot to replied all:

Hi Congyang,

Thank you for the hint, after building xen, your script works for qemu-xen!=

so now I am trying to set up the secondary node with the script provided by=
Changlong in his first reply:
---------------------------------------------------------------------------= --------------------
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.imghidden_disk=3D/mnt/ramfs/hidden_di= sk.imglocal_img=3D/root/xie/suse-64hvm.img*
tmp_disk_size=3D`./qemu-colo/qemu-img info $local_img |grep 'virtual si= ze'
|awk=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/root/xie/xen/tools/qemu-xen-dir/qemu-img create -f qco= w2 $1
$tmp_disk_size
}
function prepare_temp_images()
{
=C2=A0 =C2=A0 =C2=A0grep -q "^none /mnt/ramfs ramfs" /proc/mounts=
=C2=A0 =C2=A0 =C2=A0if [[ $? -ne 0 ]]; then
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0mount -t ramfs none /mnt/ramfs/ -o size= =3D2G
=C2=A0 =C2=A0 =C2=A0fi

=C2=A0 =C2=A0 =C2=A0if [[ ! -e $active_disk ]]; then
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0create_image $active_disk
=C2=A0 =C2=A0 =C2=A0fi

=C2=A0 =C2=A0 =C2=A0if [[ ! -e $hidden_disk ]]; then
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0create_image $hidden_disk
=C2=A0 =C2=A0 =C2=A0fi
}
---------------------------------------------------------------------------= --------------------

I have question about for the codes below:



 *active_disk=3D/mnt/ramfs/active_disk.imghidden_disk=3D/mnt/ramfs/hidden_di= sk.imglocal_img=3D/root/xie/suse-64hvm.img*

Do I have to create my own image and put the img in that location? if so what kind of img specifically?

The scripts will create "/mnt/ramfs/active_disk.img" and "/m= nt/ramfs/hidden_disk.img" automaticly. You need create Domain U image = by yourself

Thanks
=C2=A0 =C2=A0 =C2=A0 =C2=A0 -Xie


because when I look into /mnt/ramfs, it is an empty directory.

Thank you!

On Sun, Mar 6, 2016 at 5:12 PM, Wen Congyang <wency@cn.fujitsu.com> wrote:

On 03/05/2016 09:51 AM, Yu-An(Victor) Chen wrote:
Hi Congyang,

Thanks for your reply,

even with your script, and I modify the "path_to_xen_source" to p= oint
where my xen directory is. I still got this error.

ERROR: User requested feature xen
=C2=A0 =C2=A0 =C2=A0 =C2=A0 configure was not able to find it.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Install xen devel

What do you think what I am missing? Thank you!

Do you build xen before?

Thanks
Wen Congyang


Victor



On Thu, Mar 3, 2016 at 6:15 PM, Wen Congyang <wency@cn.fujitsu.com
<mailto:wency@= cn.fujitsu.com>> wrote:

=C2=A0 =C2=A0 =C2=A0On 03/04/2016 10:01 AM, Yu-An(Victor) Chen wrote:
=C2=A0 =C2=A0 =C2=A0> Hi,
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0> So I git clone
https://urldefense.pro= ofpoint.com/v2/url?u=3Dhttps-3A__github.com_wencongyang_qemu-2Dxen.git&= d=3DCwICaQ&c=3DclK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=3DIitX= 1U91-NhsQt0q4MJOLQ&m=3D4j1T2HKL4uKodf62b4Tz1XtOvX81uAqCqfOcD90CRAY&= s=3Ds0fo5ej8_vZ1PmOkDCuyIroS5Zi_KpDSHI8jqodSmrg&e=3D
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0> but i only see branch "con-xen-v2" inste= ad of " colo-xen-v2" so I
assume I use just use con-xen-v2.
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0> But then the following step:
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0> in both ~/qemu-colo and ~/qemu-xen
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0> ./configure --enable-xen --target-list=3Dx86_64-so= ftmmu
--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"


=C2=A0 =C2=A0 =C2=A0This command line is out of dated. The following is my = building
scripts:
=C2=A0 =C2=A0 =C2=A0#! /bin/bash

=C2=A0 =C2=A0 =C2=A0path_to_xen_source=3D/work/src/xen
=C2=A0 =C2=A0 =C2=A0#./configure --enable-xen --target-list=3Di386-softmmu = \
=C2=A0 =C2=A0 =C2=A0#=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 --extra-cfla= gs=3D"-I$path_to_xen_source/tools/include
-I$path_to_xen_source/tools/libxc/include
-I$path_to_xen_source/tools/xenstore/include" \
=C2=A0 =C2=A0 =C2=A0#=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 --extra-ldfl= ags=3D"-L$path_to_xen_source/tools/libxc
-L$path_to_xen_source/tools/xenstore"

=C2=A0 =C2=A0 =C2=A0extra_cflags=3D""
=C2=A0 =C2=A0 =C2=A0extra_cflags+=3D" -DXC_WANT_COMPAT_EVTCHN_API=3D1&= quot;
=C2=A0 =C2=A0 =C2=A0extra_cflags+=3D" -DXC_WANT_COMPAT_GNTTAB_API=3D1&= quot;
=C2=A0 =C2=A0 =C2=A0extra_cflags+=3D" -DXC_WANT_COMPAT_MAP_FOREIGN_API= =3D1"
=C2=A0 =C2=A0 =C2=A0extra_cflags+=3D" -I$path_to_xen_source/tools/incl= ude"
=C2=A0 =C2=A0 =C2=A0extra_cflags+=3D" -I$path_to_xen_source/tools/libs= /toollog/include"
=C2=A0 =C2=A0 =C2=A0extra_cflags+=3D" -I$path_to_xen_source/tools/libs= /evtchn/include"
=C2=A0 =C2=A0 =C2=A0extra_cflags+=3D" -I$path_to_xen_source/tools/libs= /gnttab/include"
=C2=A0 =C2=A0 =C2=A0extra_cflags+=3D"
-I$path_to_xen_source/tools/libs/foreignmemory/include"
=C2=A0 =C2=A0 =C2=A0extra_cflags+=3D" -I$path_to_xen_source/tools/libx= c/include"
=C2=A0 =C2=A0 =C2=A0extra_cflags+=3D" -I$path_to_xen_source/tools/xens= tore/include"
=C2=A0 =C2=A0 =C2=A0extra_cflags+=3D" -I$path_to_xen_source/tools/xens= tore/compat/include"
=C2=A0 =C2=A0 =C2=A0extra_cflags+=3D" "

=C2=A0 =C2=A0 =C2=A0extra_ldflags=3D""
=C2=A0 =C2=A0 =C2=A0extra_ldflags+=3D" -L$path_to_xen_source/tools/lib= xc"
=C2=A0 =C2=A0 =C2=A0extra_ldflags+=3D" -L$path_to_xen_source/tools/xen= store"
=C2=A0 =C2=A0 =C2=A0extra_ldflags+=3D" -L$path_to_xen_source/tools/lib= s/evtchn"
=C2=A0 =C2=A0 =C2=A0extra_ldflags+=3D" -L$path_to_xen_source/tools/lib= s/gnttab"
=C2=A0 =C2=A0 =C2=A0extra_ldflags+=3D" -L$path_to_xen_source/tools/lib= s/foreignmemory"
=C2=A0 =C2=A0 =C2=A0extra_ldflags+=3D"
-Wl,-rpath-link=3D$path_to_xen_source/tools/libs/toollog"
=C2=A0 =C2=A0 =C2=A0extra_ldflags+=3D"
-Wl,-rpath-link=3D$path_to_xen_source/tools/libs/evtchn"
=C2=A0 =C2=A0 =C2=A0extra_ldflags+=3D"
-Wl,-rpath-link=3D$path_to_xen_source/tools/libs/gnttab"
=C2=A0 =C2=A0 =C2=A0extra_ldflags+=3D" -Wl,-rpath-link=3D$path_to_xen_= source/tools/libs/call"
=C2=A0 =C2=A0 =C2=A0extra_ldflags+=3D"
-Wl,-rpath-link=3D$path_to_xen_source/tools/libs/foreignmemory"
=C2=A0 =C2=A0 =C2=A0extra_ldflags+=3D" "

=C2=A0 =C2=A0 =C2=A0./configure --enable-xen --target-list=3Di386-softmmu \=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0--extra-cflag= s=3D"$extra_cflags" \
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0--extra-ldfla= gs=3D"$extra_ldflags"

=C2=A0 =C2=A0 =C2=A0if [[ $? -ne 0 ]]; then
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0exit 1
=C2=A0 =C2=A0 =C2=A0fi

=C2=A0 =C2=A0 =C2=A0#make -j8 && make clean
=C2=A0 =C2=A0 =C2=A0make -j8

=C2=A0 =C2=A0 =C2=A0You can find the newest building way in tools/Makefile(= xen's codes):
=C2=A0 =C2=A0 =C2=A0subdir-all-qemu-xen-dir: qemu-xen-dir-find
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0if test -d $(QEMU_UPSTREAM_= LOC) ; then \
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0source=3D$(QEMU_UPSTREAM_LOC); \
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0else \
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0source=3D.; \
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0fi; \
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cd qemu-xen-dir; \
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0if $$source/scripts/traceto= ol.py --check-backend --backend
stderr ; then \

=C2=A0 enable_trace_backend=3D'--enable-trace-backend=3Dstderr'; \<= br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0else \
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0enable_trace_backend=3D'' ; \
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0fi ; \
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0$$source/configure --enable= -xen --target-list=3Di386-softmmu \
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0$(QEMU_XEN_ENABLE_DEBUG) \
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0$$enable_trace_backend \
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0--prefix=3D$(LIBEXEC) \
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0--libdir=3D$(LIBEXEC_LIB) \
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0--includedir=3D$(LIBEXEC_INC) \
=C2=A0 =C2=A0 =C2=A0....

=C2=A0 =C2=A0 =C2=A0Thanks
=C2=A0 =C2=A0 =C2=A0Wen Congyang

=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0> I got the following error message:
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0> "ERROR: User requested feature xen
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0 configure was not able = to find it.
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0 Install xen devel"=
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0> I found out the the error came from just simply do= ing this:
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0> ./configure --enable-xen
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0> I am thinking the reason is because I did this ste= p wrong:
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0> "path_to_xen_source=3D~/xen"
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0> Do I just simply copy and paste the above command = into the
terminal and execute?
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0> Thank you!
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0> Victor
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0> Thank you!
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0> On Thu, Mar 3, 2016 at 2:46 AM, Wen Congyang <<= a href=3D"mailto:wency@cn.fujitsu.com" target=3D"_blank">wency@cn.fujitsu.c= om
<mailto:wency@= cn.fujitsu.com> <mailto:wency@cn.fujitsu.com <mailto:
wency@cn.fujitsu.= com>>> wrote:
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0On 03/03/2016 05:39 PM, Yu-An(V= ictor) Chen wrote:
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> Hi Changlong,
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> Thanks for the reply,
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> Again when I am trying to = do the following:
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> 5. build qemu-colo
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> 1) cd ~/qemu-colo/; *git c= heckout colo-xen-v2*
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> *
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> *
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> I got this error message *= "error: pathspec 'colo-xen-v2' did
not match any file(s) known to git."* Even if I do git fetch, I still = get
the same error.
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> the qemu-colo I cloned fro= m is provided by you
https://urldefense.pr= oofpoint.com/v2/url?u=3Dhttps-3A__github.com_wencongyang_qemu-2Dcolo.git&am= p;d=3DCwICaQ&c=3DclK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=3DIi= tX1U91-NhsQt0q4MJOLQ&m=3DMgaousw-OxgAf6f9NTOk2AidO8unmTx8nKwiGLUCISU&am= p;s=3DTz2SiQ2gjQexttffgWiqgwj07qsfY4TpG4Hfcpo9Lco&e=3D
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>
https://urldefense.proofpo= int.com/v2/url?u=3Dhttps-3A__github.com_wencongyang_qemu-2Dxen&d=3DCwIC= aQ&c=3DclK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=3DIitX1U91-Nhs= Qt0q4MJOLQ&m=3DMgaousw-OxgAf6f9NTOk2AidO8unmTx8nKwiGLUCISU&s=3Dz-Ke= xB48-yzsD9EEJ5tC3p8tHRiRi7LoUiP-gF6kKX0&e=3D
, not qemu-colo
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> Thank you!
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> Victor
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0> On Thu, Feb 25, 2016 at 9:= 07 PM, Changlong Xie <
xiecl.fnst@c= n.fujitsu.com <mailto:xiecl.fnst@cn.fujitsu.com> <mailto:
xiecl.fnst@c= n.fujitsu.com <mailto:xiecl.fnst@cn.fujitsu.com>> <mailto:
xiecl.fnst@c= n.fujitsu.com <mailto:xiecl.fnst@cn.fujitsu.com> <mailto:
xiecl.fnst@c= n.fujitsu.com <mailto:xiecl.fnst@cn.fujitsu.com>>>> wrote:
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0On 02/2= 6/2016 12:55 PM, Yu-An(Victor) Chen wrote:
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0Hi Changlong,
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0Are you suggesting I should hold off on setting up
COLO for now?
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0No, jus= t following my steps.
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0Thanks<= br> =C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0-Xie
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0Thanks!
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0Victor
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0On Thu, Feb 25, 2016 at 8:19 PM, Changlong Xie <
xiecl.fnst@c= n.fujitsu.com <mailto:xiecl.fnst@cn.fujitsu.com> <mailto:
xiecl.fnst@c= n.fujitsu.com <mailto:xiecl.fnst@cn.fujitsu.com>> <mailto:
xiecl.fnst@c= n.fujitsu.com <mailto:xiecl.fnst@cn.fujitsu.com> <mailto:
xiecl.fnst@c= n.fujitsu.com <mailto:xiecl.fnst@cn.fujitsu.com>>>>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0wrote:
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0On 02/26/2016 11:38 AM, Yu-An(Victor) Chen wrote:
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Hi Changlong,
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Thanks for the reply!
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0So I am trying to follow your new
instructions, but when I am trying to do
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0this:
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 cd ~/colo-proxy/; git checkout
405527cbfa9f
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0I got the following error:
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0"error: pathspec '405527cbfa9f&= #39; did not
match any file(s) known to git."
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0I assume it is just a typo? Thank you! =C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0Hi victor
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0Please git clone
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
https://urldefe= nse.proofpoint.com/v2/url?u=3Dhttps-3A__github.com_Pating_colo-2Dproxy_tree= _changlox&d=3DCwICaQ&c=3DclK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_g= I&r=3DIitX1U91-NhsQt0q4MJOLQ&m=3DpCAkg_8tEQmGEZZoUlyePZjK7z-6aEmp-n= 6UrQRLWo4&s=3DWw-EAIszC-zQuVcDc4XpigwVbMG_4t2SpTg2PV6HTjM&e=3D<= br>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0*Notice* that, currently we implement colo proxy
as a kernel module what
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0is a temporary measure. But further more we'll
intergrate it in qemu and
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0drop this one, so both qemu-colo and xen-colo
will share the same proxy.
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0Please don't test this colo proxy now, there
maybe some bugs, but it's
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0acceptable.
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0Thanks
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 -Xie
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Victor
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>
=C2=A0 =C2=A0 =C2=A0>















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