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

[Xen-users] kernel panic with iSCSI

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] kernel panic with iSCSI
From: Michael Jinks <mjinks@xxxxxxxxxxxx>
Date: Sun, 18 Jan 2009 12:50:56 -0600
Delivery-date: Sun, 18 Jan 2009 10:53:23 -0800
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/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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.16 (2007-06-09)
I'm trying to get an iSCSI connection going, with a Linux domU
initiating to an OpenSolaris target.  Discovery works fine, but so far
every attempt to log in to my test target has caused a kernel panic.

Am I just naive?  Is there some reason this shouldn't work, like a
conflict between the iSCSI code and the Xen domU patches?  Is anybody
else successfully running an iSCSI initiator from within a Linux domU?

If this should work, then I think I need to take my question to the
iSCSI folks next since it's their code throwing the panic, but first I
wanted to rule out the possibility that I'm trying to do something known
not to work in Xen.

Thanks,
--Michael

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

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