From: Dilshan Jayarathna <dilshan@ics.mq.edu.au>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: ACM not enabled with xen-unstable
Date: Thu, 25 Sep 2008 10:30:45 +1000 [thread overview]
Message-ID: <48DADBB5.7010005@ics.mq.edu.au> (raw)
In-Reply-To: <C500140E.2096A%gscoker@alpha.ncsc.mil>
[-- Attachment #1.1: Type: text/plain, Size: 1850 bytes --]
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
>>
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 2426 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2008-09-25 0:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 0:00 ACM not enabled with xen-unstable Dilshan Jayarathna
2008-09-24 19:58 ` George S. Coker, II
2008-09-25 0:30 ` Dilshan Jayarathna [this message]
2008-09-25 17:12 ` George S. Coker, II
2008-09-25 23:35 ` Dilshan Jayarathna
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=48DADBB5.7010005@ics.mq.edu.au \
--to=dilshan@ics.mq.edu.au \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.