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-devel] Red Hat Cluster and Xen

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Red Hat Cluster and Xen
From: "David Shwatrz" <dshwatrz@xxxxxxxxx>
Date: Wed, 21 Mar 2007 16:59:11 +0200
Delivery-date: Wed, 21 Mar 2007 07:58:09 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=Esdq3MfyTFazRQTWyM5fuSNF02zjYkLQXWWQ5N8Nf03U8ZvLzLzKhGw+BXaOhP0A/sqBAiGxGjSB7AKgd/04sj7qSZipq+/BiK9fvGkDMAaHfsTXwgvNQPX56wPYFasOxB8WJIuAVS+pE+xT0Kcgur2OhxoNlBFJl3aJtimOiII=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=aNyUoNgOsKLJr/myL/6973CWlZQX/6Q4gdkqcedf8lWXawFBiBra8hZd8HJTst/TtXorTYUCQ7cVnRk3SFRTpkwohQaxwADmH77Z41HGCTAL9yZ1F1d2zTR5KN4/AQJqd194uwNJX2XRLSbtaL6sWuXJHsWAJJnE92M8cJ+3rKs=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hello all,

I had tried to build Red Hat Cluster (http://sourceware.org/cluster/) against  
a Xen tree in order to deploy a cluster with Xen VMs.
Under the ftp repository, ftp://sources.redhat.com/pub/cluster/releases,
there are some releases.
I started by trying to build the latest, which is: cluster-2.00.00.tar.gz.

I ran :
    ./configure --kernel_src=/work/src/xen-3.0.4_1-src/linux-

I get the following error :     
    /work/src/cluster-2.00.00/gnbd-kernel/src/gnbd.c: In function 'gnbd_init':
/work/src/cluster- 2.00.00/gnbd-kernel/src/gnbd.c:888: error: 'struct request'
  has no member named 'cmd_type'
It turns out that the struct request in
  /work/src/xen-3.0.4_1-src/linux- is missing
    a member named 'cmd_type' ; this member DOES exists in linux kernel 2.6.20 for example.
After probing a bit, I discovered that the problem is that this redhat cluster
    version is for kernel 2.6.20 (and higher) , and Xen
    (also unstable version, as far as I know) still does not work with this version.
    see the following thread:
    So I went a step back and tried cluster-1.03.00.
    (If you wonder why I skipped cluster-1.04 version, which does exists
    in that repository: the reason is simple ; If you will look at that thread
    mentioned above you will find out that also cluster-1.04 is intended for use with 2.6.20.)
    after "make install" I got:
    /work/src/cluster-1.03.00/gfs-kernel/src/nolock/main.c: In function 'nolock_plock_get':
/work/src/cluster-1.03.00/gfs-kernel/src/nolock/main.c:250: error: too many arguments to function 'posix_test_lock'

It turned out that the posix_test_lock() prototype in the linux kernel that Xen
uses is:
 struct file_lock *posix_test_lock(struct file *, struct file_lock *);
while the call to posix_test_lock() in gfs-kernel/src/nolock/main.c is with three

                    What should I do ? should I go again one step back (until reaching a
stop point for this recursion) ?

Any ideas ?


Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>