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

Re: [Xen-devel] Trying to track down odd behavior, errors in xen dmesg

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] Trying to track down odd behavior, errors in xen dmesg
From: Keith Swett <swettk@xxxxxxxxx>
Date: Tue, 12 Apr 2011 18:02:43 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 12 Apr 2011 16:03:56 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=lmSFTjcWkjQKwB3bPrFCBsPPFx2VLk6DvuX/HS+M5ks=; b=e0zwJQO+uc1ACUt7eGEauSYFLuGppwBUsvWpLuCLayyrj9wmTOyEJx81cqUUkpFDRT v46yRz8VdRkUypgKQyxs/NBlO6qgLKoCOFt5qJ4nIuDsLaLomxcYf/4xts8AaBWYR6cO prWcHsPXgaKshVJ6RHvl5LIKHanJErxDqq7FM=
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=aZYKOVhPLN6BCu9GJqsGVLOXBGgRpmf0y2MONSP7giyEdOkqkrhqVCuGDNslo37DF+ zgkhBOdxgwoldvL5Tmvylv011/PcrLAUTn/PKKVSzxu2q2eVxrP5DqR9C0xM7JXuVuLF gEvHwKcAo29qlVM3iuRtBm7yQWWkjA6hAOMYE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110412224840.GA9512@xxxxxxxxxxxx>
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: <BANLkTim_Khsw=KCvHFqg1mzwQGtayQLRpQ@xxxxxxxxxxxxxx> <BANLkTi==g14Na0XCBAC0zqOZ_xFU16YSCQ@xxxxxxxxxxxxxx> <20110408135337.GG6189@xxxxxxxxxxxx> <BANLkTinJ4eu6TFhTujbdW_JUJ_4ZVQ3hQQ@xxxxxxxxxxxxxx> <20110412102002.GA30108@xxxxxxxxxxxx> <BANLkTi=p3h7jyxpZhkbect25tPngFf5Xiw@xxxxxxxxxxxxxx> <20110412204123.GA7308@xxxxxxxxxxxx> <BANLkTikiWVXgvANu2RAph6m5T5i4_aE7Hw@xxxxxxxxxxxxxx> <20110412210810.GB21002@xxxxxxxxxxxx> <BANLkTikYWd4KU4dP2FBjFhZOLzkdgKjEDw@xxxxxxxxxxxxxx> <20110412224840.GA9512@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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

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