From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keith Swett <swettk@gmail.com>
Subject: Re: Trying to track down odd behavior, errors in xen dmesg
Date: Tue, 12 Apr 2011 18:02:43 -0500
Message-ID: <BANLkTi=DEXmLeWPOk3Scny-6jTGW7sjJGQ@mail.gmail.com>
References: <BANLkTim_Khsw=KCvHFqg1mzwQGtayQLRpQ@mail.gmail.com>
	<BANLkTi==g14Na0XCBAC0zqOZ_xFU16YSCQ@mail.gmail.com>
	<20110408135337.GG6189@dumpdata.com>
	<BANLkTinJ4eu6TFhTujbdW_JUJ_4ZVQ3hQQ@mail.gmail.com>
	<20110412102002.GA30108@dumpdata.com>
	<BANLkTi=p3h7jyxpZhkbect25tPngFf5Xiw@mail.gmail.com>
	<20110412204123.GA7308@dumpdata.com>
	<BANLkTikiWVXgvANu2RAph6m5T5i4_aE7Hw@mail.gmail.com>
	<20110412210810.GB21002@dumpdata.com>
	<BANLkTikYWd4KU4dP2FBjFhZOLzkdgKjEDw@mail.gmail.com>
	<20110412224840.GA9512@dumpdata.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20110412224840.GA9512@dumpdata.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

Konrad,

> Please don't top-post.
Sorry.

I did comment out the line (I didn't see the duration variable
declared anywhere)
and rebuilt and re-tested.  It appears to have the same error.  I
found the problem with this morning's testing.  The error occurs when
I place the VM running the iSCSI target on the same physical machine
that is running the initiator (this may seem backwards but it's for a
DRBD/Pacemaker fail-over)  Is this just an unsupported configuration?

--Keith