what''s the best way of setting up the source tree so that ''make linux26'' will automagically apply a given patch to a particular source tree? eg iscsi initiator patch to 2.6.7-xenU. thanks James
> what''s the best way of setting up the source tree so that ''make linux26'' will automagically apply a given patch to a particular source tree? eg iscsi initiator patch to 2.6.7-xenU.I find it easy to build the iscsi initiator module outside the kernel tree. [Even if you build it into the kernel you''ll still need an initrd anyhow] Just edit TOPDIR and KDIR, then "make ARCH=xen". If you want to apply it as a patch, you could follow the ebtables example in the to-level Makefiles. Ian ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
I don''t know if you use a Debian system. If so I''ll be releasing the XenLinux-Build utility and an iSCSI initator deb in the next couple of days. The XenLinux-BUild is being setup to use the debian style /usr/src/kernel-patches structure to apply various patches auto-magically prior to building your kernel and creating the tarball. The only glitch that I can''t figure out is this: how best to keep the minimal number of kernel source trees while still keeping track of what patches were applied and removeing/applying the necessary ones as apropriate for each config file... For now if you use it you will need to either always use the source with the same patches, or run debian/rules clean prior to creating a different kernel without patches that you have applied before. Anyone have any ideas on this part? First release is tonight btw. Haven''t written the deb creation part as of yet, just tarball creation. Brian On Mon, 2004-08-23 at 07:53, James Harper wrote:> what''s the best way of setting up the source tree so that ''make > linux26'' will automagically apply a given patch to a particular source > tree? eg iscsi initiator patch to 2.6.7-xenU. > > thanks > > James------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Mon, 23 Aug 2004, Ian Pratt wrote:> Just edit TOPDIR and KDIR, then "make ARCH=xen".Why edit? Just specify on the cmdline. ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
actually, to make it for xenU from xen0 (no compiler tools in xenU on my setup), i have to also replace all occurances ''uname -r'' with something that gives me ''2.6.7-xenU'' (eg echo 2.6.7-xenU) in both the makefile and install.sh files. it''s a bit of a pain. the initrd comment is true though, unless iscsi (built in to the kernel) could be convinced to connect via a kernel parameter... that seems a bit extreme though when an initrd would solve the problem nicely. as for patches, would a patch.d directory be out of the question? something that the makefile could call via run-parts after extracting each source tree? It could pass the name of the source tree as a parameter. The patch.d directory would contain scripts that actually apply the patches. James From: Ian Pratt Sent: Tue 24/08/2004 12:42 AM To: James Harper Cc: xen-devel@lists.sourceforge.net; Ian.Pratt@cl.cam.ac.uk Subject: Re: [Xen-devel] iscsi patch> what''s the best way of setting up the source tree so that ''make linux26'' will automagically apply a given patch to a particular source tree? eg iscsi initiator patch to 2.6.7-xenU.I find it easy to build the iscsi initiator module outside the kernel tree. [Even if you build it into the kernel you''ll still need an initrd anyhow] Just edit TOPDIR and KDIR, then "make ARCH=xen". If you want to apply it as a patch, you could follow the ebtables example in the to-level Makefiles. Ian
> actually, to make it for xenU from xen0 (no compiler tools in xenU on my setup), i have to also replace all occurances ''uname -r'' with something that gives me ''2.6.7-xenU'' (eg echo 2.6.7-xenU) in both the makefile and install.sh files. it''s a bit of a pain.Hmm, I''m not sure why you had to do that. I build on a totally different system to the one I''m installing on (it runs a 2.4 kernel) and other than editing TOPDIR and KDIR everything worked fine if I did a "make ARCH=xen", and then did a "make ARCH=xen install" on the target system (it shouldn''t rebuild anything, so you won''t need a compiler).> the initrd comment is true though, unless iscsi (built in to the kernel) could be convinced to connect via a kernel parameter... that seems a bit extreme though when an initrd would solve the problem nicely.Adding a kernel command line parameter to do this would be tough -- iscsid is a big daemon and setting up a connection to an iscsi disk is really quite complex. Ian ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
i hadn''t thought of doing that. I make it hard for myself sometimes!!! there''s an iscsi-boot program which I can''t get working - are there some network ioctl''s not implemented under xen? It seems to be a minimal iscsid which doesn''t persist but connects the root filesystem. Maybe it isn''t maintained anymore but it''s in utils. James From: Ian Pratt Sent: Tue 24/08/2004 5:49 PM To: James Harper Cc: Ian Pratt; xen-devel@lists.sourceforge.net; Ian.Pratt@cl.cam.ac.uk Subject: Re: [Xen-devel] iscsi patch> actually, to make it for xenU from xen0 (no compiler tools in xenU on my setup), i have to also replace all occurances ''uname -r'' with something that gives me ''2.6.7-xenU'' (eg echo 2.6.7-xenU) in both the makefile and install.sh files. it''s a bit of a pain.Hmm, I''m not sure why you had to do that. I build on a totally different system to the one I''m installing on (it runs a 2.4 kernel) and other than editing TOPDIR and KDIR everything worked fine if I did a "make ARCH=xen", and then did a "make ARCH=xen install" on the target system (it shouldn''t rebuild anything, so you won''t need a compiler).> the initrd comment is true though, unless iscsi (built in to the kernel) could be convinced to connect via a kernel parameter... that seems a bit extreme though when an initrd would solve the problem nicely.Adding a kernel command line parameter to do this would be tough -- iscsid is a big daemon and setting up a connection to an iscsi disk is really quite complex. Ian
> there''s an iscsi-boot program which I can''t get working - are there some network ioctl''s not implemented under xen? It seems to be a minimal iscsid which doesn''t persist but connects the root filesystem. Maybe it isn''t maintained anymore but it''s in utils.I haven''t looked at iscsi-boot -- I just cooked my own initrd. Since iscsid doesn''t terminate it''s not possible to free the initrd after the pivot_root, which wases some memory. iscsi-boot sounds like a better way forward. Can you get iscsi-boot working on a native 2.6 system? I''d be rather surprised if it didn''t just work running over Xen. As regards your 2.6 ipv6 problem, are you sure you haven''t got any iptables rules that might be blocking things? Is it the case that you can have a new guest domain booted and talking to the network just fine, and then merely the act of insmod''ing ipv6 into dom0 will break it? Ian ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
iscsi-boot appears to try and bring up the network interface and give it an address and route. unfortunately it says this instead (under an initrd environment): iSCSI: error in getting interface name : No such device iSCSI: Error in bringing up the network interface when I try to run iscsid under initrd it says all isc1093350010.49159 >> iscsid[97]: iSCSI session ioctl failed for <snip>, Can not allocate memory: Cannot allocate memory any ideas? something is obviously different about initrd but i can''t put my finger on what. it''s starting to drive me crazy! James From: Ian Pratt Sent: Tue 24/08/2004 9:58 PM To: James Harper Cc: Ian Pratt; xen-devel@lists.sourceforge.net; Ian.Pratt@cl.cam.ac.uk Subject: Re: [Xen-devel] iscsi patch> there''s an iscsi-boot program which I can''t get working - are there some network ioctl''s not implemented under xen? It seems to be a minimal iscsid which doesn''t persist but connects the root filesystem. Maybe it isn''t maintained anymore but it''s in utils.I haven''t looked at iscsi-boot -- I just cooked my own initrd. Since iscsid doesn''t terminate it''s not possible to free the initrd after the pivot_root, which wases some memory. iscsi-boot sounds like a better way forward. Can you get iscsi-boot working on a native 2.6 system? I''d be rather surprised if it didn''t just work running over Xen. As regards your 2.6 ipv6 problem, are you sure you haven''t got any iptables rules that might be blocking things? Is it the case that you can have a new guest domain booted and talking to the network just fine, and then merely the act of insmod''ing ipv6 into dom0 will break it? Ian
> iscsi-boot appears to try and bring up the network interface and give it an address and route. unfortunately it says this instead (under an initrd environment): > iSCSI: error in getting interface name > : No such device > iSCSI: Error in bringing up the network interfaceAre you sure you''re bringing up the network interface before trying to start iscsi-boot? Put an ''ifconfig eth0'' in your initrd. (You need to enable CONFIG_IP_PNP if you want to set the ip address on the command line)> when I try to run iscsid under initrd it says > all isc1093350010.49159 >> iscsid[97]: iSCSI session ioctl failed for <snip>, Can not allocate memory: Cannot allocate memory > > any ideas? something is obviously different about initrd but i can''t put my finger on what. it''s starting to drive me crazy!I''d get strace on your initrd and start both commands under strace. Are you sure you''ve got the scsi, sd and iscsi_sfnet modules all loaded OK? (stick cat /proc/modules in your initrd). To make life easy for myself I''ve often got initrd''s working using bash before switching to nash to save memory. ldd will tell you what libraries you need to copy across. Ian ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
i''ve got busybox in my initrd so right at the end i dump out to a shell. i bring up the network with an ifconfig in my init script and can ping the network. there must be something in /dev or something somewhere that i''m missing that makes these ioctls not work under the stripped down environment of initrd. i''ll try an strace and see what happens. james From: Ian Pratt Sent: Tue 24/08/2004 11:17 PM To: James Harper Cc: Ian Pratt; xen-devel@lists.sourceforge.net; Ian.Pratt@cl.cam.ac.uk Subject: Re: [Xen-devel] iscsi patch> iscsi-boot appears to try and bring up the network interface and give it an address and route. unfortunately it says this instead (under an initrd environment): > iSCSI: error in getting interface name > : No such device > iSCSI: Error in bringing up the network interfaceAre you sure you''re bringing up the network interface before trying to start iscsi-boot? Put an ''ifconfig eth0'' in your initrd. (You need to enable CONFIG_IP_PNP if you want to set the ip address on the command line)> when I try to run iscsid under initrd it says > all isc1093350010.49159 >> iscsid[97]: iSCSI session ioctl failed for <snip>, Can not allocate memory: Cannot allocate memory > > any ideas? something is obviously different about initrd but i can''t put my finger on what. it''s starting to drive me crazy!I''d get strace on your initrd and start both commands under strace. Are you sure you''ve got the scsi, sd and iscsi_sfnet modules all loaded OK? (stick cat /proc/modules in your initrd). To make life easy for myself I''ve often got initrd''s working using bash before switching to nash to save memory. ldd will tell you what libraries you need to copy across. Ian
Have either of you used a linux based iSCSI target driver? If so, which driver did you use? I''ve found 4 so far and none of them will compile cleanly against my fileserver running 2.6.8 8-(. Second, do any of them export a block device instead of the common file and scsi block device? On Tue, 2004-08-24 at 08:28, James Harper wrote:> i''ve got busybox in my initrd so right at the end i dump out to a > shell. i bring up the network with an ifconfig in my init script and > can ping the network. > > there must be something in /dev or something somewhere that i''m > missing that makes these ioctls not work under the stripped down > environment of initrd. > > i''ll try an strace and see what happens. > > james > > ______________________________________________________________________ > From: Ian Pratt > Sent: Tue 24/08/2004 11:17 PM > To: James Harper > Cc: Ian Pratt; xen-devel@lists.sourceforge.net; Ian.Pratt@cl.cam.ac.uk > Subject: Re: [Xen-devel] iscsi patch > > > > iscsi-boot appears to try and bring up the network interface and give it an address and route. unfortunately it says this instead (under an initrd environment): > > iSCSI: error in getting interface name > > : No such device > > iSCSI: Error in bringing up the network interface > > Are you sure you''re bringing up the network interface before > trying to start iscsi-boot? Put an ''ifconfig eth0'' in your > initrd. > > (You need to enable CONFIG_IP_PNP if you want to set the ip > address on the command line) > > > when I try to run iscsid under initrd it says > > all isc1093350010.49159 >> iscsid[97]: iSCSI session ioctl failed for <snip>, Can not allocate memory: Cannot allocate memory > > > > any ideas? something is obviously different about initrd but i can''t put my finger on what. it''s starting to drive me crazy! > > I''d get strace on your initrd and start both commands under > strace. > > Are you sure you''ve got the scsi, sd and iscsi_sfnet modules all > loaded OK? (stick cat /proc/modules in your initrd). > > To make life easy for myself I''ve often got initrd''s working > using bash before switching to nash to save memory. ldd will tell > you what libraries you need to copy across. > > Ian------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> Have either of you used a linux based iSCSI target driver? If so, which > driver did you use? I''ve found 4 so far and none of them will compile > cleanly against my fileserver running 2.6.8 8-(.I use a h/w target. When I last looked the iscsitarget project on sourceforge looked most promising from an architectural point of view, but they currently only support 2.4. http://zaal.org/iscsi has some useful information. Ian ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Well crudpuppies... 8-P I guess I''ll have to fall back to a 2.4 kernel for now and hope all of the evms features that I''m using on 2.6.8 work in 2.4.x. *sigh* NFS root is just too darn unstable to run any XenLinux kernels from. Just to give you an idea of what I''m trying to acomplish here... a pair of raid-5 servers would provide evms volumes to the iSCSI target drivers. Eaxh Xen node machine would mount a iSCSI target from each nfs server in a raid-mirror block device and export it as a xen block device to the XenLinux image to run from. Eventually I want to create an inteligent iSCSI relay target that would sit on a Linux-HA cluster between the Xen nodes and the iSCSI target fileservers. Upon failure of either machine it would inteligently resync the mirrors in a method similar to rsync so we aren''t copying entire multi-gig images across the entwork just to recover a couple blocks of difference between the mirror sets. I''m not entirely certain how I''m going to acomplish this as of yet. My first idea was some kind of log loop device on the iscsi servers that the iSCSI relay process would write to for checkpointing. Anyways, it''s somethign that doesn''t exist yet and that I would like to eventually put togeather as a HA solution for iSCSI target array. Hence my interest in iSCSI. :) OpenGFS and other solutions are nice, but require a spefic filesystem. I''d rather have the client machines totally unaware of the backend requirements. The clients would just mount iSCSI devices. A fully encapsulated HA disk array instead of forcing the client OS to be aware of the complexities in the backend. On Wed, 2004-08-25 at 02:27, Ian Pratt wrote:> > Have either of you used a linux based iSCSI target driver? If so, which > > driver did you use? I''ve found 4 so far and none of them will compile > > cleanly against my fileserver running 2.6.8 8-(. > > I use a h/w target. > > When I last looked the iscsitarget project on sourceforge looked > most promising from an architectural point of view, but they > currently only support 2.4. > > http://zaal.org/iscsi has some useful information. > > Ian------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> Well crudpuppies... 8-P I guess I''ll have to fall back to a 2.4 kernel > for now and hope all of the evms features that I''m using on 2.6.8 work > in 2.4.x. *sigh* NFS root is just too darn unstable to run any XenLinux > kernels from.You know that 2.6.8 has a horrible NFS bug which is why 2.6.8.1 got released, right? I''ve certainly never found NFS root to work very satisfactorily under any version of Linux I''ve tried -- it''s quite easy to get the thing to deadlock in low memory situations. That''s why I switched to using iSCSI, which with the Cisco initiator actually seems pretty stable, at least for me.> Just to give you an idea of what I''m trying to acomplish here... > > a pair of raid-5 servers would provide evms volumes to the iSCSI target > drivers. Eaxh Xen node machine would mount a iSCSI target from each nfs > server in a raid-mirror block device and export it as a xen block device > to the XenLinux image to run from.You don''t really mean ''nfs server'' in the above do you? I can''t see where NFS comes into the setup you''re describing. Ian ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Yep. It also exists in 2.6.7, 2.6.6, etc. I''ve always found NFS-root to be an undesireable position to be in for any kind of production setup. NFS just isn''t solid enough to handle temporary fileserver failures IMHO. 8-( I used it because I really didn''t have any alternatives for being able to move a XenLinux image between various servers cleanly. You are right below in that I don''t mean nfs server. I''m trying to get away from NFS completely. It''s a hack of a network based filesystem IMHO. Even NFS4 doesn''t solve half of the issues. 8-( NFS5 sounds promising, but yet again, it''s still hacks IMHO. I believe that for a root filesystem you REALLY do want block level interfaces like iSCSI, FC, and other SANs for production systems. Anything less is playing russian roulette with your server IMO. On Wed, 2004-08-25 at 12:40, Ian Pratt wrote:> > Well crudpuppies... 8-P I guess I''ll have to fall back to a 2.4 kernel > > for now and hope all of the evms features that I''m using on 2.6.8 work > > in 2.4.x. *sigh* NFS root is just too darn unstable to run any XenLinux > > kernels from. > > You know that 2.6.8 has a horrible NFS bug which is why 2.6.8.1 > got released, right? > > I''ve certainly never found NFS root to work very satisfactorily > under any version of Linux I''ve tried -- it''s quite easy to get > the thing to deadlock in low memory situations. > > That''s why I switched to using iSCSI, which with the Cisco > initiator actually seems pretty stable, at least for me. > > > Just to give you an idea of what I''m trying to acomplish here... > > > > a pair of raid-5 servers would provide evms volumes to the iSCSI target > > drivers. Eaxh Xen node machine would mount a iSCSI target from each nfs > > server in a raid-mirror block device and export it as a xen block device > > to the XenLinux image to run from. > > You don''t really mean ''nfs server'' in the above do you? I can''t > see where NFS comes into the setup you''re describing. > > Ian------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel