| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: Loop and ENBD device management (was Re: [Xen-devel] Automation scri
> > This should already be useful, at least for file-based disks. It'd be
> > nice to
> > have the ENBD script working and have some kind of iSCSI script at
> some
> > stage.
>
> For iSCSI, have a look at iscsi-init at sourceforge.
> http://iscsi-init.sourceforge.net. Load it as a module in an initrd and
> it uses some kernel parameters and automatically configures the network
> and then connects to the designated target.
I've found iscsi-init very useful. I've created in an initrd that
loads it and the iscsi_sfnet module, and am then able to pass in
the initiator and target name on the kernel command line.
A couple of things to watch out for:
* If you're using 2.4, it's necessary to hack the iscsi code such
that ENABLE_CLUSTERING is changed to DISABLE_CLUSTERING
* you need to enable CONFIG_VLAN_8021Q=y to get iscsi-init to work.
> Just on the topic of iSCSI though, linux-iscsi 4.0.1.8 + iscsitarget
> (sourceforge project names) causes corruption for me. 4.0.1.9 doesn't
> but then iscsi-init doesn't work for that yet.
I use a hardware target. There's three different linux iscsi
target implementations, and they're all lacking in one way or
another.
Ian
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
|
|
|
| |
|
Home