From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Trying to track down odd behavior, errors in xen dmesg Date: Wed, 13 Apr 2011 09:05:32 -0400 Message-ID: <20110413130532.GA9500@dumpdata.com> References: <20110408135337.GG6189@dumpdata.com> <20110412102002.GA30108@dumpdata.com> <20110412204123.GA7308@dumpdata.com> <20110412210810.GB21002@dumpdata.com> <20110412224840.GA9512@dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keith Swett Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Tue, Apr 12, 2011 at 06:02:43PM -0500, Keith Swett wrote: > 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 OK, were there are any other errors? > 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 Oh wow. iSCSI target and iSCSI initiator on the same box and then DRBD on top? Whoa. > DRBD/Pacemaker fail-over) Is this just an unsupported configuration? IT is an odd configuration. > > --Keith > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel