All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alvin Starr <alvin@iplink.net>
To: "Edwards, Nigel (Nigel Edwards)" <nigel.edwards@hp.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: iSCSI problems
Date: Mon, 31 Oct 2005 08:52:24 -0500	[thread overview]
Message-ID: <43662198.70101@Iplink.net> (raw)
In-Reply-To: <DF5E364A470421429AE6DC96979A4F6F28060A@sdcexc04.emea.cpqcorp.net>

Edwards, Nigel (Nigel Edwards) wrote:

>Hi,
>I am having problems getting iSCSI working with xen. I can access
>iSCSI drives fine from Xen0 (e.g. untar a 500MB archive and I don't
>see problems reported through dmesg or /proc/kmsg). However, if I try
>to project them into an instance of XenU as a scsi device to boot the
>unprivileged domain I get an oops in Xen0 - often resulting in the
>whole machine crashing.  This occurs in the very early stages of boot
>of xenU.
>
>I am using linux-iscsi-4.0.2 for iscsi_sfnet.ko
>scsi_transport_iscsi.ko is being built in linux-2.6.12-xen0
>I downloaded xen-unstable-src.tgz October 25th.
>
>I notice that there appear to be some significant differences between
>scsi_transport_iscsi.c in linux-iscsi-4.0.2 and the version in 
>linux-2.6.12 kernel.
>
>Example oops below. I have also attached the domain config file. I am
>not sure what to do next to get this working.  Any suggestions would
>be appreciated. If you have iSCSI working, if you could drop me a note
>indicating what code and modules you are using I would be very grateful.
>
>Cheers,
>Nigel.
>  
>
Having played with this I would suggest that you use iSCSI in Dom0 and 
export the disks from Dom0 to the varios DomU's.
I have managed to get this working with the aid of some hacks to the 
UDEV configuration files so that I can get a deivce entry like 
/dev/magical-iscsi-targetname.my.fun.domain.com.
It is then easy to map these things into the approprate DomU configs.

I would be concerned about using iSCSI in the DomU's because of the 
extra network overhead in propigating the data across the bridge.

-- 
Alvin Starr                   ||   voice: (416)585-9971
Interlink Connectivity        ||   fax:   (416)585-9974
alvin@iplink.net              ||

  reply	other threads:[~2005-10-31 13:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-31 11:12 iSCSI problems Edwards, Nigel (Nigel Edwards)
2005-10-31 13:52 ` Alvin Starr [this message]
2005-10-31 14:57 ` Brian Wolfe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43662198.70101@Iplink.net \
    --to=alvin@iplink.net \
    --cc=nigel.edwards@hp.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.