[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
  • 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
  • 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=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.