Re: [Xen-devel] Loading ACM policy in XSM

[Syunsuke HAYASHI <syunsuke@jp.fujitsu.com>]

Hi, Stefan.

I tested as you said.

■"Module/example.client_b1.bin" is written in grub.conf
-----------------------------------------------------------------------
# xm list --label
Name                                ID   Mem VCPUs      State   Time(s) 
Label
Domain-0                             0  1024     4     r-----     47.7 
unlabeled

# xm getpolicy
Error: xm needs to be configured to use the xen-api.
Usage: xm getpolicy [options]

Get the policy of the system.

     Usage: xm getpolicy [options]

     The following options are defined
       --dumpxml     Display the XML of the policy

     Get the policy managed by xend.
-----------------------------------------------------------------------

■"Module/example.client_b1.bin" is not written in grub.conf
-----------------------------------------------------------------------
#xm list --label
Name                                ID   Mem VCPUs      State   Time(s) 
Label
Domain-0                             0  1024     4     r-----     46.5 
  DEFAULT

#xm getpolicy
Error: xm needs to be configured to use the xen-api.
Usage: xm getpolicy [options]

Get the policy of the system.

     Usage: xm getpolicy [options]

     The following options are defined
       --dumpxml     Display the XML of the policy

     Get the policy managed by xend.

-----------------------------------------------------------------------
Is it good in this?

Thanks,

Syunsuke HAYASHI
> 
> Syunsuke HAYASHI <syunsuke@jp.fujitsu.com> wrote on 08/28/2007 09:20:44 PM:
> 
>  > Hi,Stefan
>  > Thank you for the help.
>  >
>  > I was not describing an ssidref=... in grub.conf.
>  > I show grub.conf and dmesg when I execute "xm chgpolicy
>  > example.client_v1" command and reboot.
>  >
>  > 
> ----------------------------grub.conf--------------------------------------
>  > # grub.conf generated by anaconda
>  >    module /example.client_v1.bin
> 
> looks good
>  >
>  >
>  > 
> -----------------------------dmesg----------------------------------------
>  >   __  __            _____  ___                     _        _     _
> [...]
>  > (XEN) Brought up 4 CPUs
>  > (XEN) Policy len  0x168, start at 3ffff000 - module 2.
>  > (XEN) acm_set_policy_reference: Activating policy example.client_v1
>  > (XEN) acm_init: Enforcing CHINESE WALL AND SIMPLE TYPE ENFORCEMENT boot
>  > policy.
> 
> So at this point the policy is loaded.
> What does 'xm getpolicy' show?
> 
> You seem to have XSM as a patch applied to Xen - what happens if you do 
> this without XSM applied?
> 
>    Stefan
> 
>  > [...]
>  > Is it good in this ?
>  >
>  > Syunsuke HAYASHI
>  > >
>  > > xen-devel-bounces@lists.xensource.com wrote on 08/27/2007 04:00:14 AM:
>  > >
>  > >  > Hi,
>  > >  > I have a problem about ACM module(hg.15730)
>  > >  > I want to label Domain-0.
>  > >  > I read xen user's manual v3.0 and "man xm" information.
>  > >  > ACM document mentions how to label Domain-0.
>  > >  > But I couldn't add the label when I tried the following steps.
>  > >  >
>  > >  >    (test1)
>  > >  >    #xm makepolicy example.client_v1
>  > >  >    #xm cfgbootpolicy example.client_v1
>  > >  >    #reboot
>  > >  >
>  > >  >    (test2)
>  > >  >    #xm setpolicy ACM example.client_v1
>  > >  >    #xm activatepolicy --boot
>  > >  >
>  > >  >    (result)
>  > >  >    [root@bx607 ~]# xm list --label
>  > >  >    Name     ID  Mem    VCPUs    State   Time(s) Label
>  > >  >    Domain-0  0  1024     4     r-----    105.1 unlabeled
>  > >  >
>  > >  > So,I tried to use "xm addlabel" command.
>  > >  >
>  > >  >    #xm makepolicy example.client_v1
>  > >  >    #xm addlabel dom_SystemManagement mgt Domain-0 example.client_v1
>  > >  >
>  > >  > But I couldn't again.
>  > >  >
>  > >  > Is there any good idea ?
>  > >
>  > > Is there an ssidref=... in the 'kernel' line in the grub title you are
>  > > booting? Can you send this line and remove the ssidref=... and try 
> again?
>  > > Otherwise if this is not the case, can you send the content of 'xm 
> dmesg'?
>  > >
>  > >    Stefan
>  > >  >
>  > >  > Thanks,
>  > >  >
>  > >  > Syunsuke HAYASHI
>  > >  >
>  > >  >
>  > >  >
>  > >  >
>  > >  > _______________________________________________
>  > >  > Xen-devel mailing list
>  > >  > Xen-devel@lists.xensource.com
>  > >  > http://lists.xensource.com/xen-devel
>  >