From: Changlong Xie <xiecl.fnst@cn.fujitsu.com>
To: "Yu-An(Victor) Chen" <chen116@usc.edu>
Cc: Wen Congyang <wency@cn.fujitsu.com>, xen-devel@lists.xen.org
Subject: Re: Patching error while setting up COLO
Date: Thu, 17 Mar 2016 09:41:33 +0800 [thread overview]
Message-ID: <56EA0B4D.5060809@cn.fujitsu.com> (raw)
In-Reply-To: <CANwucLkTpao+QsGh7oCOXwUsmPfDvSgD4HiQYTp-3VTR_MoNNw@mail.gmail.com>
On 03/17/2016 03:45 AM, Yu-An(Victor) Chen wrote:
> 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!
>
master:
br0 bind with eth0: 192.168.0.33
eth1: 192.168.1.33
eth2: 192.168.2.33
slave:
br0 bind with eth0: 192.168.0.88
br1: no ip address
eth1: 192.168.1.88
eth2: 192.168.2.88
master:eth0/slave:eth0/client connect to a same switch(a normal route
should be enough)
master:eth1 directly connected with slave:eth1 by cable(for forward)
master:eth2 directly connected with slave:eth2 by cable(for checkpoint)
It should be detail enough.
Thanks
-Xie
> Victor
>
>
> On Tue, Mar 15, 2016 at 11: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
>> <http://wiki.xenproject.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping> you
>> sent me, colo network interfaces between two servers should be set up like
>> 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 <xiecl.fnst@cn.fujitsu.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=/mnt/ramfs/active_disk.imghidden_disk=/mnt/ramfs/hidden_disk.imglocal_img=/root/xie/suse-64hvm.img*
>>>> tmp_disk_size=`./qemu-colo/qemu-img info $local_img |grep 'virtual size'
>>>> |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=2G
>>>> 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=/mnt/ramfs/active_disk.imghidden_disk=/mnt/ramfs/hidden_disk.imglocal_img=/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
>>> "/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 <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 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 <wency@cn.fujitsu.com
>>>>>>
>>>>> <mailto:wency@cn.fujitsu.com>> 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=https-3A__github.com_wencongyang_qemu-2Dxen.git&d=CwICaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=IitX1U91-NhsQt0q4MJOLQ&m=4j1T2HKL4uKodf62b4Tz1XtOvX81uAqCqfOcD90CRAY&s=s0fo5ej8_vZ1PmOkDCuyIroS5Zi_KpDSHI8jqodSmrg&e=
>>>>>
>>>>>> >
>>>>>> > but i only see branch "con-xen-v2" instead of " colo-xen-v2" so
>>>>>> 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=x86_64-softmmu
>>>>>>
>>>>> --extra-cflags="-I$path_to_xen_source/tools/include
>>>>> -I$path_to_xen_source/tools/libxc -I$path_to_xen_source/tools/xenstore"
>>>>> --extra-ldflags="-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=/work/src/xen
>>>>>> #./configure --enable-xen --target-list=i386-softmmu \
>>>>>> # --extra-cflags="-I$path_to_xen_source/tools/include
>>>>>>
>>>>> -I$path_to_xen_source/tools/libxc/include
>>>>> -I$path_to_xen_source/tools/xenstore/include" \
>>>>>
>>>>>> # --extra-ldflags="-L$path_to_xen_source/tools/libxc
>>>>>>
>>>>> -L$path_to_xen_source/tools/xenstore"
>>>>>
>>>>>>
>>>>>> extra_cflags=""
>>>>>> extra_cflags+=" -DXC_WANT_COMPAT_EVTCHN_API=1"
>>>>>> extra_cflags+=" -DXC_WANT_COMPAT_GNTTAB_API=1"
>>>>>> extra_cflags+=" -DXC_WANT_COMPAT_MAP_FOREIGN_API=1"
>>>>>> extra_cflags+=" -I$path_to_xen_source/tools/include"
>>>>>> extra_cflags+=" -I$path_to_xen_source/tools/libs/toollog/include"
>>>>>> extra_cflags+=" -I$path_to_xen_source/tools/libs/evtchn/include"
>>>>>> extra_cflags+=" -I$path_to_xen_source/tools/libs/gnttab/include"
>>>>>> extra_cflags+="
>>>>>>
>>>>> -I$path_to_xen_source/tools/libs/foreignmemory/include"
>>>>>
>>>>>> extra_cflags+=" -I$path_to_xen_source/tools/libxc/include"
>>>>>> extra_cflags+=" -I$path_to_xen_source/tools/xenstore/include"
>>>>>> extra_cflags+="
>>>>>> -I$path_to_xen_source/tools/xenstore/compat/include"
>>>>>> extra_cflags+=" "
>>>>>>
>>>>>> extra_ldflags=""
>>>>>> extra_ldflags+=" -L$path_to_xen_source/tools/libxc"
>>>>>> extra_ldflags+=" -L$path_to_xen_source/tools/xenstore"
>>>>>> extra_ldflags+=" -L$path_to_xen_source/tools/libs/evtchn"
>>>>>> extra_ldflags+=" -L$path_to_xen_source/tools/libs/gnttab"
>>>>>> extra_ldflags+=" -L$path_to_xen_source/tools/libs/foreignmemory"
>>>>>> extra_ldflags+="
>>>>>>
>>>>> -Wl,-rpath-link=$path_to_xen_source/tools/libs/toollog"
>>>>>
>>>>>> extra_ldflags+="
>>>>>>
>>>>> -Wl,-rpath-link=$path_to_xen_source/tools/libs/evtchn"
>>>>>
>>>>>> extra_ldflags+="
>>>>>>
>>>>> -Wl,-rpath-link=$path_to_xen_source/tools/libs/gnttab"
>>>>>
>>>>>> extra_ldflags+="
>>>>>> -Wl,-rpath-link=$path_to_xen_source/tools/libs/call"
>>>>>> extra_ldflags+="
>>>>>>
>>>>> -Wl,-rpath-link=$path_to_xen_source/tools/libs/foreignmemory"
>>>>>
>>>>>> extra_ldflags+=" "
>>>>>>
>>>>>> ./configure --enable-xen --target-list=i386-softmmu \
>>>>>> --extra-cflags="$extra_cflags" \
>>>>>> --extra-ldflags="$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=$(QEMU_UPSTREAM_LOC); \
>>>>>> else \
>>>>>> source=.; \
>>>>>> fi; \
>>>>>> cd qemu-xen-dir; \
>>>>>> if $$source/scripts/tracetool.py --check-backend --backend
>>>>>>
>>>>> stderr ; then \
>>>>>
>>>>>>
>>>>>> enable_trace_backend='--enable-trace-backend=stderr'; \
>>>>>
>>>>>> else \
>>>>>> enable_trace_backend='' ; \
>>>>>> fi ; \
>>>>>> $$source/configure --enable-xen
>>>>>> --target-list=i386-softmmu \
>>>>>> $(QEMU_XEN_ENABLE_DEBUG) \
>>>>>> $$enable_trace_backend \
>>>>>> --prefix=$(LIBEXEC) \
>>>>>> --libdir=$(LIBEXEC_LIB) \
>>>>>> --includedir=$(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=~/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
>>>>>>
>>>>> <mailto:wency@cn.fujitsu.com> <mailto:wency@cn.fujitsu.com <mailto:
>>>>> 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=https-3A__github.com_wencongyang_qemu-2Dcolo.git&d=CwICaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=IitX1U91-NhsQt0q4MJOLQ&m=Mgaousw-OxgAf6f9NTOk2AidO8unmTx8nKwiGLUCISU&s=Tz2SiQ2gjQexttffgWiqgwj07qsfY4TpG4Hfcpo9Lco&e=
>>>>>
>>>>>> >
>>>>>> >
>>>>>>
>>>>>
>>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_wencongyang_qemu-2Dxen&d=CwICaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=IitX1U91-NhsQt0q4MJOLQ&m=Mgaousw-OxgAf6f9NTOk2AidO8unmTx8nKwiGLUCISU&s=z-KexB48-yzsD9EEJ5tC3p8tHRiRi7LoUiP-gF6kKX0&e=
>>>>> , not qemu-colo
>>>>>
>>>>>> >
>>>>>> > >
>>>>>> > > Thank you!
>>>>>> > >
>>>>>> > > Victor
>>>>>> > >
>>>>>> > >
>>>>>> > >
>>>>>> > > On Thu, Feb 25, 2016 at 9:07 PM, Changlong Xie <
>>>>>>
>>>>> xiecl.fnst@cn.fujitsu.com <mailto:xiecl.fnst@cn.fujitsu.com> <mailto:
>>>>> xiecl.fnst@cn.fujitsu.com <mailto:xiecl.fnst@cn.fujitsu.com>> <mailto:
>>>>> xiecl.fnst@cn.fujitsu.com <mailto:xiecl.fnst@cn.fujitsu.com> <mailto:
>>>>> xiecl.fnst@cn.fujitsu.com <mailto: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 <mailto:xiecl.fnst@cn.fujitsu.com> <mailto:
>>>>> xiecl.fnst@cn.fujitsu.com <mailto:xiecl.fnst@cn.fujitsu.com>> <mailto:
>>>>> xiecl.fnst@cn.fujitsu.com <mailto:xiecl.fnst@cn.fujitsu.com> <mailto:
>>>>> xiecl.fnst@cn.fujitsu.com <mailto: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=https-3A__github.com_Pating_colo-2Dproxy_tree_changlox&d=CwICaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=IitX1U91-NhsQt0q4MJOLQ&m=pCAkg_8tEQmGEZZoUlyePZjK7z-6aEmp-n6UrQRLWo4&s=Ww-EAIszC-zQuVcDc4XpigwVbMG_4t2SpTg2PV6HTjM&e=
>>>>>
>>>>>> > > *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-colo
>>>>>>
>>>>> will share the same proxy.
>>>>>
>>>>>> > > Please don't test this colo proxy now, there
>>>>>>
>>>>> maybe some bugs, but it's
>>>>>
>>>>>> > > acceptable.
>>>>>> > >
>>>>>> > > Thanks
>>>>>> > > -Xie
>>>>>> > >
>>>>>> > >
>>>>>> > > Victor
>>>>>> > >
>>>>>> > >
>>>>>> > >
>>>>>> > >
>>>>>> > >
>>>>>> > >
>>>>>> > >
>>>>>> > >
>>>>>> > >
>>>>>> > >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>
>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-03-17 1:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 5:17 Patching error while setting up COLO Yu-An(Victor) Chen
2016-02-25 8:49 ` Changlong Xie
2016-02-25 10:31 ` Ian Campbell
2016-02-26 2:38 ` Changlong Xie
2016-02-26 3:38 ` Yu-An(Victor) Chen
2016-02-26 4:19 ` Changlong Xie
2016-02-26 4:55 ` Yu-An(Victor) Chen
2016-02-26 5:07 ` Changlong Xie
2016-03-03 9:39 ` Yu-An(Victor) Chen
2016-03-03 10:46 ` Wen Congyang
2016-03-04 2:01 ` Yu-An(Victor) Chen
2016-03-04 2:15 ` Wen Congyang
2016-03-05 1:51 ` Yu-An(Victor) Chen
2016-03-07 1:12 ` Wen Congyang
2016-03-08 22:57 ` Yu-An(Victor) Chen
2016-03-14 8:36 ` Changlong Xie
2016-03-16 6:06 ` Yu-An(Victor) Chen
2016-03-16 19:45 ` Yu-An(Victor) Chen
2016-03-17 1:41 ` Changlong Xie [this message]
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=56EA0B4D.5060809@cn.fujitsu.com \
--to=xiecl.fnst@cn.fujitsu.com \
--cc=chen116@usc.edu \
--cc=wency@cn.fujitsu.com \
--cc=xen-devel@lists.xen.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.