WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: Dilshan Jayarathna <dilshan@xxxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] ACM not enabled with xen-unstable
From: "George S. Coker, II" <gscoker@xxxxxxxxxxxxxx>
Date: Thu, 25 Sep 2008 13:12:46 -0400
Cc:
Delivery-date: Thu, 25 Sep 2008 10:15:32 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <48DADBB5.7010005@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AckfMe3IH5viBzgiTEKM10r0oDHE1A==
Thread-topic: [Xen-devel] ACM not enabled with xen-unstable
User-agent: Microsoft-Entourage/12.12.0.080729

While I do maintain XSM and XSM/FLASK, I’m not that familiar with XSM/ACM.  I don’t believe any significant
ACM patches have been committed to -unstable since the 3.3 release.  The issue that you uncovered is due to
a recent patch to –unstable, 3.3 is unaffected.


On 9/24/08 8:30 PM, "Dilshan Jayarathna" <dilshan@xxxxxxxxxxxxx> wrote:

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@xxxxxxxxxxxxx> <mailto: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
    
 



  


_______________________________________________
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
<Prev in Thread] Current Thread [Next in Thread>