Re: Shared Kernel on Sles10
I'm trying to do manual configuration. The problem now seems to be related to System Map. Using value provided by IBM site during the DEFSYS command ( DEFSYS LXSHR 0-FF EW 100-2FF SR 300-4FF EW MINSIZE=64M seems are related to 2.4 kernel system map. Anybody know the new value for 2.6 kernel? Thanks Max Mark Post ha scritto: On Tue, Sep 25, 2007 at 3:40 PM, in message [EMAIL PROTECTED], Max Belardi [EMAIL PROTECTED] wrote: Thanks Mark if I point to this site... I can get informations here: http://www.vm.ibm.com/linux/linuxnss.html The first paragraph show... The VM Share Kernel Support procedure documented on this page was created a few years ago for use with an older Linux Kernel. So, if you are using Linux Kernel 2.6, it would be best NOT to use this procedure, and instead download a new patch of kernel NSS support from the following link. I point to the new link http://www-128.ibm.com/developerworks/linux/linux390/whatsnew.html ...and there are some documentation about device drivers and commands In chapter 13 there is: Shared kernel support Setting up a Linux NSS means performs this steps: 1. Boot Linux. 2. Insert savesys=nssname into the kernel parameter file used by your boot configuration, where nssname is the name you want to assign to the NSS. The name can be 1-8 characters long and must consist of alphabetic and numeric characters. Be sure not to assign a name that matches any of the device numbers used at your installation. 3. Issue a zipl command to write the modified configuration to the boot device. 4. Close down Linux. 5. Issue an IPL command to boot Linux from the device that holds the Linux kernel. During the IPL process, the NSS is created and Linux is actually booted from the NSS. This procedure seems that is not working at this time What's wrong??? Procedure??? (automatic NSS generation is not supported) Kernel??? (currently is 2.6.16.53) As I said in my other reply, what's wrong is that the patch referenced has not (yet) been incorporated in the kernel that ships with SLES. The developerWorks web site is intended for people that intend to build their own kernel from source. That means, distribution providers, or people who are doing it for educational or other purposes. In your case, you should go with the manual procedure that gives all the z/VM commands to use. Understand, though, that the resulting kernel-in-NSS is not (yet) supported by Novell. If/when we ship that functionality, it will be supported. Until then, you're on your own unless you are willing to negotiate a custom support arrangement. (Personally I don't think it will be any problematic than booting from a kernel on disk, but commercial support models being what they are, that scenario doesn't fall under the supported category yet.) One thing to keep in mind is that putting your kernel into an NSS is only going to save you somewhere around 1-4MB (at most). Unless you have a _lot_ of z/VM guests, that isn't going to buy you much. You're much better off concentrating on implementing CMM (phase 1), or xip2fs. You'll get a lot more return for your efforts there. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Shared Kernel on Sles10
Guys, I'm trying to set up a NSS for Shared kernel support. My distribution is a SLES10 with SP1. The CONFIG_SHARED_KERNEL option seems to be already specified in this kernel level 2.6.16.46 If I try to IPL the first instance with savesys parameter... I'm not able to see any NSS creation in VM (QUERY NSS doesn't show nss i'm creating). Does anyvody know if i need to take other actions befor IPLing a Linux with savesys parameter??? This parameter is pecified on zipl.conf: [nssipl] image = /boot/image target = /boot/zipl ramdisk = /boot/initrd,0x100 parameters = savesys=LNX0NSS root=/dev/dasdb1 dasd=101,201 TERM=dumb 3 Thanks Max -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Shared Kernel on Sles10
Sure... I've set all privileges (E included)! Dave Jones ha scritto: Hi, Max. There should be some CP error or warning messages assoicated with you attempting to save the Linux kernel in an NSS. Does your virtual machine where you are attempting to do this have the correct CP privilege classes? I believe that to save an NSS, you need Class E privileges. Max Belardi wrote: Guys, I'm trying to set up a NSS for Shared kernel support. My distribution is a SLES10 with SP1. The CONFIG_SHARED_KERNEL option seems to be already specified in this kernel level 2.6.16.46 If I try to IPL the first instance with savesys parameter... I'm not able to see any NSS creation in VM (QUERY NSS doesn't show nss i'm creating). Does anyvody know if i need to take other actions befor IPLing a Linux with savesys parameter??? This parameter is pecified on zipl.conf: [nssipl] image = /boot/image target = /boot/zipl ramdisk = /boot/initrd,0x100 parameters = savesys=LNX0NSS root=/dev/dasdb1 dasd=101,201 TERM=dumb 3 Thanks Max -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- DJ V/Soft -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Shared Kernel on Sles10
Thanks Mark if I point to this site... I can get informations here: http://www.vm.ibm.com/linux/linuxnss.html The first paragraph show... The VM Share Kernel Support procedure documented on this page was created a few years ago for use with an older Linux Kernel. So, if you are using Linux Kernel 2.6, it would be best NOT to use this procedure, and instead download a new patch of kernel NSS support from the following link. I point to the new link http://www-128.ibm.com/developerworks/linux/linux390/whatsnew.html ...and there are some documentation about device drivers and commands In chapter 13 there is: Shared kernel support Setting up a Linux NSS means performs this steps: 1. Boot Linux. 2. Insert savesys=nssname into the kernel parameter file used by your boot configuration, where nssname is the name you want to assign to the NSS. The name can be 1-8 characters long and must consist of alphabetic and numeric characters. Be sure not to assign a name that matches any of the device numbers used at your installation. 3. Issue a zipl command to write the modified configuration to the boot device. 4. Close down Linux. 5. Issue an IPL command to boot Linux from the device that holds the Linux kernel. During the IPL process, the NSS is created and Linux is actually booted from the NSS. This procedure seems that is not working at this time What's wrong??? Procedure??? (automatic NSS generation is not supported) Kernel??? (currently is 2.6.16.53) Mark Post ha scritto: On Tue, Sep 25, 2007 at 12:22 PM, in message [EMAIL PROTECTED], Max Belardi [EMAIL PROTECTED] wrote: Guys, I'm trying to set up a NSS for Shared kernel support. My distribution is a SLES10 with SP1. The CONFIG_SHARED_KERNEL option seems to be already specified in this kernel level 2.6.16.46 If I try to IPL the first instance with savesys parameter... I'm not able to see any NSS creation in VM (QUERY NSS doesn't show nss i'm creating). Does anyvody know if i need to take other actions befor IPLing a Linux with savesys parameter??? The automatic creation of the NSS via the savesys= kernel parm is not part of SLES10, even with SP1. I'm hoping to get that included with SP2. If you want to create an NSS, you'll need to do it manually. There is doc (somewhere) on IBM's web site. I'm pretty sure that it's pointed to by the http://linuxvm.org/Info/l390link.html page. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Shared Kernel on Sles10
..done System Boot Control: The system has been set up System Boot Control: Running /etc/init.d/boot.local kernel.hz_timer = 0 appldata info: os-ops registeredé MORE... VMLINUX6 appldata info: mem-ops registeredé appldata info: net_sum-ops registeredé appldata info: Monitoring os data enabled, DIAG 0xDC started. appldata info: Monitoring mem data enabled, DIAG 0xDC started. appldata info: Monitoring net_sum data enabled, DIAG 0xDC started. appldata info: Monitoring timer started. appldata info: Monitoring CPU interval set to 1 milliseconds. Creating //rmfpms/.rmfpms ... mkdir: cannot create directory ù//rmfpms/.rmfpms': No such file or directory Performance gatherer backends not started Creating //rmfpms/.rmfpms ... mkdir: cannot create directory ù//rmfpms/.rmfpms': No such file or directory dasd_proc: /proc/dasd/statictics: 'set on' dasd_proc: Statistics switched on Starting performance gatherer backends ... ls: //rmfpms/bin//*gat: No such file or directory touch: cannot touch ù//rmfpms/.rmfpms/.rmfpms_started': No such file or director y /root/rmfpms/bin/rmfpms: line 59: //rmfpms/bin//gpmddsrv: No such file or direct ory doneé ¬1A..done INIT: Entering runlevel: 3 MORE... VMLINUX6 Dave Jones ha scritto: Hi, Max. I am sure we could be of more help to you in getting this problem fixed if we had a better idea of what the problem really is. It appears that your virtual machine has enough CP privileges (maybe too many!). There should be some CP messages on the Linux 3270 console when you attempt to do the save. Could you show us the console output when you do the actual IPL 150 (say) IPL command, step 5? That might give us a better idea of what is going wrong for you. Max Belardi wrote: Thanks Mark if I point to this site... I can get informations here: http://www.vm.ibm.com/linux/linuxnss.html The first paragraph show... The VM Share Kernel Support procedure documented on this page was created a few years ago for use with an older Linux Kernel. So, if you are using Linux Kernel 2.6, it would be best NOT to use this procedure, and instead download a new patch of kernel NSS support from the following link. I point to the new link http://www-128.ibm.com/developerworks/linux/linux390/whatsnew.html ...and there are some documentation about device drivers and commands In chapter 13 there is: Shared kernel support Setting up a Linux NSS means performs this steps: 1. Boot Linux. 2. Insert savesys=nssname into the kernel parameter file used by your boot configuration, where nssname is the name you want to assign to the NSS. The name can be 1-8 characters long and must consist of alphabetic and numeric characters. Be sure not to assign a name that matches any of the device numbers used at your installation. 3. Issue a zipl command to write the modified configuration to the boot device. 4. Close down Linux. 5. Issue an IPL command to boot Linux from the device that holds the Linux kernel. During the IPL process, the NSS is created and Linux is actually booted from the NSS. This procedure seems that is not working at this time What's wrong??? Procedure??? (automatic NSS generation is not supported) Kernel??? (currently is 2.6.16.53) -- DJ V/Soft -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED
Re: Fedora-DS on Linux for SYstem z
Mark Post ha scritto: On Thu, Sep 6, 2007 at 6:05 AM, in message [EMAIL PROTECTED], Massimiliano Belardi [EMAIL PROTECTED] wrote: Hi Guys, does anybody know if Fedora-DS is included on RedHat for Linux distribution? Anybody tryied to compile it from source to System z platform? What is it? If the package name contains the string fed then I didn't see it on the RHEL5 DVD. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 Is the Directory Server... http://directory.fedoraproject.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
