Has anyone been successful in installing and running iSCSI in domain0? If so, I would like to know your configuration – I’m running xen 3.0 (kernel 2.6.12) and have tried linux-iscsi 4.x & 5.x, open iscsi and unh-iscsi. Most have some compile issues, once resolved they will stack dump when doing some iSCSI operations Thanks _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Has anyone been successful in installing and running iSCSI indomain0?> If so, I would like to know your configuration - > > I''m running xen 3.0 (kernel 2.6.12) and have tried > linux-iscsi 4.x & 5.x, open iscsi and unh-iscsi. Most have > some compile issues, once resolved they will stack dump when > doing some iSCSI operationsI used to use linux-iscsi 4.x on xen -unstable just fine, but I haven''t tried in quite a while. [Some earlier versions did make various dubious assumptions that weren''t true on xen.] One option would be to try the xen merge tree which is currently based off the 2.6.15-rc6, and hence includes the open iscsi patches. http://xenbits.xensource.com/ext/linux-2.6-merge.hg I haven''t tried this, but would be interested to hear whether it works, and would like to fix it if it doesn''t. Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I''m booting dom0 via PXE with iSCSI root and also the domUs use iSCSI root. The latest syslinux is required for booting Xen kernels via PXE. The most stable iSCSI initiator I''ve found was Core-iSCSI (see http://lwn.net/Articles/163608/) built against the Xen 3.0 release kernel sources (don''t forget ARCH=xen when building the module!). For the target I''m using IET (http://sourceforge.net/projects/iscsitarget/) built against the latest FC4 kernel (2.6.14-1.1653). I''ve been running this for some number of weeks and it''s pretty solid. Performance is also good. In theory, this also means I could migrate the guests around the network transparently, but I haven''t tested that yet. The only catch with the software based iSCSI initiator is I had to roll a highly customized initrd which logs into the iSCSI target(s) and in the case of dom0 brings up the bridge. I setup the initrd in such a way that I can pass kernel parameters to tell domU/dom0 which targets to login to. Hope that helps.. Dan- Ian Pratt wrote:> > Has anyone been successful in installing and running iSCSI in >domain0? > > >>If so, I would like to know your configuration - >> >>I''m running xen 3.0 (kernel 2.6.12) and have tried >>linux-iscsi 4.x & 5.x, open iscsi and unh-iscsi. Most have >>some compile issues, once resolved they will stack dump when >>doing some iSCSI operations >> >> > >I used to use linux-iscsi 4.x on xen -unstable just fine, but I haven''t >tried in quite a while. [Some earlier versions did make various dubious >assumptions that weren''t true on xen.] > >One option would be to try the xen merge tree which is currently based >off the 2.6.15-rc6, and hence includes the open iscsi patches. > >http://xenbits.xensource.com/ext/linux-2.6-merge.hg > >I haven''t tried this, but would be interested to hear whether it works, >and would like to fix it if it doesn''t. > >Ian > >_______________________________________________ >Xen-users mailing list >Xen-users@lists.xensource.com >http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks, I try out the Core-iSCSI>From: Dan Cox <dan@wep.net> >To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> >CC: bart brooks <bart_brooks@hotmail.com>, xen-users@lists.xensource.com, > ian.pratt@cl.cam.ac.uk >Subject: Re: [Xen-users] iSCSi on Xen >Date: Sat, 31 Dec 2005 19:13:27 -0600 >MIME-Version: 1.0 >Received: from mail.wep.net ([69.17.23.195]) by >bay0-mc12-f2.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.211); Sat, 31 >Dec 2005 17:13:31 -0800 >Received: from [10.10.10.51] (rock.int [10.10.10.51])by mail.wep.net >(8.13.4/8.13.4) with ESMTP id k011D7og010789;Sat, 31 Dec 2005 19:13:07 >-0600 >X-Message-Info: JGTYoYF78jF/dQyUHhmJXhTPks5HPovwBZhM1UrTRMc>User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) >X-Accept-Language: en-us, en >References: ><A95E2296287EAD4EB592B5DEEFCE0E9D409F19@liverpoolst.ad.cl.cam.ac.uk> >Return-Path: dan@wep.net >X-OriginalArrivalTime: 01 Jan 2006 01:13:31.0788 (UTC) >FILETIME=[948AACC0:01C60E70] > >I''m booting dom0 via PXE with iSCSI root and also the domUs use iSCSI root. >The latest syslinux is required for booting Xen kernels via PXE. >The most stable iSCSI initiator I''ve found was Core-iSCSI (see >http://lwn.net/Articles/163608/) built against the Xen 3.0 release kernel >sources (don''t forget ARCH=xen when building the module!). For the target >I''m using IET (http://sourceforge.net/projects/iscsitarget/) built against >the latest FC4 kernel (2.6.14-1.1653). I''ve been running this for some >number of weeks and it''s pretty solid. Performance is also good. In theory, >this also means I could migrate the guests around the network >transparently, but I haven''t tested that yet. The only catch with the >software based iSCSI initiator is I had to roll a highly customized initrd >which logs into the iSCSI target(s) and in the case of dom0 brings up the >bridge. I setup the initrd in such a way that I can pass kernel parameters >to tell domU/dom0 which targets to login to. Hope that helps.. > >Dan- > >Ian Pratt wrote: > >> > Has anyone been successful in installing and running iSCSI in >>domain0? >> >> >>>If so, I would like to know your configuration - >>> >>>I''m running xen 3.0 (kernel 2.6.12) and have tried linux-iscsi 4.x & 5.x, >>>open iscsi and unh-iscsi. Most have some compile issues, once resolved >>>they will stack dump when doing some iSCSI operations >>> >>> >> >>I used to use linux-iscsi 4.x on xen -unstable just fine, but I haven''t >>tried in quite a while. [Some earlier versions did make various dubious >>assumptions that weren''t true on xen.] >> >>One option would be to try the xen merge tree which is currently based >>off the 2.6.15-rc6, and hence includes the open iscsi patches. >> >>http://xenbits.xensource.com/ext/linux-2.6-merge.hg >> >>I haven''t tried this, but would be interested to hear whether it works, >>and would like to fix it if it doesn''t. >> >>Ian >> >>_______________________________________________ >>Xen-users mailing list >>Xen-users@lists.xensource.com >>http://lists.xensource.com/xen-users >> >> >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Dan Cox wrote:> I''m booting dom0 via PXE with iSCSI root and also the domUs use iSCSI > root. The latest syslinux is required for booting Xen kernels via PXE. > The most stable iSCSI initiator I''ve found was Core-iSCSI (see > http://lwn.net/Articles/163608/) built against the Xen 3.0 release > kernel sources (don''t forget ARCH=xen when building the module!). For > the target I''m using IET > (http://sourceforge.net/projects/iscsitarget/) built against the > latest FC4 kernel (2.6.14-1.1653). I''ve been running this for some > number of weeks and it''s pretty solid. Performance is also good. In > theory, this also means I could migrate the guests around the network > transparently, but I haven''t tested that yet. The only catch with the > software based iSCSI initiator is I had to roll a highly customized > initrd which logs into the iSCSI target(s) and in the case of dom0 > brings up the bridge. I setup the initrd in such a way that I can pass > kernel parameters to tell domU/dom0 which targets to login to. Hope > that helps.. > > Dan- > > Ian Pratt wrote: > >> > Has anyone been successful in installing and running iSCSI in >> domain0? >> >I have had good and bad luck with all the initiators but Core-iSCSI and I have not yet gotten that one to work. Currently I am having the most luck with open-iscsi It seems to give the best in terms of being able to pick and choose what target I connect to. The one issue with open-iscsi is that it seems to use up lots of kernel memory. If I connect more then 3 targets I run out of memory on my Dom0 that is only configured with 256M. I have a 2.0.x version of xen running for nearly a year now with linux-iscsi but I was never able to recreate the config with more current versions of Xen. I have my DomU''s running using the drives as visable in the Dom0. My reason is that I believe that running through the block interface should be much faster than running over the bridging network connection. The biggest issue with using the devices in Dom0 is making sure that the iscsi devices are available using predictable device names. To get this to work I have hacked the udev code to create the devices with a name that matches the target name as set up in iet. I tried booting a Dom0 from an iscsi drive using grubs network boot capability but that did not work very well so I gave up doing that. I have had some luck booting a regular system using syslinux but had to hack the initrd so badly that I just gave it up as being unsupportable. If the open-iscsi guys manage to get iscsid to be restartable it may be worth taking another look at that process again. I have managed to migrate domains from my various xen servers so long as the iscsi devices were available with the same device names on each server. -- Alvin Starr || voice: (416)585-9971 Interlink Connectivity || fax: (416)585-9974 alvin@iplink.net || _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sun, 01 Jan 2006 22:52:48 -0500, Alvin Starr wrote> I have had good and bad luck with all the initiators but Core-iSCSI and > I have not yet gotten that one to work. > Currently I am having the most luck with open-iscsi It seems to give the > best in terms of being able to pick and choose what target I connect > to. The one issue with open-iscsi is that it seems to use up lots of > kernel memory. If I connect more then 3 targets I run out of memory on > my Dom0 that is only configured with 256M. > I have a 2.0.x version of xen running for nearly a year now with > linux-iscsi but I was never able to recreate the config with more > current versions of Xen. > I have my DomU''s running using the drives as visable in the Dom0. My > reason is that I believe that running through the block interface should > be much faster than running over the bridging network connection. > The biggest issue with using the devices in Dom0 is making sure that the > iscsi devices are available using predictable device names. To get this > to work I have hacked the udev code to create the devices with a name > that matches the target name as set up in iet. > > I tried booting a Dom0 from an iscsi drive using grubs network boot > capability but that did not work very well so I gave up doing that. I > have had some luck booting a regular system using syslinux but had to > hack the initrd so badly that I just gave it up as being unsupportable. > If the open-iscsi guys manage to get iscsid to be restartable it may be > worth taking another look at that process again. > > I have managed to migrate domains from my various xen servers so long as > the iscsi devices were available with the same device names on each server.Would it be possible for you to explain or point me on to some documentation on how you get a DomU to run on iSCSI? - I am trying to get this to work with SuSE 10.0 at the moment with the open-iscsi and iscsitarget that is shipped as part of the distribution. - I think I have the iSCSI bit working fine and I have put the device in a volume group and I have created logical volumes on it which I want to use as backing devices for DomU. lvscan shows: ACTIVE ''/dev/datavg01/vm01lv'' [2.50 GB] inherit ACTIVE ''/dev/datavg01/vm01swaplv'' [512.00 MB] inherit I do have to activate the volumes manually with "lvchange -a y" at the moment on which is not too much of a problem as afterthat I can access the volumes fine. I have created a root filesystem in the volume but when I activate the domain I get: Waiting for device /dev/sda1 to appear: ok rootfs: major=8 minor=1 devn=2049 Mounting root /dev/sda1 mount: No such device Kernel panic - not syncing: Attempted to kill init! I think I may be using the wrong kernel module within DomU - any ieas what I should be using? The contents of my domain config file in /etc/xen are: kernel = "/boot/vmlinuz-xen" ramdisk = "/boot/initrd-xen" builder=''linux'' memory = 256 name = "vm01" cpu = -1 vcpus = 4 nics=1 vif = [ ''bridge=xenbr0'' ] disk = [ ''phy:datavg01/vm01swaplv,sda1,w'', ''phy:datavg01/vm01swaplv,sda2,w'' ] root = "/dev/sda1 ro" extra = "3" restart = ''onreboot'' What I am trying to archive at the end is domain migration from on Xen host to another so any documentation of this on iSCSI would be very helpful. Best regards Hubba _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users