* Patching error while setting up COLO @ 2016-02-25 5:17 Yu-An(Victor) Chen 2016-02-25 8:49 ` Changlong Xie 0 siblings, 1 reply; 19+ messages in thread From: Yu-An(Victor) Chen @ 2016-02-25 5:17 UTC (permalink / raw) To: xen-devel [-- Attachment #1.1: Type: text/plain, Size: 692 bytes --] Hi, I am trying to set up COLO by following this http://wiki.xenproject.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping I was able to follow the step up to $git am ~/ColoPatchForQemu/*.patch When I try to run the above command, I got the following error: error: patch failed: include/hw/xen/xen_common.h:186 error: include/hw/xen/xen_common.h: patch does not apply error: patch failed: xen-hvm.c:85 error: xen-hvm.c: patch does not apply Patch failed at 0018 Revert "Xen: Use the ioreq-server API when available" The copy of the patch that failed is found in: /root/xen/tools/qemu-xen-dir/.git/rebase-apply/patch Please let me know how I can solve this patching error. Thank you! Victor [-- Attachment #1.2: Type: text/html, Size: 1322 bytes --] [-- Attachment #2: Type: text/plain, Size: 126 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Patching error while setting up COLO 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 0 siblings, 1 reply; 19+ messages in thread From: Changlong Xie @ 2016-02-25 8:49 UTC (permalink / raw) To: Yu-An(Victor) Chen, xen-devel; +Cc: Wen Congyang [-- Attachment #1: Type: text/plain, Size: 5141 bytes --] On 02/25/2016 01:17 PM, Yu-An(Victor) Chen wrote: > Hi, > > I am trying to set up COLO by following this > http://wiki.xenproject.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping > > I was able to follow the step up to > > $git am ~/ColoPatchForQemu/*.patch > > When I try to run the above command, I got the following error: > > error: patch failed: include/hw/xen/xen_common.h:186 > error: include/hw/xen/xen_common.h: patch does not apply > error: patch failed: xen-hvm.c:85 > error: xen-hvm.c: patch does not apply > Patch failed at 0018 Revert "Xen: Use the ioreq-server API when available" > The copy of the patch that failed is found in: > /root/xen/tools/qemu-xen-dir/.git/rebase-apply/patch > > Please let me know how I can solve this patching error. Thank you! > Hi Victor Sorry for this. Since we have no privilege to update the Wiki for a long time so most contents of this page are dated : ( 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 >= 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（we use "SUSE Linux Enterprise Server 11" currently）. REDHAT and Ubuntu is not 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: http://wiki.xenproject.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping - Test environment prepare On both Primary/Secondary hosts: 1. cd ~ git clone https://github.com/wencongyang/colo-proxy git clone https://github.com/macrosheep/iptables.git git clone https://github.com/torvalds/linux git clone https://github.com/wencongyang/qemu-colo git clone https://github.com/wencongyang/xen 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: http://wiki.xenproject.org/wiki/Mainline_Linux_Kernel_Configs 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=/usr/ --libdir=/usr/lib64; make; make install 5. build qemu-colo 1) cd ~/qemu-colo/; git checkout colo-xen-v2 2) path_to_xen_source=~/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" 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=eth1 on secondary: rm -f /var/log/xen/* rm -f /var/lib/xen/userdata-d.* service xencommons start modprobe xt_SECCOLO active_disk=/mnt/ramfs/active_disk.img hidden_disk=/mnt/ramfs/hidden_disk.img local_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 } 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 > http://lists.xen.org/xen-devel > [-- Attachment #2: hvm_nopv_colo --] [-- Type: text/plain, Size: 1180 bytes --] builder='hvm' memory='1024' vcpus=2 cpus=['2','3'] name='hvm_nopv_colo' device_model_version='qemu-xen' device_model_override='/root/xie/qemu-colo/x86_64-softmmu/qemu-system-x86_64' #需要把'vdev=sda'改成'vdev=hda'因为备端某些bug(libxl__domain_suspend_device_model->libxl__qmp_save->xen-save-devices-state失败),即不用scsi而用ide disk = [ 'format=raw,devtype=disk,access=w,backendtype=qdisk,vdev=hda,colo,colo-host=192.168.3.2,colo-port=9000,colo-export=qdisk1,active-disk=/mnt/ramfs/active_disk.img,hidden-disk=/mnt/ramfs/hidden_disk.img,target=/root/xie/suse-64hvm.img'] vif = [ 'mac=00:16:4f:00:00:11, bridge=br0, model=e1000, forwarddev=eth1' ] #disk = [ '/root/xie/suse-64hvm.img,raw,hda,rw','/root/SLES-11-SP3-DVD-x86_64-GM-DVD1.iso,,hdc,r,cdrom' ] #vif = [ 'mac=00:16:4f:00:00:11,bridge=br0,model=virtio-net' ] #----------------------------------------------------------------------------- # boot on floppy (a), hard disk (c), Network (n) or CD-ROM (d) # default: hard disk, cd-rom, floppy boot='c' sdl=0 vnc=1 vnclisten='' stdvga = 0 serial='pty' apic=1 apci=1 pae=1 extid=0 keymap='en-us' localtime=1 hpet=1 usbdevice='tablet' xen_platform_pci = 0 [-- Attachment #3: Type: text/plain, Size: 126 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Patching error while setting up COLO 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 0 siblings, 2 replies; 19+ messages in thread From: Ian Campbell @ 2016-02-25 10:31 UTC (permalink / raw) To: Changlong Xie, Yu-An(Victor) Chen, xen-devel; +Cc: Wen Congyang 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 long > 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: http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html > > 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 >= 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（we use "SUSE Linux > Enterprise Server 11" currently）. REDHAT and Ubuntu is not 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: http://wiki.xenproject.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping > > - Test environment prepare > > On both Primary/Secondary hosts: > 1. > cd ~ > git clone https://github.com/wencongyang/colo-proxy > git clone https://github.com/macrosheep/iptables.git > git clone https://github.com/torvalds/linux > git clone https://github.com/wencongyang/qemu-colo > git clone https://github.com/wencongyang/xen > > 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: http://wiki.xenproject.org/wiki/Mainline_Linux_Kernel_Configs > 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=/usr/ > --libdir=/usr/lib64; make; make install > > 5. build qemu-colo > 1) cd ~/qemu-colo/; git checkout colo-xen-v2 > 2) > path_to_xen_source=~/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" > 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=eth1 > > on secondary: > rm -f /var/log/xen/* > rm -f /var/lib/xen/userdata-d.* > service xencommons start > modprobe xt_SECCOLO > active_disk=/mnt/ramfs/active_disk.img > hidden_disk=/mnt/ramfs/hidden_disk.img > local_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 > } > 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 > > http://lists.xen.org/xen-devel > > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Patching error while setting up COLO 2016-02-25 10:31 ` Ian Campbell @ 2016-02-26 2:38 ` Changlong Xie 2016-02-26 3:38 ` Yu-An(Victor) Chen 1 sibling, 0 replies; 19+ messages in thread From: Changlong Xie @ 2016-02-26 2:38 UTC (permalink / raw) To: Ian Campbell, Yu-An(Victor) Chen, xen-devel; +Cc: Wen Congyang On 02/25/2016 06:31 PM, Ian Campbell wrote: >> Sorry for this. Since we have no privilege to update the Wiki for a long >> >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: > http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html > Sound good to me. Thanks -Xie >> > >> >Anyway i'll write down detail steps here for colo on XEN. >> > _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Patching error while setting up COLO 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 1 sibling, 1 reply; 19+ messages in thread From: Yu-An(Victor) Chen @ 2016-02-26 3:38 UTC (permalink / raw) To: Ian Campbell; +Cc: Changlong Xie, Wen Congyang, xen-devel [-- Attachment #1.1: Type: text/plain, Size: 8277 bytes --] 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 <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 long > > 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=http-3A__xenproject.org_component_content_article_100-2Dmisc_145-2Drequest-2Dto-2Dbe-2Dmade-2Da-2Dwiki-2Deditor.html&d=CwIFaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=IitX1U91-NhsQt0q4MJOLQ&m=Vnnj3Mx_nu951rfkiPcsuwuboBSLRcYYu30Uho1r7kw&s=81rG3g_B23OhGxLWYNA7Hs6cFJy4VxE2Sdqhr0qe7Ds&e= > > > > > 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 >= 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（we use "SUSE Linux > > Enterprise Server 11" currently）. REDHAT and Ubuntu is not 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=http-3A__wiki.xenproject.org_wiki_COLO-5F-2D-5FCoarse-5FGrain-5FLock-5FStepping&d=CwIFaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=IitX1U91-NhsQt0q4MJOLQ&m=Vnnj3Mx_nu951rfkiPcsuwuboBSLRcYYu30Uho1r7kw&s=-vAQ55Sl3YGAa0EmRYKB2pvrRVa_D6nLQCNiOGz7IeI&e= > > > > - Test environment prepare > > > > On both Primary/Secondary hosts: > > 1. > > cd ~ > > git clone > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_wencongyang_colo-2Dproxy&d=CwIFaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=IitX1U91-NhsQt0q4MJOLQ&m=Vnnj3Mx_nu951rfkiPcsuwuboBSLRcYYu30Uho1r7kw&s=uS-WmNmGEeeyytonbMxBCcbSHRzQJXUa6_pvkiGEPh4&e= > > git clone > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_macrosheep_iptables.git&d=CwIFaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=IitX1U91-NhsQt0q4MJOLQ&m=Vnnj3Mx_nu951rfkiPcsuwuboBSLRcYYu30Uho1r7kw&s=ZycjXRwwoyK_M8zU4CS8QsVaLWXzjx8mwtlEEIRlY_I&e= > > git clone > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_torvalds_linux&d=CwIFaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=IitX1U91-NhsQt0q4MJOLQ&m=Vnnj3Mx_nu951rfkiPcsuwuboBSLRcYYu30Uho1r7kw&s=TeB7X5i8Ua7jemThOaxH4oNER5ZMCcs1dyqUxZVIWPY&e= > > git clone > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_wencongyang_qemu-2Dcolo&d=CwIFaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=IitX1U91-NhsQt0q4MJOLQ&m=Vnnj3Mx_nu951rfkiPcsuwuboBSLRcYYu30Uho1r7kw&s=2kSeFd9-e3hISEJ1QZB1uzfVs8TxQwFQ_Rt4EuySfu8&e= > > git clone > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_wencongyang_xen&d=CwIFaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=IitX1U91-NhsQt0q4MJOLQ&m=Vnnj3Mx_nu951rfkiPcsuwuboBSLRcYYu30Uho1r7kw&s=ztSkYn_Z-t4_vnCdkHl09RzW8LaD9nnkeebyhac3a_0&e= > > > > 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=http-3A__wiki.xenproject.org_wiki_Mainline-5FLinux-5FKernel-5FConfigs&d=CwIFaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=IitX1U91-NhsQt0q4MJOLQ&m=Vnnj3Mx_nu951rfkiPcsuwuboBSLRcYYu30Uho1r7kw&s=3A6be8ZmUe1yTPFuGHZp3fD_LAtyo_5MW2jdVrBSDcs&e= > > 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=/usr/ > > --libdir=/usr/lib64; make; make install > > > > 5. build qemu-colo > > 1) cd ~/qemu-colo/; git checkout colo-xen-v2 > > 2) > > path_to_xen_source=~/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" > > 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=eth1 > > > > on secondary: > > rm -f /var/log/xen/* > > rm -f /var/lib/xen/userdata-d.* > > service xencommons start > > modprobe xt_SECCOLO > > active_disk=/mnt/ramfs/active_disk.img > > hidden_disk=/mnt/ramfs/hidden_disk.img > > local_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 > > } > > 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=http-3A__lists.xen.org_xen-2Ddevel&d=CwIFaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=IitX1U91-NhsQt0q4MJOLQ&m=Vnnj3Mx_nu951rfkiPcsuwuboBSLRcYYu30Uho1r7kw&s=pwe0Fv2-rSmRy2SSYtNS48UnU0Dh911PUXDso8uG0nU&e= > > > > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xen.org > > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.xen.org_xen-2Ddevel&d=CwIFaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=IitX1U91-NhsQt0q4MJOLQ&m=Vnnj3Mx_nu951rfkiPcsuwuboBSLRcYYu30Uho1r7kw&s=pwe0Fv2-rSmRy2SSYtNS48UnU0Dh911PUXDso8uG0nU&e= > [-- Attachment #1.2: Type: text/html, Size: 14058 bytes --] [-- Attachment #2: Type: text/plain, Size: 126 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Patching error while setting up COLO 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 0 siblings, 1 reply; 19+ messages in thread From: Changlong Xie @ 2016-02-26 4:19 UTC (permalink / raw) To: Yu-An(Victor) Chen; +Cc: Wen Congyang, xen-devel 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://github.com/Pating/colo-proxy/tree/changlox *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 ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Patching error while setting up COLO 2016-02-26 4:19 ` Changlong Xie @ 2016-02-26 4:55 ` Yu-An(Victor) Chen 2016-02-26 5:07 ` Changlong Xie 0 siblings, 1 reply; 19+ messages in thread From: Yu-An(Victor) Chen @ 2016-02-26 4:55 UTC (permalink / raw) To: Changlong Xie; +Cc: Wen Congyang, xen-devel [-- Attachment #1.1: Type: text/plain, Size: 1301 bytes --] Hi Changlong, Are you suggesting I should hold off on setting up COLO for now? Thanks! Victor On Thu, Feb 25, 2016 at 8:19 PM, Changlong Xie <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 >> > > > [-- Attachment #1.2: Type: text/html, Size: 2353 bytes --] [-- Attachment #2: Type: text/plain, Size: 126 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Patching error while setting up COLO 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 0 siblings, 1 reply; 19+ messages in thread From: Changlong Xie @ 2016-02-26 5:07 UTC (permalink / raw) To: Yu-An(Victor) Chen; +Cc: Wen Congyang, xen-devel 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> > 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 ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Patching error while setting up COLO 2016-02-26 5:07 ` Changlong Xie @ 2016-03-03 9:39 ` Yu-An(Victor) Chen 2016-03-03 10:46 ` Wen Congyang 0 siblings, 1 reply; 19+ messages in thread From: Yu-An(Victor) Chen @ 2016-03-03 9:39 UTC (permalink / raw) To: Changlong Xie; +Cc: Wen Congyang, xen-devel [-- Attachment #1.1: Type: text/plain, Size: 2093 bytes --] 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://github.com/wencongyang/qemu-colo.git Thank you! Victor On Thu, Feb 25, 2016 at 9:07 PM, Changlong Xie <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 >> > >> 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 >>>> >>>> >>> >>> >>> >> >> >> > > [-- Attachment #1.2: Type: text/html, Size: 4394 bytes --] [-- Attachment #2: Type: text/plain, Size: 126 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Patching error while setting up COLO 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 0 siblings, 1 reply; 19+ messages in thread From: Wen Congyang @ 2016-03-03 10:46 UTC (permalink / raw) To: Yu-An(Victor) Chen, Changlong Xie; +Cc: xen-devel 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://github.com/wencongyang/qemu-colo.git https://github.com/wencongyang/qemu-xen, 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>> 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>> > 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 ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Patching error while setting up COLO 2016-03-03 10:46 ` Wen Congyang @ 2016-03-04 2:01 ` Yu-An(Victor) Chen 2016-03-04 2:15 ` Wen Congyang 0 siblings, 1 reply; 19+ messages in thread From: Yu-An(Victor) Chen @ 2016-03-04 2:01 UTC (permalink / raw) To: Wen Congyang; +Cc: Changlong Xie, xen-devel [-- Attachment #1.1: Type: text/plain, Size: 4255 bytes --] Hi, So I git clone https://github.com/wencongyang/qemu-xen.git 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" 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> 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>> 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>> > > 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 > > > > > > > > > > > > > > > > > > > > > > > > [-- Attachment #1.2: Type: text/html, Size: 8833 bytes --] [-- Attachment #2: Type: text/plain, Size: 126 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Patching error while setting up COLO 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 0 siblings, 1 reply; 19+ messages in thread From: Wen Congyang @ 2016-03-04 2:15 UTC (permalink / raw) To: Yu-An(Victor) Chen; +Cc: Changlong Xie, xen-devel On 03/04/2016 10:01 AM, Yu-An(Victor) Chen wrote: > Hi, > > So I git clone https://github.com/wencongyang/qemu-xen.git > > 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>> 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>>> 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>>> > > 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 ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Patching error while setting up COLO 2016-03-04 2:15 ` Wen Congyang @ 2016-03-05 1:51 ` Yu-An(Victor) Chen 2016-03-07 1:12 ` Wen Congyang 0 siblings, 1 reply; 19+ messages in thread From: Yu-An(Victor) Chen @ 2016-03-05 1:51 UTC (permalink / raw) To: Wen Congyang; +Cc: Changlong Xie, xen-devel [-- Attachment #1.1: Type: text/plain, Size: 8921 bytes --] 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! Victor On Thu, Mar 3, 2016 at 6:15 PM, Wen Congyang <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>> 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>>> 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>>> > > > 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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > [-- Attachment #1.2: Type: text/html, Size: 14203 bytes --] [-- Attachment #2: Type: text/plain, Size: 126 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Patching error while setting up COLO 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 0 siblings, 1 reply; 19+ messages in thread From: Wen Congyang @ 2016-03-07 1:12 UTC (permalink / raw) To: Yu-An(Victor) Chen; +Cc: Changlong Xie, xen-devel 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 ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Patching error while setting up COLO 2016-03-07 1:12 ` Wen Congyang @ 2016-03-08 22:57 ` Yu-An(Victor) Chen 2016-03-14 8:36 ` Changlong Xie 0 siblings, 1 reply; 19+ messages in thread From: Yu-An(Victor) Chen @ 2016-03-08 22:57 UTC (permalink / raw) To: Wen Congyang; +Cc: Changlong Xie, xen-devel [-- Attachment #1.1: Type: text/plain, Size: 12484 bytes --] 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? 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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > [-- Attachment #1.2: Type: text/html, Size: 22144 bytes --] [-- Attachment #2: Type: text/plain, Size: 126 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Patching error while setting up COLO 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 0 siblings, 1 reply; 19+ messages in thread From: Changlong Xie @ 2016-03-14 8:36 UTC (permalink / raw) To: Yu-An(Victor) Chen, Wen Congyang; +Cc: xen-devel 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 ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Patching error while setting up COLO 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 0 siblings, 1 reply; 19+ messages in thread From: Yu-An(Victor) Chen @ 2016-03-16 6:06 UTC (permalink / raw) To: Changlong Xie; +Cc: Wen Congyang, xen-devel [-- Attachment #1.1: Type: text/plain, Size: 14548 bytes --] 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 >>>> > > >>>> > > >>>> > > >>>> > > >>>> > > >>>> > > >>>> > > >>>> > > >>>> > > >>>> > > >>>> > >>>> > >>>> > >>>> > >>>> >>>> >>>> >>>> >>>> >>> >>> >>> >>> >> >> >> > > [-- Attachment #1.2: Type: text/html, Size: 24395 bytes --] [-- Attachment #2: Type: text/plain, Size: 126 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Patching error while setting up COLO 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 0 siblings, 1 reply; 19+ messages in thread From: Yu-An(Victor) Chen @ 2016-03-16 19:45 UTC (permalink / raw) To: Changlong Xie; +Cc: Wen Congyang, xen-devel [-- Attachment #1.1: Type: text/plain, Size: 15757 bytes --] 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 <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 >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> >>> >>> >>> >> >> > [-- Attachment #1.2: Type: text/html, Size: 25831 bytes --] [-- Attachment #2: Type: text/plain, Size: 126 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Patching error while setting up COLO 2016-03-16 19:45 ` Yu-An(Victor) Chen @ 2016-03-17 1:41 ` Changlong Xie 0 siblings, 0 replies; 19+ messages in thread From: Changlong Xie @ 2016-03-17 1:41 UTC (permalink / raw) To: Yu-An(Victor) Chen; +Cc: Wen Congyang, xen-devel 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 ^ permalink raw reply [flat|nested] 19+ messages in thread
end of thread, other threads:[~2016-03-17 1:41 UTC | newest] Thread overview: 19+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 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 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).