From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nathan Lutchansky Subject: Xen and iscsitarget Date: Thu, 4 Nov 2004 13:22:51 -0500 Message-ID: <20041104182251.GA11808@litech.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uAKRQypu60I7Lcqm" Return-path: Content-Disposition: inline Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: xen-devel@lists.sourceforge.net List-Id: xen-devel@lists.xenproject.org --uAKRQypu60I7Lcqm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi all, I've been using Xen for a few months now and I'm quite impressed. Not only is the virtualization platform stable and well-designed, but the surrounding administrative tools and processes are usable and complete. (Although I admit, I was kind of disappointed with the performance until I realized recently that I hadn't compiled support for my ATA chipset into the dom0 kernel and all disk I/O was PIO.) My problem is that I'm unable to get the Cisco linux-iscsi initiator=20 running under Xen. It seems other people have been able to do this so=20 maybe I'm doing something wrong. I'm running the Xen 2.0 release candidate (which, BTW, is very nice=20 otherwise, I've had no other problems) and have iscsitarget 0.3.4 running= =20 on an external host. The iscsitarget has been working fine with non-Xen=20 hosts. Unfortunately, I'm unable to get unprivileged domains to talk to the=20 iscsitarget. Using Linux 2.4.27-xenU with linux-iscsi 3.6.2 I get the=20 error "xmit_data failed to send 8240 bytes, rc 48", and using Linux=20 2.6.9-xenU with linux-iscsi 4.0.1.10 it simply locks up the whole kernel=20 on session initiation. (Pings still work though.) In domain 0, I can use linux-iscsi-4.0.1.10 to talk to the target=20 successfully, however, under load I will often get syslog messages=20 "iscsi-tx: page allocation failure. order:0, mode:0x20" and a big call=20 trace (see below). These apparently cause no real problems though, and=20 all my data seems to be intact and the filesystem works fine. Domain: Kernel: Linux-iscsi: Result: unpriv 2.4.27-xenU 3.6.2 "xmit_data failed" unpriv 2.6.9-xenU 4.0.1.10 immediate lock-up domain 0 2.6.9-xen0 4.0.1.10 works fine, with strange errs The lock-up with 2.6.9 happens after less than a kilobyte of data has been= =20 transmitted in either direction. My unprivileged domains otherwise work fine and I've pumped many=20 gigabytes of data between them and the network. Since this only breaks from an unprivileged domain, I'm guessing that=20 there's some incompatibility between how VIFs are implemented and how=20 linux-iscsi wants to use them. Can anybody suggest kernel and linux-iscsi versions that seem to work=20 correctly? -Nathan Using Linux 2.4.27-xenU with linux-iscsi 3.6.2: Nov 4 12:39:56 iscsi-test kernel: iSCSI: session c0724000 xmit_data=20 failed to send 8240 bytes, rc 48 Nov 4 12:39:56 iscsi-test kernel: iSCSI: session c0724000 to=20 iqn.1998-07.org.litech.daily-post:storage.test.loop0 dropped Nov 4 12:39:56 iscsi-test kernel: iSCSI: session c0724000 to=20 iqn.1998-07.org.litech.daily-post:storage.test.loop0 waiting 2 seconds=20 before next login attempt Nov 4 12:39:58 iscsi-test kernel: iSCSI: bus 0 target 2 trying to=20 establish session c0724000 to portal 0, address 192.168.16.24 port 3260=20 group 1 Nov 4 12:39:58 iscsi-test kernel: iSCSI: session c0724000 login=20 negotiation failed, can't accept =3DNotUnderstood in security stage Nov 4 12:39:58 iscsi-test kernel: iSCSI: session c0724000 may be in use,= =20 retrying login to portal 0 at 35927 Nov 4 12:39:58 iscsi-test kernel: iSCSI: session c0724000 to=20 iqn.1998-07.org.litech.daily-post:storage.test.loop0 waiting 1 seconds=20 before next login attempt Using Linux 2.6.9-xen0 with linux-iscsi 4.0.1.10: Nov 4 13:15:13 faboo kernel: iscsi-tx: page allocation failure. order:0,= =20 mode:0x20 Nov 4 13:15:13 faboo kernel: [__alloc_pages+447/880] __alloc_pages+0x1bf/0x370 Nov 4 13:15:13 faboo kernel: []=20 __alloc_pages+0x1bf/0x370 Nov 4 13:15:13 faboo kernel: Nov 4 13:15:13 faboo kernel: [__get_free_pages+31/64]=20 __get_free_pages+0x1f/0x40 Nov 4 13:15:13 faboo kernel: [] __get_free_pages+0x1f/0x40 Nov 4 13:15:13 faboo kernel: Nov 4 13:15:13 faboo kernel: [kmem_getpages+34/224]=20 kmem_getpages+0x22/0xe0 Nov 4 13:15:13 faboo kernel: [] kmem_getpages+0x22/0xe0 Nov 4 13:15:13 faboo kernel: Nov 4 13:15:13 faboo kernel: [cache_grow+187/400] cache_grow+0xbb/0x190 Nov 4 13:15:13 faboo kernel: [] cache_grow+0xbb/0x190 Nov 4 13:15:13 faboo kernel: Nov 4 13:15:13 faboo kernel: [cache_alloc_refill+223/560]=20 cache_alloc_refill+0xdf/0x230 Nov 4 13:15:13 faboo kernel: [] cache_alloc_refill+0xdf/0x230 Nov 4 13:15:13 faboo kernel: Nov 4 13:15:13 faboo kernel: [__kmalloc+141/160] __kmalloc+0x8d/0xa0 Nov 4 13:15:13 faboo kernel: [] __kmalloc+0x8d/0xa0 Nov 4 13:15:13 faboo kernel: Nov 4 13:15:13 faboo kernel: [alloc_skb+71/224] alloc_skb+0x47/0xe0 Nov 4 13:15:13 faboo kernel: [] alloc_skb+0x47/0xe0 Nov 4 13:15:13 faboo kernel: Nov 4 13:15:13 faboo kernel: [tcp_sendmsg+4076/4528]=20 tcp_sendmsg+0xfec/0x11b0 Nov 4 13:15:13 faboo kernel: [] tcp_sendmsg+0xfec/0x11b0 Nov 4 13:15:13 faboo kernel: Nov 4 13:15:13 faboo kernel: [cache_alloc_refill+223/560]=20 cache_alloc_refill+0xdf/0x230 Nov 4 13:15:13 faboo kernel: [] cache_alloc_refill+0xdf/0x230 Nov 4 13:15:13 faboo kernel: Nov 4 13:15:13 faboo kernel: [inet_sendmsg+77/96] inet_sendmsg+0x4d/0x60 Nov 4 13:15:13 faboo kernel: [] inet_sendmsg+0x4d/0x60 Nov 4 13:15:13 faboo kernel: Nov 4 13:15:13 faboo kernel: [sock_sendmsg+229/256]=20 sock_sendmsg+0xe5/0x100 Nov 4 13:15:13 faboo kernel: [] sock_sendmsg+0xe5/0x100 Nov 4 13:15:13 faboo kernel: Nov 4 13:15:13 faboo kernel: [ip_rcv_finish+0/656]=20 ip_rcv_finish+0x0/0x290 Nov 4 13:15:13 faboo kernel: [] ip_rcv_finish+0x0/0x290 Nov 4 13:15:13 faboo kernel: Nov 4 13:15:13 faboo kernel: [inet_sendmsg+77/96] inet_sendmsg+0x4d/0x60 Nov 4 13:15:13 faboo kernel: [] inet_sendmsg+0x4d/0x60 Nov 4 13:15:13 faboo kernel: Nov 4 13:15:13 faboo kernel: [sock_sendmsg+229/256]=20 sock_sendmsg+0xe5/0x100 Nov 4 13:15:13 faboo kernel: [] sock_sendmsg+0xe5/0x100 Nov 4 13:15:13 faboo kernel: Nov 4 13:15:13 faboo kernel: [autoremove_wake_function+0/96]=20 autoremove_wake_function+0x0/0x60 Nov 4 13:15:13 faboo kernel: []=20 autoremove_wake_function+0x0/0x60 Nov 4 13:15:13 faboo kernel: Nov 4 13:15:13 faboo kernel: [kernel_sendmsg+70/96]=20 kernel_sendmsg+0x46/0x60 Nov 4 13:15:13 faboo kernel: [] kernel_sendmsg+0x46/0x60 Nov 4 13:15:13 faboo kernel: Nov 4 13:15:13 faboo kernel: [sock_no_sendpage+138/144]=20 sock_no_sendpage+0x8a/0x90 Nov 4 13:15:13 faboo kernel: [] sock_no_sendpage+0x8a/0x90 Nov 4 13:15:13 faboo kernel: Nov 4 13:15:13 faboo kernel: [tcp_sendpage+81/160]=20 tcp_sendpage+0x51/0xa0 Nov 4 13:15:13 faboo kernel: [] tcp_sendpage+0x51/0xa0 Nov 4 13:15:13 faboo kernel: Nov 4 13:15:13 faboo kernel: [pg0+143619158/1002090496]=20 iscsi_sendpage+0xc6/0x100 [iscsi_sfnet] Nov 4 13:15:13 faboo kernel: [] iscsi_sendpage+0xc6/0x100=20 [iscsi_sfnet] Nov 4 13:15:13 faboo kernel: Nov 4 13:15:13 faboo kernel: [pg0+143637917/1002090496]=20 iscsi_xmit_data+0x66d/0xbb0 [iscsi_sfnet] Nov 4 13:15:13 faboo kernel: [] iscsi_xmit_data+0x66d/0xbb0=20 [iscsi_sfnet] Nov 4 13:15:13 faboo kernel: Nov 4 13:15:13 faboo kernel: [pg0+143613807/1002090496]=20 iscsi_xmit_task+0x39f/0x540 [iscsi_sfnet] Nov 4 13:15:13 faboo kernel: [] iscsi_xmit_task+0x39f/0x540=20 [iscsi_sfnet] Nov 4 13:15:13 faboo kernel: Nov 4 13:15:13 faboo kernel: [pg0+143639673/1002090496]=20 iscsi_xmit_r2t_data+0xc9/0x1c0 [iscsi_sfnet] Nov 4 13:15:13 faboo kernel: [] iscsi_xmit_r2t_data+0xc9/0x1c0= =20 [iscsi_sfnet] Nov 4 13:15:13 faboo kernel: Nov 4 13:15:13 faboo kernel: [pg0+143588753/1002090496]=20 process_tx_requests+0x291/0x340 [iscsi_sfnet] Nov 4 13:15:13 faboo kernel: []=20 process_tx_requests+0x291/0x340 [iscsi_sfnet] Nov 4 13:15:13 faboo kernel: Nov 4 13:15:13 faboo kernel: [autoremove_wake_function+0/96]=20 autoremove_wake_function+0x0/0x60 Nov 4 13:15:13 faboo kernel: []=20 autoremove_wake_function+0x0/0x60 Nov 4 13:15:13 faboo kernel: Nov 4 13:15:13 faboo kernel: [autoremove_wake_function+0/96]=20 autoremove_wake_function+0x0/0x60 Nov 4 13:15:13 faboo kernel: []=20 autoremove_wake_function+0x0/0x60 Nov 4 13:15:13 faboo kernel: Nov 4 13:15:13 faboo kernel: [pg0+143589280/1002090496]=20 iscsi_tx_thread+0x160/0x1e0 [iscsi_sfnet] Nov 4 13:15:13 faboo kernel: [] iscsi_tx_thread+0x160/0x1e0=20 [iscsi_sfnet] Nov 4 13:15:13 faboo kernel: Nov 4 13:15:13 faboo kernel: [default_wake_function+0/32]=20 default_wake_function+0x0/0x20 Nov 4 13:15:13 faboo kernel: [] default_wake_function+0x0/0x20 Nov 4 13:15:13 faboo kernel: Nov 4 13:15:13 faboo kernel: [pg0+143588928/1002090496]=20 iscsi_tx_thread+0x0/0x1e0 [iscsi_sfnet] Nov 4 13:15:13 faboo kernel: [] iscsi_tx_thread+0x0/0x1e0=20 [iscsi_sfnet] Nov 4 13:15:13 faboo kernel: Nov 4 13:15:13 faboo kernel: [kernel_thread_helper+5/16]=20 kernel_thread_helper+0x5/0x10 Nov 4 13:15:13 faboo kernel: [] kernel_thread_helper+0x5/0x10 Nov 4 13:15:13 faboo kernel: --uAKRQypu60I7Lcqm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBinN7TviDkW8mhycRAqXSAJ9wFf9PRlZwz8j+TPg1JAVRApeaxACfZZfQ unxKqsa9M67JGzauh6/cTiM= =A1h1 -----END PGP SIGNATURE----- --uAKRQypu60I7Lcqm-- ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click