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-users

[Xen-users] ACM errors -- CentOS 5.2 and Xen 3.2.1 incompatibility?

To: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] ACM errors -- CentOS 5.2 and Xen 3.2.1 incompatibility?
From: "Nadolski, Ed" <Ed.Nadolski@xxxxxxx>
Date: Tue, 12 Aug 2008 10:46:12 -0600
Accept-language: en-US
Acceptlanguage: en-US
Delivery-date: Tue, 12 Aug 2008 09:49:01 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acj8mu4YIOCb9CImQFigjKAbZZI+SQ==
Thread-topic: ACM errors -- CentOS 5.2 and Xen 3.2.1 incompatibility?
Has anyone seen the following errors on CentOS 5.2 with Xen 3.2.1:

# xm list
ACMError: Policy file '/etc/xen/acm-security/policies/-security_policy.xml' not 
found.
# xm dmesg
Error: (13, 'Permission denied')


I get these every time I do the following:

1. Default install of CentOS 5.2 on Intel DQ35 motherboard system
2. Install mercurial
3. Download xen-3.2.1.tar.gz from xen.org and untar.
4. make world (fails when it can't find linux-2.6.18-xen.hg)
5. hg clone http://xenbits.xensource.com/linux-2.6.18-xen.hg
6. make all (succeeds)
7. make install (succeeds)
8. depmod & mkinitrd
9. edit grub.conf and reboot new Xen kernel

After reboot, I then run "xm list" and "xm dmesg" which used to work but now 
give the above error.

Evidently it doesn't like my security policy and more -- any thoughts/ideas on 
why?   Is this a known bug or incompatibility? Is my build/config wrong?

Thanks,
Ed Nadolski
LSI




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

<Prev in Thread] Current Thread [Next in Thread>