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-users] Problem iscsi on domU

To: "Lino Moragon" <lino.moragon@xxxxxxxxxxxx>
Subject: Re: [Xen-users] Problem iscsi on domU
From: "Todd Deshane" <deshantm@xxxxxxxxx>
Date: Wed, 2 Jul 2008 15:40:58 -0400
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 02 Jul 2008 12:41:39 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :to:subject:cc:in-reply-to:mime-version:content-type:references; bh=ktmP0JVrpbhfQKu60WcQHNvw/edtZ2bb+91JGt6vJxw=; b=Il3FIt01Zh/A5zaTrwd6643QUknMF974ZM9mkIKUaWbVuU+WcABVqJSxmns38Hmqzb scbrpZT9tzO0ea6zMpfPjvSr84sA0QUA/L6mXMhLMSsI2E5nE1i3v2IKCLyaB6V7C4CA OclyO0WdEBXdp2Lfh6W/JWg92WzSa34u4t/a0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to :mime-version:content-type:references; b=vGP/LFUUrnPhTWtzNcoiMJH9xI73Osl0S0Y+CN1jU1eWQUehyM2AX0ApPEK4wR+RHV fE0qbdEREzFHBbF5+ZK4Mqsn2Bt7T6iDm7VAAGQA6BJPsU8K7mETZoLY5H/1+oEYRdnS 12Hwht3me8H6aNa4r48WeHhiwmEerUz1Uz4m8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <486B357E.9040404@xxxxxxxxxxxx>
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4868AB67.803@xxxxxxxxxxxx> <1e16a9ed0806302226m5cdada85qc73667f3eefe184@xxxxxxxxxxxxxx> <4869D078.4020202@xxxxxxxxxxxx> <1e16a9ed0807010957k5d99f61cgd49a7913dd9cb468@xxxxxxxxxxxxxx> <486B357E.9040404@xxxxxxxxxxxx>
Reply-to: deshantm@xxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

On Wed, Jul 2, 2008 at 3:59 AM, Lino Moragon <lino.moragon@xxxxxxxxxxxx> wrote:
Todd Deshane wrote:

On Tue, Jul 1, 2008 at 2:36 AM, Lino Moragon <lino.moragon@xxxxxxxxxxxx <mailto:lino.moragon@xxxxxxxxxxxx>> wrote:

   Todd Deshane wrote:

       On Mon, Jun 30, 2008 at 5:46 AM, Lino Moragon
       <lino.moragon@xxxxxxxxxxxx <mailto:lino.moragon@xxxxxxxxxxxx>
       <mailto:lino.moragon@xxxxxxxxxxxx>>> wrote:

          Hi list,

          I'm having troubles to get an iscsi initiator working on a
          As dom0 and domU I use a Centos 5 with the 2.6.18-53.1.14.el5
          As iscsi initiator i use the iscsi-initiator-utils of the
          The problem is, that when I log in to my iscsi target on
       the domU
          it is recognized as /dev/sda1.
          Now sda1 is also my root partition on the domU. And when I
          it I've mounted the root partition and not the iscsi device.

          Has anyone had this problem yet? Is there a solution to make it
          recognized as e.g. /dev/sdb ?

          Any help and tips would be appreciated.

       You should be able to setup a udev rule that will recognize
       the drives and correctly set them up.

       take a look here:


   Thanks for your response. I just tried it that way.
   Only problem is, that it creates a link that links to the same
   So if I mount the new /dev/iscsi_11 device it will mount again the
   root filesystem.
   Are there other possible options? Or isn't it at all possible?

Take a look at:
If I look at by-uuid i only get my "real" scsi device:
lrwxrwxrwx 1 root root 10 Jul  2 08:49 efd01d87-9b04-4d65-976c-cea045f51137 -> ../../sda1

Also for the by-id:
lrwxrwxrwx 1 root root 10 Jul  2 08:49 efd01d87-9b04-4d65-976c-cea045f51137 -> ../../sda1

And for the path there is my iscsi entry:
lrwxrwxrwx 1 root root 10 Jul  2 08:50 ip- -> ../../sda1

But it is also linked to sda1 ... Problem is that udev doesn't seem to create a "new" block device like sdb...

Any ideas?

Just to be clear, this is on the domU right?

The iSCSI device *should* show up as a new scsi device like you want (i.e sdb etc.).

If it is not that seems like a bug in the domU kernel. Try exporting the iSCSI device to another computer or guest with a different kernel.

This kind of thing should work, I haven't used it regularly for a couple years, but it worked pretty well then, so it should work even better now.


Todd Deshane
check out our book: runningxen.com
Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>