Re: [Xen-devel] ACM not enabled with xen-unstable

["George S. Coker, II" <gscoker@xxxxxxxxxxxxxx>]

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@xxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel


-- 
George S. Coker, II <gscoker@xxxxxxxxxxxxxx>



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