From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dilshan Jayarathna Subject: Re: ACM not enabled with xen-unstable Date: Thu, 25 Sep 2008 10:30:45 +1000 Message-ID: <48DADBB5.7010005@ics.mq.edu.au> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1268265516==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --===============1268265516== Content-Type: multipart/alternative; boundary="------------080205050206030200080203" This is a multi-part message in MIME format. --------------080205050206030200080203 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Hi George, Indeed, you're correct. It wasn't even uncommented. I'll try with (xsm_module_name acm). What would be the best suitable version for try out XSM/ACM? I was thinking xen-unstable due to constant patches. Thanks, Dilshan George S. Coker, II wrote: > I bet the problem is that you don=B9t have an entry like, > (xsm_module_name acm) in your xend-config.sxp file. A patch was recent= ly > introduced into the python tool chain that removed some autogenerated p= ython > code based on these variables in favor of a key-value pair set in > xend-config.sxp. The default setting is dummy and if you have a > pre-existing xend-config, you don't get a default key-value entry on a = fresh > -unstable install. > > George > > On 9/23/08 8:00 PM, "Dilshan Jayarathna" wrote: > > =20 >> Hi, >> >> I am trying build Xen with XSM enabled using xen-unstable.hg. >> >> When I do: >> # xm getpolicy >> I get: >> Supported security subsystems: None >> >> It looks like it is creating all accessory directories, etc., but ACM = doesn't >> seems to be enabled. >> >> Config.mk file has: >> # Enable XSM security module. Enabling XSM requires selection of an >> # XSM security module (FLASK_ENABLE or ACM_SECURITY). >> XSM_ENABLE ?=3D y >> FLASK_ENABLE ?=3D n >> ACM_SECURITY ?=3D y >> >> Build and install completes without errors. I also updated the unstabl= e.hg >> using 'hg pull -u', but no luck. >> I've built 3.2.1 as well as 3.3.0 with ACM enabled and everything seem= s to be >> OK. >> >> Is there anything extra I should do with xen-unstable.hg? >> >> OS: CentOS 5.2 (i386) >> >> Regards, >> Dilshan >> >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel >> =20 > > > =20 --------------080205050206030200080203 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi George,

Indeed, you're correct. It wasn't even uncommented.

I'll try with (xsm_module_name acm).

What would be the best suitable version for try out XSM/ACM?
I was thinking xen-unstable due to constant patches.

Thanks,
Dilshan

George S. Coker, II wrote:

I bet the problem is that you don¹t have an entry like,
(xsm_module_name acm) in your xend-config.sxp file.  A patch was recently
introduced into the python tool chain that removed some autogenerated python
code based on these variables in favor of a key-value pair set in
xend-config.sxp.  The default setting is dummy and if you have a
pre-existing xend-config, you don't get a default key-value entry on a fresh
-unstable install.

George

On 9/23/08 8:00 PM, "Dilshan Jayarathna" <dilshan@ics.mq.edu.au> wrote:

Hi,

I am trying build Xen with XSM enabled using xen-unstable.hg.

When I do:
# xm getpolicy
I get:
Supported security subsystems: None

It looks like it is creating all accessory directories, etc., but ACM doesn't
seems to be enabled.

Config.mk file  has:
# Enable XSM security module.  Enabling XSM requires selection of an
# XSM security module (FLASK_ENABLE or ACM_SECURITY).
XSM_ENABLE ?= y
FLASK_ENABLE ?= n
ACM_SECURITY ?= y

Build and install completes without errors. I also updated the unstable.hg
using 'hg pull -u', but no luck.
I've built 3.2.1 as well as 3.3.0 with ACM enabled and everything seems to be
OK.

Is there anything extra I should do with xen-unstable.hg?

OS: CentOS 5.2 (i386)

Regards,
Dilshan


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

--------------080205050206030200080203-- --===============1268265516== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============1268265516==--