From: Alex Zeffertt <alex.zeffertt@eu.citrix.com>
To: Yuvraj Agarwal <yuvraj@cs.ucsd.edu>
Cc: 'xen-devel' <xen-devel@lists.xensource.com>
Subject: Re: FW: using OCAML xenstored
Date: Wed, 26 May 2010 11:28:06 +0100 [thread overview]
Message-ID: <4BFCF7B6.2020608@eu.citrix.com> (raw)
In-Reply-To: <000201cafc8c$47deb880$d79c2980$@cs.ucsd.edu>
Some time ago I sent some patches against xen-ocaml-tools.hg to make it work as
replacement for the C xenstored in xen-unstable.hg. One of the patches was to
fix this install path issue:
http://lists.xensource.com/archives/html/xen-devel/2009-04/msg00697.html
I don't think these patches were applied. (I don't know if there is a reason for
this.) It might be worth checking out the whole patch queue if you are
intending to use it with xen-unstable.hg.
Regards,
Alex
On 26/05/10 05:31, Yuvraj Agarwal wrote:
>
>
> Hi, Just posting this on the list too in case anyone else has experience
> with the OCAML version of xenstored….
>
> --Yuvraj
>
> *From:* Yuvraj Agarwal [mailto:yuvraj@cs.ucsd.edu]
> *Sent:* Tuesday, May 25, 2010 10:26 AM
> *To:* 'Boris Derzhavets'; 'Pasi Kärkkäinen'
> *Subject:* RE: [Xen-devel] using OCAML xenstored
>
> Hi Boris and Pasi,
>
> I checked out the latest xen-testing from mercurial, and edited the
> Config.mk file to have the OCAML version of xenstored built.
>
> I checked and made sure that I have all the patches, and my xm info
> shows 4.0.1-rc1. After that I built using:
>
> make xen; make tools; make stubdom
>
> make install-xen;
> make install-tools PYTHON_PREFIX_ARG=;
>
> make install-stubdom
>
> Unfortunately, it looks like even though the new OCAML version of
> xenstored is built, it appears in /usr/bin/xenstored instead of the
> usual “/usr/sbin/xenstored” and the default part of the xenstored to use
> is the standard one (not the OCAML one)…
>
> Just FYI: This is an Ubuntu 10.04 64 bit system.
>
> root@ BlackBox:/# ll /usr/bin/xenstored (new OCAML xenstored I just
> built..)
>
> -rwxr-xr-x 1 root root 925039 2010-05-25 10:15 /usr/bin/xenstored
>
> root@ BlackBox:/# ll /usr/sbin/xenstored (<< Standard C xenstored)
>
> -rwxr-xr-x 1 root root 94728 2010-05-01 00:36 /usr/sbin/xenstored
>
> root@ BlackBox:/# which xenstored
>
> /usr/sbin/xenstored
>
> root@BlackBox:/#
>
> thanks
>
> Yuvraj
>
> * *
>
> *From:* xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] *On Behalf Of *Boris
> Derzhavets
> *Sent:* Sunday, May 23, 2010 11:47 AM
> *To:* Yuvraj Agarwal; Pasi Kärkkäinen
> *Cc:* xen-devel@lists.xensource.com
> *Subject:* Re: [Xen-devel] using OCAML xenstored
>
> > 4. "make xen", make "tools" and then the "make xen-install" and "make
> > install-tools PYTHON_PREFIX_ARG="
>
> make install-tools PYTHON_PREFIX_ARG=
>
> Wrong syntax when install tools
>
> Boris
> BTW. Just a notice.
>
> --- On *Sun, 5/23/10, Pasi Kärkkäinen /<pasik@iki.fi
> <mailto:pasik@iki.fi>>/* wrote:
>
>
> From: Pasi Kärkkäinen <pasik@iki.fi <mailto:pasik@iki.fi>>
> Subject: Re: [Xen-devel] using OCAML xenstored
> To: "Yuvraj Agarwal" <yuvraj@cs.ucsd.edu <mailto:yuvraj@cs.ucsd.edu>>
> Cc: xen-devel@lists.xensource.com <mailto:xen-devel@lists.xensource.com>
> Date: Sunday, May 23, 2010, 9:59 AM
>
> On Sat, May 22, 2010 at 05:48:58PM -0700, Yuvraj Agarwal wrote:
> > Hi All,
> >
> > I would like to give the OCAML version of xenstored a shot, since the
> > older version (in C) takes a long time to start up a large number of VMs.
> > I have a new machine (Ubuntu 10.04 64bit) that I plan to give this a try
> > with. Is there something else that I need to do besides the following:
> >
> > 1. Build the 2.6.32 pvops kernel as specified in:
> > http://wiki.xensource.com/xenwiki/XenParavirtOps
> > < DONE >
> > 2. Download the xen-4.0.0 stable version from
> > http://www.xen.org/products/xen_source.html
> > 3. change Config.mk flag CONFIG_OCAML_XENSTORED ?= n to "y" as"
> > CONFIG_OCAML_XENSTORED ?= y
> > 4. "make xen", make "tools" and then the "make xen-install" and "make
> > install-tools PYTHON_PREFIX_ARG="
> >
> > Is there something else needed? Are there any recent patches to the OCAML
> > xenstored that I need to apply?
> >
>
> Just browse through http://xenbits.xen.org/xen-unstable.hd and
> http://xenbits.xen.org/xen-4.0-testing.hg changelogs.
>
> xen-4.0-testing.hg is currently at 4.0.1-rc1 stage.
>
> -- Pasi
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com </mc/compose?to=Xen-devel@lists.xensource.com>
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2010-05-26 10:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 9:37 ocaml parallel build errors Christoph Egger
2010-05-17 9:55 ` Keir Fraser
2010-05-23 0:48 ` using OCAML xenstored Yuvraj Agarwal
2010-05-23 13:59 ` Pasi Kärkkäinen
2010-05-23 18:47 ` Boris Derzhavets
[not found] ` <0d2e01cafc2f$59453250$0bcf96f0$@ucsd.edu>
2010-05-26 4:31 ` FW: " Yuvraj Agarwal
2010-05-26 10:28 ` Alex Zeffertt [this message]
2010-05-26 18:27 ` Yuvraj Agarwal
2010-05-28 9:21 ` Alex Zeffertt
2010-05-28 9:51 ` Pasi Kärkkäinen
2010-05-28 10:13 ` Alex Zeffertt
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=4BFCF7B6.2020608@eu.citrix.com \
--to=alex.zeffertt@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=yuvraj@cs.ucsd.edu \
/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).