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/
Home Products Support Community News


RE: [Xen-devel] iscsi patch

To: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] iscsi patch
From: James Harper <JamesH@xxxxxxxxxxxxxxxx>
Date: Tue, 24 Aug 2004 23:28:20 +1000
Cc: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 24 Aug 2004 14:37:14 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: <E1BzbAr-0002Oo-00@xxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <E1BzbAr-0002Oo-00@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Thread-index: AcSJ3jjwzs02ojXcTmu3VmDsf7UG1Q==
Thread-topic: [Xen-devel] iscsi patch
i've got busybox in my initrd so right at the end i dump out to a shell. i bring up the network with an ifconfig in my init script and can ping the network.
there must be something in /dev or something somewhere that i'm missing that makes these ioctls not work under the stripped down environment of initrd.
i'll try an strace and see what happens.

From: Ian Pratt
Sent: Tue 24/08/2004 11:17 PM
To: James Harper
Cc: Ian Pratt; xen-devel@xxxxxxxxxxxxxxxxxxxxx; Ian.Pratt@xxxxxxxxxxxx
Subject: Re: [Xen-devel] iscsi patch

> iscsi-boot appears to try and bring up the network interface and give it an address and route. unfortunately it says this instead (under an initrd environment):
> iSCSI: error in getting interface name
> : No such device
> iSCSI: Error in bringing up the network interface

Are you sure you're bringing up the network interface before
trying to start iscsi-boot? Put an 'ifconfig eth0' in your

(You need to enable CONFIG_IP_PNP if you want to set the ip
address on the command line)

> when I try to run iscsid under initrd it says 
> all isc1093350010.49159 >> iscsid[97]: iSCSI session ioctl failed for <snip>, Can not allocate memory: Cannot allocate memory
> any ideas? something is obviously different about initrd but i can't put my finger on what. it's starting to drive me crazy!

I'd get strace on your initrd and start both commands under

Are you sure you've got the scsi, sd and iscsi_sfnet modules all
loaded OK? (stick cat /proc/modules in your initrd).

To make life easy for myself I've often got initrd's working
using bash before switching to nash to save memory. ldd will tell
you what libraries you need to copy across.