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

Re: [Xen-users] Xen domU's and iscsi initaitor problems.

  • To: "Ryan Kish" <rpkish@xxxxxxxxx>
  • From: "Jerry Amundson" <jamundso@xxxxxxxxx>
  • Date: Wed, 21 Feb 2007 14:53:28 -0600
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 21 Feb 2007 12:52:56 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=QHhruVbZAbJ4Mc83sUSwB3ZYdOTxKwCkIqktSFveAayfZLXoD6RPqWpTIi/6lsgjQ5BFUGY8QSMEV6JfgaXav4L5YQPOzDI+Uvc4gOaCGFYdkgmUfp5otyeSHNQQ8fqStybbGs62vG5qNjEuibTuV/l78NHffExcipAoT5QaZew=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On 2/21/07, Ryan Kish <rpkish@xxxxxxxxx> wrote:
Hello, I have been using Xen now for several months and have been
quite successful until attempting to utilize iscsi within my domU's.

Not surprising....
Didn't most of the iscsi usage you found involve dom0?

My research has turned up many posts of people using iscsi with no
problems, and I have found no others with the problem I seem to be
experiencing. If this has been covered on this list in the past,
please accept my humble apologies.

Accepted. :-)

(note: most of my configuration is based on the iscsi-xen howto at

Right - the dom0's are iscsi initiators...
Theorizing here, but it's possible that the CPU and network overhead
in dom0 is not conducive to putting iscsi, which itself is CPU and
network overhead, within the domU.


"Pay no attention to that man behind the curtain!"

Xen-users mailing list



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