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


Re: [Xen-devel] Remus blktap2 issue

To: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-devel] Remus blktap2 issue
From: Shriram Rajagopalan <rshriram@xxxxxxxxx>
Date: Wed, 8 Sep 2010 01:50:50 -0700
Cc: Xen-devel@xxxxxxxxxxxxxxxxxxx, Jonathan Kirsch <kirsch.jonathan@xxxxxxxxx>
Delivery-date: Wed, 08 Sep 2010 01:51:37 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=6IxTUqU06NV05Tzx6EIDpH+Z4zg324tzNxp3spRRbjg=; b=rNH0qJ/NfTEEu315pwX3Nmqe0FuKxG7Yj/OuXq1mMA2PYd85dA4fPy3YVSyNoBIM7L 5GWC6AjvFF9JoAx0b3mC8o1dUrsGvzBiiVDUp1Pajkj+keZUw35wxLkPU9BhRFOqieEh oF7EMQzyqVtjxIR73JeRqliU5Noc9KWsnIbNo=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=nZ7354dqbN86+5RWGdpm+bLh6usGuqUw2cQo27jWcnJaANT52gmhfvQ2iJBMVRnaql uriUmeFI6agOmLW9aqQvB+LeYpaEWVIJVHM7T7axvfkhu7GaAf+ArMIy22cd6OkiaMaT 3is3udg6PrRVZVd7LAJOzTev1/9n/16xWR9dg=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100908060101.GE2804@xxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTinCyWjaSwGQT7bWL7=tkF_xQe3ABeosAusr+mjg@xxxxxxxxxxxxxx> <20100908060101.GE2804@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Its not just the tap2:remus:....

there is a bug lurking in the in tools/python/xen/remus/device.py in ReplicatedDisk class. The regular _expression_ scans the domU config for only tap:tapdisk:remus... or tap:remus.. disk types only. I was able to get it working by fixing that regexp.
This applies for xen 4.0.1 only. Am not sure about xen unstable.
 Here is a patch that might be of help to you (its rather crude but heck I was too lazy :) )
diff -r b536ebfba183 tools/python/xen/remus/device.py
--- a/tools/python/xen/remus/device.py  Wed Aug 25 09:22:42 2010 +0100
+++ b/tools/python/xen/remus/device.py  Fri Sep 03 08:47:13 2010 -0700
@@ -36,10 +36,13 @@
         # to request commits.
         self.ctlfd = None
-        if not disk.uname.startswith('tap:remus:') and not disk.uname.startswith('tap:tapdisk:remus:'):
+        if not disk.uname.startswith('tap2:remus:') and not disk.uname.startswith('tap:remus:') and not disk.uname.startswith('tap:tapdisk:remus:'):
             raise ReplicatedDiskException('Disk is not replicated: %s' %
-        fifo = re.match("tap:.*(remus.*)\|", disk.uname).group(1).replace(':', '_')
+        if disk.uname.startswith('tap2:remus:'):           
+            fifo = re.match("tap2:.*(remus.*)\|", disk.uname).group(1).replace(':', '_')
+        else:
+            fifo = re.match("tap:.*(remus.*)\|", disk.uname).group(1).replace(':', '_')
         absfifo = os.path.join(self.FIFODIR, fifo)
         absmsgfifo = absfifo + '.msg'

On Tue, Sep 7, 2010 at 11:01 PM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
On Tue, Sep 07, 2010 at 03:28:32PM -0700, Jonathan Kirsch wrote:
>    Hello,
>    I have been playing around with Remus on Xen 4.0.1, attempting to
>    fail-over for an HVM domU.
>    I've run into some problems that I think could be related to tapdisk2 and
>    its interaction with how one sets up Remus disk replication in the domU
>    config file.
>    A few things I've noticed:
>    -The tap:remus:backupHostIP:port|aio:imagePath notation does not work for
>    me, although this is what is written in the Remus documentation.  However,
>    I have found the following to work (i.e., not complain when starting
>    domU), so this is what I've been using:
>    tap2:remus:backupHostIP:port|aio:imagePath...

Yeah, this stuff was changed in Xen 4.0.1:

I guess someone should update the remus wiki page.

-- Pasi

Xen-devel mailing list

perception is but an offspring of its own self
Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>