From: "Yu-An(Victor) Chen" <chen116@usc.edu>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: Changlong Xie <xiecl.fnst@cn.fujitsu.com>, xen-devel@lists.xen.org
Subject: Re: Patching error while setting up COLO
Date: Thu, 3 Mar 2016 18:01:10 -0800 [thread overview]
Message-ID: <CANwucLnx7L_UKkk16SbW4kkh2nn0xdrjL-=dpyJxiTK7FfZhfg@mail.gmail.com> (raw)
In-Reply-To: <56D8161E.7010707@cn.fujitsu.com>
[-- 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
next prev parent reply other threads:[~2016-03-04 2:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 5:17 Patching error while setting up COLO Yu-An(Victor) Chen
2016-02-25 8:49 ` Changlong Xie
2016-02-25 10:31 ` Ian Campbell
2016-02-26 2:38 ` Changlong Xie
2016-02-26 3:38 ` Yu-An(Victor) Chen
2016-02-26 4:19 ` Changlong Xie
2016-02-26 4:55 ` Yu-An(Victor) Chen
2016-02-26 5:07 ` Changlong Xie
2016-03-03 9:39 ` Yu-An(Victor) Chen
2016-03-03 10:46 ` Wen Congyang
2016-03-04 2:01 ` Yu-An(Victor) Chen [this message]
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANwucLnx7L_UKkk16SbW4kkh2nn0xdrjL-=dpyJxiTK7FfZhfg@mail.gmail.com' \
--to=chen116@usc.edu \
--cc=wency@cn.fujitsu.com \
--cc=xen-devel@lists.xen.org \
--cc=xiecl.fnst@cn.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).