WARNING - OLD ARCHIVES

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

xen-users

Re: [Xen-users] Xen and iSCSI

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Xen and iSCSI
From: Datto <datto@xxxxxxxxxxx>
Date: Sat, 28 Jan 2006 10:24:44 -0800
Cc: gledesma@xxxxxxxxx
Delivery-date: Sat, 28 Jan 2006 18:34:15 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Sensitivity: Normal
>> Using CentOS 4.2 (which came with a cleanly packaged
>> iscsi-initiator-tools) I've gotten it to work and I find the
>> performance preferrable to NFS Root.

How did you get past the "FATAL: module iscsi_sfnet not found." error when 
starting up the iscsi initiator on CentOS 4.2? That's stopping me from getting 
the iscsi initiator to work on CentOS 4.2. Evidently the iscsi_sfnet module 
doesn't exist on my CentOS 4.2 system after I installed the 
iscsi-initiator-utils RPM from the CentOS 4.2 CD media.

Thanks for your help.

Datto

----------------
Using CentOS 4.2 (which came with a cleanly packaged
iscsi-initiator-tools) I've gotten it to work and I find the
performance preferrable to NFS Root. I still haven't gotten the hang
of booting using iSCSI Root over the network, but it should just be a
couple more adjustments to the initrd.

Currently, I have dom0 serve as the iSCSI initiator and then have the
domUs use the block devices. Some limitations I've run into:
- I can't manage to get the iSCSI initiator to see changes to the
exported LUNs (e.g. block device has been grown, or see more LUNs)
- For multiple LUNs from different iSCSI Targets, establish a fixed
order/names for the block devices

Other than that, you shouldn't have too much problems with it. :-)

- gino ledesma

On 1/28/06, Markus Hochholdinger <Markus@xxxxxxxxxxxxxxxxx> wrote:
> hi,
>
> has anyone experience with the use of iscsi (as iscsi initiator) in Xen (which
> Xen version?). Does it work in dom0 and domU?
>
> Does it work (good)? Or are there any problems (besides the normal linux
> problems with iscsi)? How is the performance in domU?
>
> Background is that i am planing virtual servers within xen and they should get
> their disks from the network so that i can perform live migration.
> Has anyone a setup like this working?
>
>
> --
> greetings
>
> eMHa
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>
>
>

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>