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/
Home Products Support Community News


[Xen-bugs] [Bug 1429] New: XSM-ACM module not working on Xen 3.3.1

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1429] New: XSM-ACM module not working on Xen 3.3.1
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 12 Mar 2009 15:11:17 -0700
Delivery-date: Thu, 12 Mar 2009 15:11:23 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

           Summary: XSM-ACM module not working on Xen 3.3.1
           Product: Xen
           Version: 3.0 (general)
          Platform: x86-64
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Tools
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: amazab@xxxxxxxx

I followed the manual to initialize XSM-ACM module on Xen3.3.1-64 bit. However,
whenever I used "xm get policy". Xen tools could not detect the DEFAULT policy
installed and reports it as "None". Of course, this affects all other ACM
functions like setpolicy, resetpolicy, etc...

I traced the code, I found that the default ACM policy starts correctly inside
then however, the problem is in the file "tools/python/xen/lowlevel/acm/acm.c".
Function "__getssid", which is supposed to get the domain's SSID and hence
determine the used policy erases the retrieved buffer in the case of success.
The faulty lines are number 70 & 71 (in Version 3.3.1). If the return is Null,
the calling function will assume that no policy is installed and hence disable
any further ACM operations!

The if condition is as follows:

    if (xc_acm_op(xc_handle, ACMOP_getssid, &getssid, sizeof(getssid)) < 0) {
        if (errno == EACCES)
            PERROR("ACM operation failed.");
        buf = NULL;
        goto out2;
    } else {
        *buflen = SSID_BUFFER_SIZE;
        buf = NULL;
        goto out2;

In the case of an "else" the two lines 
        buf = NULL;
Should be omitted!!


Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 1429] New: XSM-ACM module not working on Xen 3.3.1, bugzilla-daemon <=