Re: HCPGIR450W and HCPGIR453W after editing user direct
Thanks Alan and Berry and everyone else who responded. Alan this wasn't my intent. When I said "immediately" I meant "immediately upon receiving the (guest) IPL interrupt". And I agree with Berry - dynamic changes can (and should) be carried forward. Changes to what I called the z/VM environment - like USER DIRECT- I reckon can (and should) be reflected back to the guest, and implemented *at that IPL*. Obviously I'm out in left field on this, but I'll keep Alans pronouncement to logout in such cases in mind in future. Thanks again ... Shane On Fri, 5 Nov 2010 10:15:08 -0400 Alan Altmark wrote: > It would be a Bad Thing if changing the directory changed a running > virtual server. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: HCPGIR450W and HCPGIR453W after editing user direct
Hi Koray, Lets try a step by step approach. Start by verifing that you are running with the correct directory. And second, try to find out what the correct IPL processes are for the guests. I would expect that your zVM guy has handed the correct instructions and that you indeed have to edit DIRECT USER. However, some sites use DIRMAINT and some do not. It doesn't matter what you use but it is vital for you to know for sure who owns the directory and what file the actual (correct) directory is. Especially in this case where you get unexpected results just after you have put a directory online. If DIRMAINT is the owner and you use MAINT you can get an (very) old directory online. The same can be true if you have editted the wrong file or by accident have put the wrong directoryfile online. Perhaps you have used a directory where minidiskentries have been swapped. So logon to user MAINT again. Issue a "FILEL DIRECT USER * ". Is there only one on C or do you have more than one? If there is one on A or B then that's your problem. And just for fun, issue "FILEL USER DIRECT * ". Found any that could be a directory and if so, any differences in the minidiskstatements for the guests? As for DIRMAINT, issue "VMLINK DIRMAINT 1DB (FILEL" and see if there is a USER BACKUP. And if so, is it a recent one? Once you know for sure that you are looking at the correct directory, take a look at the IPL statement in the directoryentry for this linux guest. Is it IPL 100 (or IPL 102)? In case of IPL the environment is set in the directory and the guest will IPL from the minidisk in the IPL statement. Then you need to determine if the minidisks have swapped for some reason and why. Or is it IPL CMS? Then take a look at the statement for the 191 device. Is it a LINK or a MDISK statement? Are they perhaps linked to the TCPMAINT 191? That would explain your comments on the TCPMAINT userid. Next take a look at the linux guest 191 disk. "VMLINK 191 (FILEL". In there you will find the PROFILE EXEC. It will execute some commands, IPL is one of them. What IPL command is executed, IPL 100 or IPL 102? Your comments on IPL from 100 and/or 102 would suggest to me that at some point the (default) configuration has been changed. And perhaps also the location of the 191 minidisk. It looks like it has been decided to change the default IPL 100 to IPL 102 (or the other way around). Should you have put an obsolete directory online it could be that in the old directory the 100 and 102 are swapped compaired to the new directory. Or that the 191 minidisk has been changed to have a different profile exec for some of the guests. Regards, Berry. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Koray Kusat Sent: zaterdag 6 november 2010 0:01 To: LINUX-390@VM.MARIST.EDU Subject: Re: HCPGIR450W and HCPGIR453W after editing user direct Hi Berry, The owner is MAINT i guess, because i'm doing all these editing things with MAINT user. I found the file PROFILE EXEC, in TCPMAINT user area (sorry, i dont know the big iron's terminology, i found it with "filel * * *" command with TCPMAINT user) which runs Linux guests automatically during IPL. The default setting is Minidisk100, but if i change it to 102, my all guests will try to IPL from 102, and this is not what i want. Because i have 14 guests and 8 of them IPL from 102, 6 of them IPL from 100. I need to change this file (or script) somehow, but i dont know how to do it. Regards 2010/11/5 van Sleeuwen, Berry > > Hi Koray, > > Go back to the process of your directory change. > > Is MAINT or DIRMAINT the leading directory owner? (take a look at the > DIRMAINT 1DB, if there is a recent USER BACKUP chances are DIRMAINT > was > leading) > Are you sure the correct directory has been put online? Did you have a > DIRECT USER on the A or B disk? > Is DIRECT USER C indeed the directory that you should use? (usually > the directory is called USER DIRECT. So either there should be a file > with that name or your zVM guy has renamed it to DIRECT USER.) > > Regards, Berry. > > -Original Message- > From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of > koray > Sent: vrijdag 5 november 2010 20:24 > To: LINUX-390@VM.MARIST.EDU > Subject: Re: HCPGIR450W and HCPGIR453W after editing user direct > > Hi Eddie, > > thanks for the tip! > yes i did ipl from minidisk 102, and /boot is on Minidisk as well. > But /dev/dasda1 seems as a part of LVM group. Maybe i remembered wrong. > Anyway, i dont know why all these changed but now i need to change the > default boot minidisk from 100 to 102, my 8 guests have this problem. > I think its somewhere in ZVM side. How can i do it? > > Regards > > On 05.11.2010 19:10, Eddie Chen wrote: > > Koray, > > > > Did you try to IPL 102 and see if it comes up. > > Is the /boot is also on Minidisk 102 as well? > > You also should mount "/dev/dasda1 to /m
Re: HCPGIR450W and HCPGIR453W after editing user direct
Hi Berry, The owner is MAINT i guess, because i'm doing all these editing things with MAINT user. I found the file PROFILE EXEC, in TCPMAINT user area (sorry, i dont know the big iron's terminology, i found it with "filel * * *" command with TCPMAINT user) which runs Linux guests automatically during IPL. The default setting is Minidisk100, but if i change it to 102, my all guests will try to IPL from 102, and this is not what i want. Because i have 14 guests and 8 of them IPL from 102, 6 of them IPL from 100. I need to change this file (or script) somehow, but i dont know how to do it. Regards 2010/11/5 van Sleeuwen, Berry > > Hi Koray, > > Go back to the process of your directory change. > > Is MAINT or DIRMAINT the leading directory owner? (take a look at the > DIRMAINT 1DB, if there is a recent USER BACKUP chances are DIRMAINT was > leading) > Are you sure the correct directory has been put online? Did you have a > DIRECT USER on the A or B disk? > Is DIRECT USER C indeed the directory that you should use? (usually the > directory is called USER DIRECT. So either there should be a file with > that name or your zVM guy has renamed it to DIRECT USER.) > > Regards, Berry. > > -Original Message- > From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of > koray > Sent: vrijdag 5 november 2010 20:24 > To: LINUX-390@VM.MARIST.EDU > Subject: Re: HCPGIR450W and HCPGIR453W after editing user direct > > Hi Eddie, > > thanks for the tip! > yes i did ipl from minidisk 102, and /boot is on Minidisk as well. > But /dev/dasda1 seems as a part of LVM group. Maybe i remembered wrong. > Anyway, i dont know why all these changed but now i need to change the > default boot minidisk from 100 to 102, my 8 guests have this problem. > I think its somewhere in ZVM side. How can i do it? > > Regards > > On 05.11.2010 19:10, Eddie Chen wrote: > > Koray, > > > > Did you try to IPL 102 and see if it comes up. > > Is the /boot is also on Minidisk 102 as well? > > You also should mount "/dev/dasda1 to /mnt " to see if the > "/boot" > > is still on that partition. > > > > > > > > -Original Message- > > From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of > > koray > > Sent: Friday, November 05, 2010 9:24 AM > > To: LINUX-390@VM.MARIST.EDU > > Subject: Re: HCPGIR450W and HCPGIR453W after editing user direct > > > > Hi again to all, > > > > after doing lots of research i found the problem is somewhere in > > linux, let me explain. > > > > - I checked all dasds, there were no offline or unattached. > > - No overlap in diskmap file. > > - I compared direct user file with the old backup and i saw there is > > no change with disk mappings. > > - I did all similar checks on Z/VM side, no problems found. > > - I ipled from SLES11 DVD and choosed boot installed system, it boots! > > So i thought it's about ZIPL configuration but there was nothing wrong > > > there. I regenerated the bootmap again by running /sbin/zipl, and > > tried to reipl from Minidisk100, but no luck. > > > > Now lets see what's weird; > > > > When i first installed SLES, the disk mapping was: > > Minidisk100 - dasda - /boot > > Minidisk101 - dasdb - swap > > Minidisk102 - dasdc - / > > Minidisk110 - dasdd - LVM Member > > ... > > Minidisk209 - dasdn - LVM Member > > > > But when i boot with cd, and activate the DASD's i see > > > > Minidisk100 - dasda > > Minidisk101 - _dasdn_ > > Minidisk102 - dasdb > > Minidisk110 - dasdc > > ... > > > > It seems the mapping has changed somehow. But when i run the installed > > > system from DVD menu, i see DASD's as they supposed to be: > > > > linux101:~ # more /proc/dasd/devices > > 0.0.0100(ECKD) at ( 94: 0) is dasda > > 0.0.0101(ECKD) at ( 94: 4) is dasdb > > 0.0.0102(ECKD) at ( 94: 8) is dasdc > > 0.0.0110(ECKD) at ( 94: 12) is dasdd > > 0.0.0200(ECKD) at ( 94: 16) is dasde > > 0.0.0201(ECKD) at ( 94: 20) is dasdf > > 0.0.0202(ECKD) at ( 94: 24) is dasdg > > 0.0.0203(ECKD) at ( 94: 28) is dasdh > > 0.0.0204(ECKD) at ( 94: 32) is dasdi > > 0.0.0205(ECKD) at ( 94: 36) is dasdj > > 0.0.0206(ECKD) at ( 94: 40) is dasdk > > 0.0.0207(ECKD) at ( 94: 44) is dasdl > > 0.0.0208(ECKD) at ( 94: 48) is dasdm > > 0.0.0209(ECKD) at ( 94: 52) is dasdn > > > > > > linux101:~ # more /etc/fstab > > /dev/disk/by-path/ccw-0.0.0101-part1 swap swap > > /dev/disk/by-path/ccw-0.0.0102-part1 / ext3 > > /dev/system/home /home > > /dev/system/opt /opt > > /dev/system/tmp /tmp > > /dev/system/usr /usr > > /dev/system/var /var > > proc /proc > > sysfs /sys > > debugfs /sys/kernel/debug > > devpts /dev/pts > > > > > > linux101:~ # more /etc/zipl.conf > > # Modified by YaST2. Last modification on Mon Nov 1 16:46:48 UTC 2010 > > > [defaultboot] defaultmenu = menu > > > > ###Don't change this comment - YaST2 identifier: Origina
Re: HCPGIR450W and HCPGIR453W after editing user direct
Hi Koray, Go back to the process of your directory change. Is MAINT or DIRMAINT the leading directory owner? (take a look at the DIRMAINT 1DB, if there is a recent USER BACKUP chances are DIRMAINT was leading) Are you sure the correct directory has been put online? Did you have a DIRECT USER on the A or B disk? Is DIRECT USER C indeed the directory that you should use? (usually the directory is called USER DIRECT. So either there should be a file with that name or your zVM guy has renamed it to DIRECT USER.) Regards, Berry. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of koray Sent: vrijdag 5 november 2010 20:24 To: LINUX-390@VM.MARIST.EDU Subject: Re: HCPGIR450W and HCPGIR453W after editing user direct Hi Eddie, thanks for the tip! yes i did ipl from minidisk 102, and /boot is on Minidisk as well. But /dev/dasda1 seems as a part of LVM group. Maybe i remembered wrong. Anyway, i dont know why all these changed but now i need to change the default boot minidisk from 100 to 102, my 8 guests have this problem. I think its somewhere in ZVM side. How can i do it? Regards On 05.11.2010 19:10, Eddie Chen wrote: >Koray, > > Did you try to IPL 102 and see if it comes up. > Is the /boot is also on Minidisk 102 as well? > You also should mount "/dev/dasda1 to /mnt " to see if the "/boot" > is still on that partition. > > > > -Original Message- > From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of > koray > Sent: Friday, November 05, 2010 9:24 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: HCPGIR450W and HCPGIR453W after editing user direct > > Hi again to all, > > after doing lots of research i found the problem is somewhere in > linux, let me explain. > > - I checked all dasds, there were no offline or unattached. > - No overlap in diskmap file. > - I compared direct user file with the old backup and i saw there is > no change with disk mappings. > - I did all similar checks on Z/VM side, no problems found. > - I ipled from SLES11 DVD and choosed boot installed system, it boots! > So i thought it's about ZIPL configuration but there was nothing wrong > there. I regenerated the bootmap again by running /sbin/zipl, and > tried to reipl from Minidisk100, but no luck. > > Now lets see what's weird; > > When i first installed SLES, the disk mapping was: > Minidisk100 - dasda - /boot > Minidisk101 - dasdb - swap > Minidisk102 - dasdc - / > Minidisk110 - dasdd - LVM Member > ... > Minidisk209 - dasdn - LVM Member > > But when i boot with cd, and activate the DASD's i see > > Minidisk100 - dasda > Minidisk101 - _dasdn_ > Minidisk102 - dasdb > Minidisk110 - dasdc > ... > > It seems the mapping has changed somehow. But when i run the installed > system from DVD menu, i see DASD's as they supposed to be: > > linux101:~ # more /proc/dasd/devices > 0.0.0100(ECKD) at ( 94: 0) is dasda > 0.0.0101(ECKD) at ( 94: 4) is dasdb > 0.0.0102(ECKD) at ( 94: 8) is dasdc > 0.0.0110(ECKD) at ( 94:12) is dasdd > 0.0.0200(ECKD) at ( 94:16) is dasde > 0.0.0201(ECKD) at ( 94:20) is dasdf > 0.0.0202(ECKD) at ( 94:24) is dasdg > 0.0.0203(ECKD) at ( 94:28) is dasdh > 0.0.0204(ECKD) at ( 94:32) is dasdi > 0.0.0205(ECKD) at ( 94:36) is dasdj > 0.0.0206(ECKD) at ( 94:40) is dasdk > 0.0.0207(ECKD) at ( 94:44) is dasdl > 0.0.0208(ECKD) at ( 94:48) is dasdm > 0.0.0209(ECKD) at ( 94:52) is dasdn > > > linux101:~ # more /etc/fstab > /dev/disk/by-path/ccw-0.0.0101-part1 swap swap > /dev/disk/by-path/ccw-0.0.0102-part1 /ext3 > /dev/system/home /home > /dev/system/opt /opt > /dev/system/tmp /tmp > /dev/system/usr /usr > /dev/system/var /var > proc /proc > sysfs/sys > debugfs /sys/kernel/debug > devpts /dev/pts > > > linux101:~ # more /etc/zipl.conf > # Modified by YaST2. Last modification on Mon Nov 1 16:46:48 UTC 2010 > [defaultboot] defaultmenu = menu > > ###Don't change this comment - YaST2 identifier: Original name: > linux### [Linux] > image = /boot/image-2.6.27.19-5-default > target = /boot/zipl > ramdisk = /boot/initrd-2.6.27.19-5-default,0x200 > parameters = "root=/dev/disk/by-path/ccw-0.0.0102-part1 TERM=dumb" > > :menu > default = 1 > prompt = 1 > target = /boot/zipl > timeout = 10 > 1 = Linux > 2 = ipl > 3 = Failsafe > > ###Don't change this comment - YaST2 identifier: Original name: ipl### > [ipl] > image = /boot/image > target = /boot/zipl > ramdisk = /boot/initrd,0x200 > parameters = "root=/dev/disk/by-path/ccw-0.0.0102-part1 TERM=dumb" > > ###Don't change this comment - YaST2 identifier: Original name: > failsafe### [Failsafe] > image = /boot/image > target = /boot/zipl > ramdisk = /boot/initrd,0x200 > parameters = "root=/dev/dis
Re: HCPGIR450W and HCPGIR453W after editing user direct
On 05.11.2010 22:16, Mark Post wrote: -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of koray Sent: Friday, November 05, 2010 9:24 AM Subject: Re: HCPGIR450W and HCPGIR453W after editing user direct -snip- - I ipled from SLES11 DVD and choosed boot installed system, it boots! So i thought it's about ZIPL configuration but there was nothing wrong there. I regenerated the bootmap again by running /sbin/zipl, and tried to reipl from Minidisk100, but no luck. Did you have all your file systems mounted the same way as they are "normally" and did you have /sys, /dev, and /proc bind mounted as well before doing the chroot? Now lets see what's weird; When i first installed SLES, the disk mapping was: Minidisk100 - dasda - /boot Minidisk101 - dasdb - swap Minidisk102 - dasdc - / Minidisk110 - dasdd - LVM Member ... Minidisk209 - dasdn - LVM Member But when i boot with cd, and activate the DASD's i see Minidisk100 - dasda Minidisk101 - _dasdn_ Minidisk102 - dasdb Minidisk110 - dasdc ... It seems the mapping has changed somehow. But when i run the installed system from DVD menu, i see DASD's as they supposed to be: This is to be expected, and not at all weird. The naming of the devices is going to depend on what order they are brought online by the kernel. In your production initrd, that order is determined by /linuxrc. On the rescue system, that order is not available (or you didn't use it. I forget how the rescue system brings up DASD or if it is done manually.). -snip- linux101:~ # more /etc/fstab /dev/disk/by-path/ccw-0.0.0101-part1 swap swap /dev/disk/by-path/ccw-0.0.0102-part1 /ext3 /dev/system/home /home /dev/system/opt /opt /dev/system/tmp /tmp /dev/system/usr /usr /dev/system/var /var proc /proc sysfs/sys debugfs /sys/kernel/debug devpts /dev/pts I don't see an entry in there for /boot. To me that means you aren't using a separate /boot file system, and your kernel and initrds are in the /boot directory _on_the_root_filesystem_, linux101:~ # more /etc/zipl.conf # Modified by YaST2. Last modification on Mon Nov 1 16:46:48 UTC 2010 [defaultboot] defaultmenu = menu ###Don't change this comment - YaST2 identifier: Original name: linux### [Linux] image = /boot/image-2.6.27.19-5-default target = /boot/zipl ramdisk = /boot/initrd-2.6.27.19-5-default,0x200 parameters = "root=/dev/disk/by-path/ccw-0.0.0102-part1 TERM=dumb" -snip- As you can see, it seems there is nothing wrong.But when i try to boot from Minidisk100, i see; See above. I suspect you should be IPLing from 102, not 100. Or, make sure that /boot on 100 and /boot on 102 are synchronized and mkinitrd and zipl re-run with them in the proper arrangement, as well as /etc/fstab being updated to point /boot to 100 if that's what you really want. Thanks Mark for your explanation, i noticed it with Eddie's mail. I dont know how it changed, it's really weird. Now i need to change the default boot minidisk from 100 to 102. Regards -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: HCPGIR450W and HCPGIR453W after editing user direct
Hi Eddie, thanks for the tip! yes i did ipl from minidisk 102, and /boot is on Minidisk as well. But /dev/dasda1 seems as a part of LVM group. Maybe i remembered wrong. Anyway, i dont know why all these changed but now i need to change the default boot minidisk from 100 to 102, my 8 guests have this problem. I think its somewhere in ZVM side. How can i do it? Regards On 05.11.2010 19:10, Eddie Chen wrote: Koray, Did you try to IPL 102 and see if it comes up. Is the /boot is also on Minidisk 102 as well? You also should mount "/dev/dasda1 to /mnt " to see if the "/boot" is still on that partition. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of koray Sent: Friday, November 05, 2010 9:24 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: HCPGIR450W and HCPGIR453W after editing user direct Hi again to all, after doing lots of research i found the problem is somewhere in linux, let me explain. - I checked all dasds, there were no offline or unattached. - No overlap in diskmap file. - I compared direct user file with the old backup and i saw there is no change with disk mappings. - I did all similar checks on Z/VM side, no problems found. - I ipled from SLES11 DVD and choosed boot installed system, it boots! So i thought it's about ZIPL configuration but there was nothing wrong there. I regenerated the bootmap again by running /sbin/zipl, and tried to reipl from Minidisk100, but no luck. Now lets see what's weird; When i first installed SLES, the disk mapping was: Minidisk100 - dasda - /boot Minidisk101 - dasdb - swap Minidisk102 - dasdc - / Minidisk110 - dasdd - LVM Member ... Minidisk209 - dasdn - LVM Member But when i boot with cd, and activate the DASD's i see Minidisk100 - dasda Minidisk101 - _dasdn_ Minidisk102 - dasdb Minidisk110 - dasdc ... It seems the mapping has changed somehow. But when i run the installed system from DVD menu, i see DASD's as they supposed to be: linux101:~ # more /proc/dasd/devices 0.0.0100(ECKD) at ( 94: 0) is dasda 0.0.0101(ECKD) at ( 94: 4) is dasdb 0.0.0102(ECKD) at ( 94: 8) is dasdc 0.0.0110(ECKD) at ( 94:12) is dasdd 0.0.0200(ECKD) at ( 94:16) is dasde 0.0.0201(ECKD) at ( 94:20) is dasdf 0.0.0202(ECKD) at ( 94:24) is dasdg 0.0.0203(ECKD) at ( 94:28) is dasdh 0.0.0204(ECKD) at ( 94:32) is dasdi 0.0.0205(ECKD) at ( 94:36) is dasdj 0.0.0206(ECKD) at ( 94:40) is dasdk 0.0.0207(ECKD) at ( 94:44) is dasdl 0.0.0208(ECKD) at ( 94:48) is dasdm 0.0.0209(ECKD) at ( 94:52) is dasdn linux101:~ # more /etc/fstab /dev/disk/by-path/ccw-0.0.0101-part1 swap swap /dev/disk/by-path/ccw-0.0.0102-part1 /ext3 /dev/system/home /home /dev/system/opt /opt /dev/system/tmp /tmp /dev/system/usr /usr /dev/system/var /var proc /proc sysfs/sys debugfs /sys/kernel/debug devpts /dev/pts linux101:~ # more /etc/zipl.conf # Modified by YaST2. Last modification on Mon Nov 1 16:46:48 UTC 2010 [defaultboot] defaultmenu = menu ###Don't change this comment - YaST2 identifier: Original name: linux### [Linux] image = /boot/image-2.6.27.19-5-default target = /boot/zipl ramdisk = /boot/initrd-2.6.27.19-5-default,0x200 parameters = "root=/dev/disk/by-path/ccw-0.0.0102-part1 TERM=dumb" :menu default = 1 prompt = 1 target = /boot/zipl timeout = 10 1 = Linux 2 = ipl 3 = Failsafe ###Don't change this comment - YaST2 identifier: Original name: ipl### [ipl] image = /boot/image target = /boot/zipl ramdisk = /boot/initrd,0x200 parameters = "root=/dev/disk/by-path/ccw-0.0.0102-part1 TERM=dumb" ###Don't change this comment - YaST2 identifier: Original name: failsafe### [Failsafe] image = /boot/image target = /boot/zipl ramdisk = /boot/initrd,0x200 parameters = "root=/dev/disk/by-path/ccw-0.0.0102-part1 TERM=dumb x11failsafe" As you can see, it seems there is nothing wrong.But when i try to boot from Minidisk100, i see; Mounting root _/dev/disk/by-path/ccw-0.0.0100-part1_ Unknown filesystem type 'LVM2_member' Kernel panic - not syncing: Attemted to kill init! HCPGIR450W ... I re-run ZIPL but, no change, it still searches 0.0.0100 for root fs. I think the reason is same with the first DASD activation menu with DVD. Linux somehow sees diskmaps different and i cant change the ZIPL behaviour. Now, i need to change ZIPL to mount root-fs from Minidisk102. And then research why the Minidisk-Linux Dasd mapping is changing. Sorry for the long mail and thanks for your patient. Regards On 05.11.2010 15:30, martin roby wrote: I have seen this happen as well; when trying to boot from san disks. Do you have your root filesystem on a san disk? Can you post your user direct entry for a user that fails? When you logged all the way out of your Linu
Re: HCPGIR450W and HCPGIR453W after editing user direct
> -Original Message- > From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of koray > Sent: Friday, November 05, 2010 9:24 AM > Subject: Re: HCPGIR450W and HCPGIR453W after editing user direct > -snip- > - I ipled from SLES11 DVD and choosed boot installed system, it boots! > So i thought it's about ZIPL configuration but there was nothing wrong > there. I regenerated the bootmap again by running /sbin/zipl, and tried > to reipl from Minidisk100, but no luck. Did you have all your file systems mounted the same way as they are "normally" and did you have /sys, /dev, and /proc bind mounted as well before doing the chroot? > Now lets see what's weird; > > When i first installed SLES, the disk mapping was: > Minidisk100 - dasda - /boot > Minidisk101 - dasdb - swap > Minidisk102 - dasdc - / > Minidisk110 - dasdd - LVM Member > ... > Minidisk209 - dasdn - LVM Member > > But when i boot with cd, and activate the DASD's i see > > Minidisk100 - dasda > Minidisk101 - _dasdn_ > Minidisk102 - dasdb > Minidisk110 - dasdc > ... > > It seems the mapping has changed somehow. But when i run the installed > system from DVD menu, i see DASD's as they supposed to be: This is to be expected, and not at all weird. The naming of the devices is going to depend on what order they are brought online by the kernel. In your production initrd, that order is determined by /linuxrc. On the rescue system, that order is not available (or you didn't use it. I forget how the rescue system brings up DASD or if it is done manually.). -snip- > linux101:~ # more /etc/fstab > /dev/disk/by-path/ccw-0.0.0101-part1 swap swap > /dev/disk/by-path/ccw-0.0.0102-part1 /ext3 > /dev/system/home /home > /dev/system/opt /opt > /dev/system/tmp /tmp > /dev/system/usr /usr > /dev/system/var /var > proc /proc > sysfs/sys > debugfs /sys/kernel/debug > devpts /dev/pts > I don't see an entry in there for /boot. To me that means you aren't using a separate /boot file system, and your kernel and initrds are in the /boot directory _on_the_root_filesystem_, > linux101:~ # more /etc/zipl.conf > # Modified by YaST2. Last modification on Mon Nov 1 16:46:48 UTC 2010 > [defaultboot] > defaultmenu = menu > > ###Don't change this comment - YaST2 identifier: Original name: linux### > [Linux] > image = /boot/image-2.6.27.19-5-default > target = /boot/zipl > ramdisk = /boot/initrd-2.6.27.19-5-default,0x200 > parameters = "root=/dev/disk/by-path/ccw-0.0.0102-part1 TERM=dumb" -snip- > As you can see, it seems there is nothing wrong.But when i try to boot > from Minidisk100, i see; See above. I suspect you should be IPLing from 102, not 100. Or, make sure that /boot on 100 and /boot on 102 are synchronized and mkinitrd and zipl re-run with them in the proper arrangement, as well as /etc/fstab being updated to point /boot to 100 if that's what you really want. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: HCPGIR450W and HCPGIR453W after editing user direct
Koray,
Did you try to IPL 102 and see if it comes up.
Is the /boot is also on Minidisk 102 as well?
You also should mount "/dev/dasda1 to /mnt " to see if the "/boot"
is still on that partition.
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of koray
Sent: Friday, November 05, 2010 9:24 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: HCPGIR450W and HCPGIR453W after editing user direct
Hi again to all,
after doing lots of research i found the problem is somewhere in linux,
let me explain.
- I checked all dasds, there were no offline or unattached.
- No overlap in diskmap file.
- I compared direct user file with the old backup and i saw there is no
change with disk mappings.
- I did all similar checks on Z/VM side, no problems found.
- I ipled from SLES11 DVD and choosed boot installed system, it boots!
So i thought it's about ZIPL configuration but there was nothing wrong
there. I regenerated the bootmap again by running /sbin/zipl, and tried
to reipl from Minidisk100, but no luck.
Now lets see what's weird;
When i first installed SLES, the disk mapping was:
Minidisk100 - dasda - /boot
Minidisk101 - dasdb - swap
Minidisk102 - dasdc - /
Minidisk110 - dasdd - LVM Member
...
Minidisk209 - dasdn - LVM Member
But when i boot with cd, and activate the DASD's i see
Minidisk100 - dasda
Minidisk101 - _dasdn_
Minidisk102 - dasdb
Minidisk110 - dasdc
...
It seems the mapping has changed somehow. But when i run the installed
system from DVD menu, i see DASD's as they supposed to be:
linux101:~ # more /proc/dasd/devices
0.0.0100(ECKD) at ( 94: 0) is dasda
0.0.0101(ECKD) at ( 94: 4) is dasdb
0.0.0102(ECKD) at ( 94: 8) is dasdc
0.0.0110(ECKD) at ( 94:12) is dasdd
0.0.0200(ECKD) at ( 94:16) is dasde
0.0.0201(ECKD) at ( 94:20) is dasdf
0.0.0202(ECKD) at ( 94:24) is dasdg
0.0.0203(ECKD) at ( 94:28) is dasdh
0.0.0204(ECKD) at ( 94:32) is dasdi
0.0.0205(ECKD) at ( 94:36) is dasdj
0.0.0206(ECKD) at ( 94:40) is dasdk
0.0.0207(ECKD) at ( 94:44) is dasdl
0.0.0208(ECKD) at ( 94:48) is dasdm
0.0.0209(ECKD) at ( 94:52) is dasdn
linux101:~ # more /etc/fstab
/dev/disk/by-path/ccw-0.0.0101-part1 swap swap
/dev/disk/by-path/ccw-0.0.0102-part1 /ext3
/dev/system/home /home
/dev/system/opt /opt
/dev/system/tmp /tmp
/dev/system/usr /usr
/dev/system/var /var
proc /proc
sysfs/sys
debugfs /sys/kernel/debug
devpts /dev/pts
linux101:~ # more /etc/zipl.conf
# Modified by YaST2. Last modification on Mon Nov 1 16:46:48 UTC 2010
[defaultboot]
defaultmenu = menu
###Don't change this comment - YaST2 identifier: Original name: linux###
[Linux]
image = /boot/image-2.6.27.19-5-default
target = /boot/zipl
ramdisk = /boot/initrd-2.6.27.19-5-default,0x200
parameters = "root=/dev/disk/by-path/ccw-0.0.0102-part1 TERM=dumb"
:menu
default = 1
prompt = 1
target = /boot/zipl
timeout = 10
1 = Linux
2 = ipl
3 = Failsafe
###Don't change this comment - YaST2 identifier: Original name: ipl###
[ipl]
image = /boot/image
target = /boot/zipl
ramdisk = /boot/initrd,0x200
parameters = "root=/dev/disk/by-path/ccw-0.0.0102-part1 TERM=dumb"
###Don't change this comment - YaST2 identifier: Original name: failsafe###
[Failsafe]
image = /boot/image
target = /boot/zipl
ramdisk = /boot/initrd,0x200
parameters = "root=/dev/disk/by-path/ccw-0.0.0102-part1 TERM=dumb
x11failsafe"
As you can see, it seems there is nothing wrong.But when i try to boot
from Minidisk100, i see;
Mounting root _/dev/disk/by-path/ccw-0.0.0100-part1_
Unknown filesystem type 'LVM2_member'
Kernel panic - not syncing: Attemted to kill init!
HCPGIR450W ...
I re-run ZIPL but, no change, it still searches 0.0.0100 for root fs. I
think the reason is same with the first DASD activation menu with DVD.
Linux somehow sees diskmaps different and i cant change the ZIPL behaviour.
Now, i need to change ZIPL to mount root-fs from Minidisk102.
And then research why the Minidisk-Linux Dasd mapping is changing.
Sorry for the long mail and thanks for your patient.
Regards
On 05.11.2010 15:30, martin roby wrote:
> I have seen this happen as well; when trying to boot from san disks.
> Do you have your root filesystem on a san disk? Can you post your user
> direct entry for a user that fails?
>
> When you logged all the way out of your Linux guests you reset that
> user. A lot of different things could have happened at that point.
>
> Do any of your Linux guests still work? When they boot do they go
> straight to the
> CPU errors? I am assuming you don't get the zipl boot menu.
>
> One thing to look for is an overlaps in your disk map.
>
> {from maint}
> diskmap user {generates a new disk map}
> x user diskmap {opens the new map in the wond
Re: HCPGIR450W and HCPGIR453W after editing user direct
I noticed that he did a X USER DIRECT C Then DIRECTXA USER Hopefully he does have a USER DIRECT on A or B. I always do a DIRECTXA USER DIRECT C to make sure I pick the one C. Sam -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Michael Harding Sent: Friday, November 05, 2010 10:36 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: HCPGIR450W and HCPGIR453W after editing user direct Think of it this way: The directory definition of a guest are the "specs" used to construct its virtual machine when it logs on. Re-iplling a guest without logging off/on is the same as rebooting your windows box without making physical changes to it, changes to the "specs" aren't seen. (There are commands which can change the virtual machine configuration dynamically, an IPL without logoff/on will pick them up and may not even be necessary, depending on what they are and the guest's OS; but that's independent of directory changes.) -- Mike Harding z/VM System Support Linux on 390 Port wrote on 11/04/2010 07:51:41 PM: > From: Shane > To: LINUX-390@vm.marist.edu > Date: 11/04/2010 07:52 PM > Subject: Re: HCPGIR450W and HCPGIR453W after editing user direct > Sent by: Linux on 390 Port > > Alan, for those of us that stumbled from the real (FSVO "real") world > into the rabbit hole that is z/VM, are admonishments such as this > inscribed in stone anywhere ?. > Where I came from IPL clears up everything - this is not something I > would have inherently expected. I can (now) see the logic, but it ain't > "in your face" obvious. > > Shane ... > -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: HCPGIR450W and HCPGIR453W after editing user direct
Think of it this way: The directory definition of a guest are the "specs" used to construct its virtual machine when it logs on. Re-iplling a guest without logging off/on is the same as rebooting your windows box without making physical changes to it, changes to the "specs" aren't seen. (There are commands which can change the virtual machine configuration dynamically, an IPL without logoff/on will pick them up and may not even be necessary, depending on what they are and the guest's OS; but that's independent of directory changes.) -- Mike Harding z/VM System Support Linux on 390 Port wrote on 11/04/2010 07:51:41 PM: > From: Shane > To: LINUX-390@vm.marist.edu > Date: 11/04/2010 07:52 PM > Subject: Re: HCPGIR450W and HCPGIR453W after editing user direct > Sent by: Linux on 390 Port > > Alan, for those of us that stumbled from the real (FSVO "real") world > into the rabbit hole that is z/VM, are admonishments such as this > inscribed in stone anywhere ?. > Where I came from IPL clears up everything - this is not something I > would have inherently expected. I can (now) see the logic, but it ain't > "in your face" obvious. > > Shane ... > -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Infoprint 6500 driver for ZLinux
On 11/3/10 4:55 PM, "koray" wrote: > What i did is, created the printer using IPP (socket) with IBM > Proprinter driver, the result was pages of garbage characters for a text > file writing just "test" inside. Then i converted the text file to > postscript using paps , the result was same. > The result for Epson FX-1050 was just nothing. The job was seemed > finished succesfully, but there was no action on printer, for both text > and postscript files. Check the settings on the printer. It's supposed to switch emulations automatically, but someone may have disabled that feature. Anything in /var/log/cups for the print job? For the text file, you should have gotten at least a minimal set of log entries. Also, what happens when you use the "print test page" button in the WWW interface to CUPS? -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: HCPGIR450W and HCPGIR453W after editing user direct
On Friday, 11/05/2010 at 10:50 EDT, Clovis Pereira wrote: > I think this model was planned for CMS (or equivalent) users, not for the > new "plug and play" systems, like zVM itself and Linux. > Example: when we attach a dasd to Linux or second level zVM, they recognize > the new resource and puts it online, "automagically". So, the signalling > mechanism already exist. > Why don't extent it to changes in USER DIRECT (HCPDIR?), including memory > changes? And left the decision how to process the interrupt to guest OS. > Maybe it is material for another "Request For Change" The CIM model was built by the DMTF with engineers from many companies and was NOT tuned for CMS. It was tuned for MS Virtual Server, KVM, VMware, z/VM, LPAR, It turned out that System z made significant contributions since it was so far ahead of the others. You can infer needed hypervisor capabilities from just studying the model. (The DMTF is to Systems Management what the IETF is to Networking.) z/VM conforms to the model. Your proposal would break the model and would, as I tried to describe, be a Bad Idea. If you alter the "current" settings for the virtual machine and add a virtual resource (dedicated dasd, minidisk), then those signals would indeed be sent. BTW, the only thing CMS can do in response to those signals is automatically RELEASE a disk that is DETACHed. If z/VM does not virtualize some set of signals, then dynamic changes to the runtime environment for the associated resource would be prohibited. Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 alan_altm...@us.ibm.com IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Can't create ctcmpc groups
On Friday, November 05, 2010 09:37:35 am you wrote: > I just cut and pasted into my startup script from the readme file at > > http://www-01.ibm.com/support/docview.wss?uid=swg27006164 > > to wit: > ¨¨ > Load the ctcmpc device driver > > # /sbin/modprobe ctcmpc > Configure the read & write i/o device addresses for a ctcmpc device: > # echo 0.0.0d90,0.0.0d91 > /sys/bus/ccwgroup/drivers/ctcmpc/group > Set the ctcmpc device online: > # echo 1 > /sys/bus/ccwgroup/drivers/ctcmpc/0.0.0d90/online > > > But I tried it with the quotes, and got the same result. The quotes are unnecessary, because there are no "shell-special" characters in that string to protect from betting changed by the shell. > This 'echo' command is strange. I wonder how it creates all these > device files in /sys/bus/ccwgroup...? All the echo command does is copy its command line arguments to its standard output. There's nothing strange about echo. The strangeness here is that the files in the /sys filesystem aren't really files: they're references to data structures within the kernel. So when you write to /sys/bus/ccwgroup/drivers/ctcmpc/group, you're not actually doing real file I/O. Instead, the I/O call invokes a function within the CTC driver that parses your two device numbers and builds the appropriate data structures within the CTC driver to represent when as a paired device. Part of generating the new data strutures involves registering entries for them with the /sys filesystem and that causes those new file entries to appear under /sys/bus/ccwgroup. That's the magic of the sysfs pseudo-filesystem: it is showing you information about the internal state of the kernel and letting you make certain changes to it. It's essentially a user-space interface to certain kernel-space data structures. If you use CP to link a new device to a Linux guest, you'll see sysfs entries for that device appear as the Linux driver detects the new "hardware". - MacK. - Edmund R. MacKenty Software Architect Rocket Software 275 Grove Street - Newton, MA 02466-2272 - USA Tel: +1.617.614.4321 Email: m...@rs.com Web: www.rocketsoftware.com -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: HCPGIR450W and HCPGIR453W after editing user direct
Hello, My personal vision: I think this model was planned for CMS (or equivalent) users, not for the new "plug and play" systems, like zVM itself and Linux. Example: when we attach a dasd to Linux or second level zVM, they recognize the new resource and puts it online, "automagically". So, the signalling mechanism already exist. Why don't extent it to changes in USER DIRECT (HCPDIR?), including memory changes? And left the decision how to process the interrupt to guest OS. Maybe it is material for another "Request For Change" __ Clovis |> | From: | |> >--| |Alan Altmark | >--| |> | To:| |> >--| |LINUX-390@vm.marist.edu | >--| |> | Date: | |> >--| |05/11/2010 12:16 | >--| |> | Subject: | |> >--| |Re: HCPGIR450W and HCPGIR453W after editing user direct | >--| |> | Sent by: | |> >--| |Linux on 390 Port | >--| On Friday, 11/05/2010 at 12:59 EDT, Shane wrote: > We are talking about a hipervisor running (nominally) directly on the > hardware - not a user-space application like VBox. > In my naivety I would expect z/VM to be *very* aware of an interrupt > for a guest IPL. If there are changes in the (z/VM) environment why > wouldn't they resolved immediately at that point ?. It's all "smoke and > mirrors" after all. > Principle of least astonishment should prevail IMHO. During the development of the CIM models for (all) virtualization, it was recognized that a virtual machine has four states: o Defined - the virtual server is defined within the hypervisor, but is not consuming resources (an entry in USER DIRECT) o Active - the virtual server is running (logged on) o Paused - resources allocated, but virtual server is not running (press PA1 with SET RUN OFF) o Suspended - hibernated (saved state) with no real resources (other than disk) allocated. On System z, applies only to newer Linuxen. There are configuration settings associated with the definition of the virtual server, and there are settings associated with the running virtual server. The runtime settings can be constrained by the definition. Consider memory: it has a default and a maximum value in USER DIRECT. The current runtime value can be anything up to the maximum. It would be a Bad Thing if changing the directory changed a running virtual server. That would seriously hamper proper Change Management and would create havoc in a virtual machine. Some conditions are detected only at virtual server IPL and the virtual server has the expectation that they will remain that way forever, as there is no signalling mechanism to tell it that there has been a change. (Consider privilege class.) This is one of the reasons that revoking a virtual machine's access to a minidisk does not DETACH the minidisk from the virtual machine. It is a separate Act of Will
Re: Can't create ctcmpc groups
Thanks, Peter, Rob THe devices 400 and 401 didn't show up on the output from lscss, even though they were listed in the VM USER DIR for the virrtual machine. I took a tip from the other thread today and logged the machine off and on. That seems to have fixed the problem. The lscss shows the devices, and the device looks online. ifconfig shows the mpc0 interface, as it did before I upgraded. It looks good apart from some error messages about the kernel being tainted by LiS - but I think I've seen those before. According to chap. 11 of the device driver manual, I should have 3 directories: /sys/bus/ccwgroup/drivers/ctcmpc/0.0.400 /sys/bus/ccwgroup/drivers/0.0.400 and /sys/devices/ctcmpc/0.0.400 I have the first two, but not the last one. I don't even have a directory /sys/devices/ctcmpc: --- LNXCCL:~ # ls /sys/devices css0 cu3088 iucv platform qeth system -- I'll have to wait until Monday to try it with commserver, but at least I've got my interface back up. Looks like a good weekend. Roger On Fri, 2010-11-05 at 14:42 +0100, Peter Oberparleiter wrote: > On 05.11.2010 13:44, Roger Evans wrote: > > When I execute the command: > > echo 0.0.0400,0.0.0401>/sys/bus/ccwgroup/drivers/ctcmpc/group > > > > as per instructions from the device drivers, Features and Commands > > manual, i get an error message. Like this: > > > > LNXCCL:/etc/rc.d # echo 0.0.0400,0.0.0401 > >> /sys/bus/ccwgroup/drivers/ctcmpc/group > > -bash: echo: write error: Invalid argument > > Possible reasons for this error: > 1. devices 400 and 401 are not recognizes by Linux > 2. devices are of different type > 3. devices are already grouped > > For 1 and 2 see the output of the lscss command. If the device doesn't > show up, make sure they are correctly attached to your z/VM guest/LPAR. > For 3 see if a directory named 0.0.0400 exists in > /sys/bus/ccwgroup/devices. If so, set it offline and ungroup it. > > > Regards, >Peter Oberparleiter > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ Med vennlig hilsen Roger Evans Systemkonsulent AutoData Norge AS - www.autodata.no - supp...@autodata.no Tlf: +47 23 17 20 30 Direkte: +47 23 17 20 46 - Faks: +47 23 17 20 50 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ <>
Re: HCPGIR450W and HCPGIR453W after editing user direct
On Friday, 11/05/2010 at 12:59 EDT, Shane wrote: > We are talking about a hipervisor running (nominally) directly on the > hardware - not a user-space application like VBox. > In my naivety I would expect z/VM to be *very* aware of an interrupt > for a guest IPL. If there are changes in the (z/VM) environment why > wouldn't they resolved immediately at that point ?. It's all "smoke and > mirrors" after all. > Principle of least astonishment should prevail IMHO. During the development of the CIM models for (all) virtualization, it was recognized that a virtual machine has four states: o Defined - the virtual server is defined within the hypervisor, but is not consuming resources (an entry in USER DIRECT) o Active - the virtual server is running (logged on) o Paused - resources allocated, but virtual server is not running (press PA1 with SET RUN OFF) o Suspended - hibernated (saved state) with no real resources (other than disk) allocated. On System z, applies only to newer Linuxen. There are configuration settings associated with the definition of the virtual server, and there are settings associated with the running virtual server. The runtime settings can be constrained by the definition. Consider memory: it has a default and a maximum value in USER DIRECT. The current runtime value can be anything up to the maximum. It would be a Bad Thing if changing the directory changed a running virtual server. That would seriously hamper proper Change Management and would create havoc in a virtual machine. Some conditions are detected only at virtual server IPL and the virtual server has the expectation that they will remain that way forever, as there is no signalling mechanism to tell it that there has been a change. (Consider privilege class.) This is one of the reasons that revoking a virtual machine's access to a minidisk does not DETACH the minidisk from the virtual machine. It is a separate Act of Will to alter the runtime environment. So the question of who is astonished the least depends on who is more important in the equation: you or the virtual machine. :-) You're flexible and understanding, the virtual machine is less so. Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 alan_altm...@us.ibm.com IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Can't create ctcmpc groups
On 05.11.2010 13:44, Roger Evans wrote: When I execute the command: echo 0.0.0400,0.0.0401>/sys/bus/ccwgroup/drivers/ctcmpc/group as per instructions from the device drivers, Features and Commands manual, i get an error message. Like this: LNXCCL:/etc/rc.d # echo 0.0.0400,0.0.0401 /sys/bus/ccwgroup/drivers/ctcmpc/group -bash: echo: write error: Invalid argument Possible reasons for this error: 1. devices 400 and 401 are not recognizes by Linux 2. devices are of different type 3. devices are already grouped For 1 and 2 see the output of the lscss command. If the device doesn't show up, make sure they are correctly attached to your z/VM guest/LPAR. For 3 see if a directory named 0.0.0400 exists in /sys/bus/ccwgroup/devices. If so, set it offline and ungroup it. Regards, Peter Oberparleiter -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Can't create ctcmpc groups
I just cut and pasted into my startup script from the readme file at http://www-01.ibm.com/support/docview.wss?uid=swg27006164 to wit: ¨¨ Load the ctcmpc device driver # /sbin/modprobe ctcmpc Configure the read & write i/o device addresses for a ctcmpc device: # echo 0.0.0d90,0.0.0d91 > /sys/bus/ccwgroup/drivers/ctcmpc/group Set the ctcmpc device online: # echo 1 > /sys/bus/ccwgroup/drivers/ctcmpc/0.0.0d90/online But I tried it with the quotes, and got the same result. This 'echo' command is strange. I wonder how it creates all these device files in /sys/bus/ccwgroup...? Roger On Fri, 2010-11-05 at 13:48 +0100, Rob van der Heij wrote: > On Fri, Nov 5, 2010 at 1:44 PM, Roger Evans wrote: > > > LNXCCL:/etc/rc.d # echo 0.0.0400,0.0.0401 > >>/sys/bus/ccwgroup/drivers/ctcmpc/group > > -bash: echo: write error: Invalid argument > > Wasn't it with quotes around the argument? Like > echo "0.0.0400,0.0.0401" > group > > Rob > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ Med vennlig hilsen Roger Evans Systemkonsulent AutoData Norge AS - www.autodata.no - supp...@autodata.no Tlf: +47 23 17 20 30 Direkte: +47 23 17 20 46 - Faks: +47 23 17 20 50 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ <>
Re: HCPGIR450W and HCPGIR453W after editing user direct
Hi again to all,
after doing lots of research i found the problem is somewhere in linux,
let me explain.
- I checked all dasds, there were no offline or unattached.
- No overlap in diskmap file.
- I compared direct user file with the old backup and i saw there is no
change with disk mappings.
- I did all similar checks on Z/VM side, no problems found.
- I ipled from SLES11 DVD and choosed boot installed system, it boots!
So i thought it's about ZIPL configuration but there was nothing wrong
there. I regenerated the bootmap again by running /sbin/zipl, and tried
to reipl from Minidisk100, but no luck.
Now lets see what's weird;
When i first installed SLES, the disk mapping was:
Minidisk100 - dasda - /boot
Minidisk101 - dasdb - swap
Minidisk102 - dasdc - /
Minidisk110 - dasdd - LVM Member
...
Minidisk209 - dasdn - LVM Member
But when i boot with cd, and activate the DASD's i see
Minidisk100 - dasda
Minidisk101 - _dasdn_
Minidisk102 - dasdb
Minidisk110 - dasdc
...
It seems the mapping has changed somehow. But when i run the installed
system from DVD menu, i see DASD's as they supposed to be:
linux101:~ # more /proc/dasd/devices
0.0.0100(ECKD) at ( 94: 0) is dasda
0.0.0101(ECKD) at ( 94: 4) is dasdb
0.0.0102(ECKD) at ( 94: 8) is dasdc
0.0.0110(ECKD) at ( 94:12) is dasdd
0.0.0200(ECKD) at ( 94:16) is dasde
0.0.0201(ECKD) at ( 94:20) is dasdf
0.0.0202(ECKD) at ( 94:24) is dasdg
0.0.0203(ECKD) at ( 94:28) is dasdh
0.0.0204(ECKD) at ( 94:32) is dasdi
0.0.0205(ECKD) at ( 94:36) is dasdj
0.0.0206(ECKD) at ( 94:40) is dasdk
0.0.0207(ECKD) at ( 94:44) is dasdl
0.0.0208(ECKD) at ( 94:48) is dasdm
0.0.0209(ECKD) at ( 94:52) is dasdn
linux101:~ # more /etc/fstab
/dev/disk/by-path/ccw-0.0.0101-part1 swap swap
/dev/disk/by-path/ccw-0.0.0102-part1 /ext3
/dev/system/home /home
/dev/system/opt /opt
/dev/system/tmp /tmp
/dev/system/usr /usr
/dev/system/var /var
proc /proc
sysfs/sys
debugfs /sys/kernel/debug
devpts /dev/pts
linux101:~ # more /etc/zipl.conf
# Modified by YaST2. Last modification on Mon Nov 1 16:46:48 UTC 2010
[defaultboot]
defaultmenu = menu
###Don't change this comment - YaST2 identifier: Original name: linux###
[Linux]
image = /boot/image-2.6.27.19-5-default
target = /boot/zipl
ramdisk = /boot/initrd-2.6.27.19-5-default,0x200
parameters = "root=/dev/disk/by-path/ccw-0.0.0102-part1 TERM=dumb"
:menu
default = 1
prompt = 1
target = /boot/zipl
timeout = 10
1 = Linux
2 = ipl
3 = Failsafe
###Don't change this comment - YaST2 identifier: Original name: ipl###
[ipl]
image = /boot/image
target = /boot/zipl
ramdisk = /boot/initrd,0x200
parameters = "root=/dev/disk/by-path/ccw-0.0.0102-part1 TERM=dumb"
###Don't change this comment - YaST2 identifier: Original name: failsafe###
[Failsafe]
image = /boot/image
target = /boot/zipl
ramdisk = /boot/initrd,0x200
parameters = "root=/dev/disk/by-path/ccw-0.0.0102-part1 TERM=dumb
x11failsafe"
As you can see, it seems there is nothing wrong.But when i try to boot
from Minidisk100, i see;
Mounting root _/dev/disk/by-path/ccw-0.0.0100-part1_
Unknown filesystem type 'LVM2_member'
Kernel panic - not syncing: Attemted to kill init!
HCPGIR450W ...
I re-run ZIPL but, no change, it still searches 0.0.0100 for root fs. I
think the reason is same with the first DASD activation menu with DVD.
Linux somehow sees diskmaps different and i cant change the ZIPL behaviour.
Now, i need to change ZIPL to mount root-fs from Minidisk102.
And then research why the Minidisk-Linux Dasd mapping is changing.
Sorry for the long mail and thanks for your patient.
Regards
On 05.11.2010 15:30, martin roby wrote:
I have seen this happen as well; when trying to boot from san disks.
Do you have your root filesystem on a san disk? Can you post your user
direct entry for a user that fails?
When you logged all the way out of your Linux guests you reset that
user. A lot of different things could have happened at that point.
Do any of your Linux guests still work? When they boot do they go
straight to the
CPU errors? I am assuming you don't get the zipl boot menu.
One thing to look for is an overlaps in your disk map.
{from maint}
diskmap user {generates a new disk map}
x user diskmap {opens the new map in the wonderful z/os editor}
{then search for overlaps}
{I usually use "right 10" first so I can see the "gap' messages"}
/over
If you have an overlap that would be the issue.
Otherwise either you are not finding your disk at boot or your zipl
boot was corrupted.
If you a working system you can move the disk to the new system and
try to mount it from the working Linux , if it mounts then you can try
to rewire the zipl boot block.
Martin
On Thu, Nov 4, 2010 at 3:31 PM, koray wrote:
Hello all,
We have 14 Sles Guests runni
Re: Can't create ctcmpc groups
On Fri, Nov 5, 2010 at 1:44 PM, Roger Evans wrote: > LNXCCL:/etc/rc.d # echo 0.0.0400,0.0.0401 >>/sys/bus/ccwgroup/drivers/ctcmpc/group > -bash: echo: write error: Invalid argument Wasn't it with quotes around the argument? Like echo "0.0.0400,0.0.0401" > group Rob -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Can't create ctcmpc groups
I am trying to use the channel-to-channel driver with the IBM Communications Processor on Z, SLES10sp2. This worked once, but after a reinstall with a new version of commserver, I'm unable to get the ctcmpc to start. When I execute the command: echo 0.0.0400,0.0.0401 >/sys/bus/ccwgroup/drivers/ctcmpc/group as per instructions from the device drivers, Features and Commands manual, i get an error message. Like this: LNXCCL:/etc/rc.d # echo 0.0.0400,0.0.0401 >/sys/bus/ccwgroup/drivers/ctcmpc/group -bash: echo: write error: Invalid argument This used to work. I am using SLES10sp2. and /sys/bus/ccwgroup/drivers/ctcmpc/group looks like this: ls -l /sys/bus/ccwgroup/drivers/ctcmpc/group --w--- 1 root root 0 Nov 5 13:35 /sys/bus/ccwgroup/drivers/ctcmpc/group Any suggestions? Has anybody ever used this product? (CommServer) Roger Evans Autodata, Norge A/S -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: HCPGIR450W and HCPGIR453W after editing user direct
I have seen this happen as well; when trying to boot from san disks.
Do you have your root filesystem on a san disk? Can you post your user
direct entry for a user that fails?
When you logged all the way out of your Linux guests you reset that
user. A lot of different things could have happened at that point.
Do any of your Linux guests still work? When they boot do they go
straight to the
CPU errors? I am assuming you don't get the zipl boot menu.
One thing to look for is an overlaps in your disk map.
{from maint}
diskmap user {generates a new disk map}
x user diskmap {opens the new map in the wonderful z/os editor}
{then search for overlaps}
{I usually use "right 10" first so I can see the "gap' messages"}
/over
If you have an overlap that would be the issue.
Otherwise either you are not finding your disk at boot or your zipl
boot was corrupted.
If you a working system you can move the disk to the new system and
try to mount it from the working Linux , if it mounts then you can try
to rewire the zipl boot block.
Martin
On Thu, Nov 4, 2010 at 3:31 PM, koray wrote:
> Hello all,
>
> We have 14 Sles Guests running on Z/VM 5.4. We edited the user direct
> file and changed the memory settings of Linux guests.For example;
>
> linux001 - 2048M 4096M
> linux002 - 2048M 4096M
> has changed to
> linux001 - 3072M 6144M
> linux002 - 1024M 2048M
>
> Now, i cant ipl my guest's. When i try to ipl from minidisk 100,
> linux 001 says:
> HCPGIR453W CP Entered, program interrupt loop.
> linux002 says:
> HCPGIR450W CP entered, disabled wait PSW 00020001 8000 001536B0
>
> It seems disk mapping are broken but i'm totally sure that i only
> changed Memory settings, not touched minidisk settings.
>
> Need your help please.
>
> Regards
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
Re: HCPGIR450W and HCPGIR453W after editing user direct
Hah. I see. CMS IPL re-boots the OS within the existing VM. LOGON/LOGOFF resets the VM. Bit like the difference between re-IPLing z/OS and re-activating the hardware partition it lives in. Thanks Berry/Rob -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of van Sleeuwen, Berry Sent: Friday, 5 November 2010 8:02 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: HCPGIR450W and HCPGIR453W after editing user direct Hi Anthony, I think the confusion is the word IPL. When we mention "IPL" we mean executing the command IPL *OR* logon a machine. But they are not always the same thing. If you logon a machine (and I mean logon a machine that is not running) you get the configuration as set in the directory. Usually you also have an IPL command in the directory. Either IPL CMS or IPL . I would think of the USER DIRECT entry as a set of (CP) commands. So basically the logon of a machine executes a series of commands to setup your virtual envirnment. What you do after the logon of a machine is up to you. If you have the correct authorization you can change quite a bit in the virtual environment. But an IPL command is just one of the commands that is executed. Yes, expanding storage has limits in the directory. For instance USER BERRY xxx 32M 128M. When I logon I get 32M storage. With DEFINE STOR I can reset that size to anything up to 128M. But when I execute the IPL CMS command I still get the size of the last DEF STOR command. It will not be reset to 32M. Any re-IPL will still have the size I had set the last time. Basically the same is true for devices in your virtual machine. I initially get what I have specified in the directory. But if I want to change that afterwards I can LINK, DETACH, DEFINE all kinds of devices. These changes remain in effect untill I either change it again or logoff/logon the virtual machine. Regards, Berry. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Anthony Thompson Sent: vrijdag 5 november 2010 10:44 To: LINUX-390@VM.MARIST.EDU Subject: Re: HCPGIR450W and HCPGIR453W after editing user direct Excuse me? If you re-IPL a virtual machine surely it resets its environment according to USER DIRECT? A virtual subset of the existing IOCDS, with the virtual addresses and user(sic)-defined storage? What do you inherit from a previous instance of a virtual machine? Bit confused here, but I freely admit I'm a z/OS person. Isn't LINKing devices (190, 490, whatever) simply part of your VM profile? And isn't expanding storage limited by what is in USER DIRECT? If you set DEF STOR in CP/CMS and re-IPL your user machine, how does the next iteration remember it? Thanks for explaining any confusion here, Ant. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: HCPGIR450W and HCPGIR453W after editing user direct
Hi Anthony, I think the confusion is the word IPL. When we mention "IPL" we mean executing the command IPL *OR* logon a machine. But they are not always the same thing. If you logon a machine (and I mean logon a machine that is not running) you get the configuration as set in the directory. Usually you also have an IPL command in the directory. Either IPL CMS or IPL . I would think of the USER DIRECT entry as a set of (CP) commands. So basically the logon of a machine executes a series of commands to setup your virtual envirnment. What you do after the logon of a machine is up to you. If you have the correct authorization you can change quite a bit in the virtual environment. But an IPL command is just one of the commands that is executed. Yes, expanding storage has limits in the directory. For instance USER BERRY xxx 32M 128M. When I logon I get 32M storage. With DEFINE STOR I can reset that size to anything up to 128M. But when I execute the IPL CMS command I still get the size of the last DEF STOR command. It will not be reset to 32M. Any re-IPL will still have the size I had set the last time. Basically the same is true for devices in your virtual machine. I initially get what I have specified in the directory. But if I want to change that afterwards I can LINK, DETACH, DEFINE all kinds of devices. These changes remain in effect untill I either change it again or logoff/logon the virtual machine. Regards, Berry. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Anthony Thompson Sent: vrijdag 5 november 2010 10:44 To: LINUX-390@VM.MARIST.EDU Subject: Re: HCPGIR450W and HCPGIR453W after editing user direct Excuse me? If you re-IPL a virtual machine surely it resets its environment according to USER DIRECT? A virtual subset of the existing IOCDS, with the virtual addresses and user(sic)-defined storage? What do you inherit from a previous instance of a virtual machine? Bit confused here, but I freely admit I'm a z/OS person. Isn't LINKing devices (190, 490, whatever) simply part of your VM profile? And isn't expanding storage limited by what is in USER DIRECT? If you set DEF STOR in CP/CMS and re-IPL your user machine, how does the next iteration remember it? Thanks for explaining any confusion here, Ant. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ ÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n k a n g e h e i m e i n f o r m a t i e b e v a t t e n e n k e l b e s t e m d v o o r d e g e a d r e s s e e r d e . I n d i e n d i t b e r i c h t n i e t v o o r u i s b e s t e m d , v e r z o e k e n w i j u d i t o n m i d d e l l i j k a a n o n s t e m e l d e n e n h e t b e r i c h t t e v e r n i e t i g e n . A a n g e z i e n d e i n t e g r i t e i t v a n h e t b e r i c h t n i e t v e i l i g g e s t e l d i s m i d d e l s v e r z e n d i n g v i a i n t e r n e t , k a n A t o s O r i g i n n i e t a a n s p r a k e l i j k w o r d e n g e h o u d e n v o o r d e i n h o u d d a a r v a n . H o e w e l w i j o n s i n s p a n n e n e e n v i r u s v r i j n e t w e r k t e h a n t e r e n , g e v e n w i j g e e n e n k e l e g a r a n t i e d a t d i t b e r i c h t v i r u s v r i j i s , n o c h a a n v a a r d e n w i j e n i g e a a n s p r a k e l i j k h e i d v o o r d e m o g e l i j k e a a n w e z i g h e i d v a n e e n v i r u s i n d i t b e r i c h t . O p a l o n z e r e c h t s v e r h o u d i n g e n , a a n b i e d i n g e n e n o v e r e e n k o m s t e n w a a r o n d e r A t o s O r i g i n g o e d e r e n e n / o f d i e n s t e n l e v e r t z i j n m e t u i t s l u i t i n g v a n a l l e a n d e r e v o o r w a a r d e n d e L e v e r i n g s v o o r w a a r d e n v a n A t o s O r i g i n v a n t o e p a s s i n g . D e z e w o r d e n u o p a a n v r a a g d i r e c t k o s t e l o o s t o e g e z o n d e n . T h i s e - m a i l a n d t h e d o c u m e n t s a t t a c h e d a r e c o n f i d e n t i a l a n d i n t e n d e d s o l e l y f o r t h e a d d r e s s e e ; i t m a y a l s o b e p r i v i l e g e d . I f y o u r e c e i v e t h i s e - m a i l i n e r r o r , p l e a s e n o t i f y t h e s e n d e r i m m e d i a t e l y a n d d e s t r o y i t .
Re: HCPGIR450W and HCPGIR453W after editing user direct
On Fri, Nov 5, 2010 at 10:44 AM, Anthony Thompson wrote: > Excuse me? > > If you re-IPL a virtual machine surely it resets its environment according to > USER DIRECT? A virtual subset of the existing IOCDS, with the virtual > addresses and user(sic)-defined storage? Incorrect. An IPL of the virtual machine clears some volatile things (does a RESET) and then loads the operating system (again). Any configuration changes that you made to your virtual machine remain since logon remain in effect. Depending on the operating system, some changes require an IPL to actually exploit the new configuration. > What do you inherit from a previous instance of a virtual machine? Bit > confused here, but I freely admit I'm a z/OS person. Isn't LINKing devices > (190, 490, whatever) simply part of your VM profile? And isn't expanding > storage limited by what is in USER DIRECT? If you set DEF STOR in CP/CMS and > re-IPL your user machine, how does the next iteration remember it? Your last question shows you correctly spotted the mistake in your initial assumptions ;-) Only LOGOFF / LOGON creates a new virtual machine like specified in the current directory. Many of the configuration changes can be done through CP commands, but it is sometimes easier to go the full logoff/logon cycle (it also demonstrates it will work next time after you forgot about these changes). Indeed, any configuration changes to your virtual machine are restricted by the directory and external security manager, and sometimes by available system resources. | Rob PS My guess is that OP was not aware that DIRMAINT was installed, and thus activated a (slightly modified) old USER DIRECT. If DIRMAINT is still running, DIRM DIRECT would restore things. Otherwise, depending on the changes since then, autologging of DIRMAINT might still work... -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: HCPGIR450W and HCPGIR453W after editing user direct
Excuse me? If you re-IPL a virtual machine surely it resets its environment according to USER DIRECT? A virtual subset of the existing IOCDS, with the virtual addresses and user(sic)-defined storage? What do you inherit from a previous instance of a virtual machine? Bit confused here, but I freely admit I'm a z/OS person. Isn't LINKing devices (190, 490, whatever) simply part of your VM profile? And isn't expanding storage limited by what is in USER DIRECT? If you set DEF STOR in CP/CMS and re-IPL your user machine, how does the next iteration remember it? Thanks for explaining any confusion here, Ant. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of van Sleeuwen, Berry Sent: Friday, 5 November 2010 6:49 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: HCPGIR450W and HCPGIR453W after editing user direct Shane, An IPL doesn't clear the (virtual) hardware environment of the guest, and that's the way it should be. For instance, when I test a new CMS I can link the MAINT 490 instead of the 190. Or when I need a bit more storage to edit a large CMS file I can use DEF STOR to increase my default. I do not want to have that reset when I IPL the machine. Regards, Berry. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Shane Sent: vrijdag 5 november 2010 5:58 To: LINUX-390@VM.MARIST.EDU Subject: Re: HCPGIR450W and HCPGIR453W after editing user direct We are talking about a hipervisor running (nominally) directly on the hardware - not a user-space application like VBox. In my naivety I would expect z/VM to be *very* aware of an interrupt for a guest IPL. If there are changes in the (z/VM) environment why wouldn't they resolved immediately at that point ?. It's all "smoke and mirrors" after all. Principle of least astonishment should prevail IMHO. Shane ... -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: HCPGIR450W and HCPGIR453W after editing user direct
Shane, An IPL doesn't clear the (virtual) hardware environment of the guest, and that's the way it should be. For instance, when I test a new CMS I can link the MAINT 490 instead of the 190. Or when I need a bit more storage to edit a large CMS file I can use DEF STOR to increase my default. I do not want to have that reset when I IPL the machine. Regards, Berry. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Shane Sent: vrijdag 5 november 2010 5:58 To: LINUX-390@VM.MARIST.EDU Subject: Re: HCPGIR450W and HCPGIR453W after editing user direct We are talking about a hipervisor running (nominally) directly on the hardware - not a user-space application like VBox. In my naivety I would expect z/VM to be *very* aware of an interrupt for a guest IPL. If there are changes in the (z/VM) environment why wouldn't they resolved immediately at that point ?. It's all "smoke and mirrors" after all. Principle of least astonishment should prevail IMHO. Shane ... -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ ÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n k a n g e h e i m e i n f o r m a t i e b e v a t t e n e n k e l b e s t e m d v o o r d e g e a d r e s s e e r d e . I n d i e n d i t b e r i c h t n i e t v o o r u i s b e s t e m d , v e r z o e k e n w i j u d i t o n m i d d e l l i j k a a n o n s t e m e l d e n e n h e t b e r i c h t t e v e r n i e t i g e n . A a n g e z i e n d e i n t e g r i t e i t v a n h e t b e r i c h t n i e t v e i l i g g e s t e l d i s m i d d e l s v e r z e n d i n g v i a i n t e r n e t , k a n A t o s O r i g i n n i e t a a n s p r a k e l i j k w o r d e n g e h o u d e n v o o r d e i n h o u d d a a r v a n . H o e w e l w i j o n s i n s p a n n e n e e n v i r u s v r i j n e t w e r k t e h a n t e r e n , g e v e n w i j g e e n e n k e l e g a r a n t i e d a t d i t b e r i c h t v i r u s v r i j i s , n o c h a a n v a a r d e n w i j e n i g e a a n s p r a k e l i j k h e i d v o o r d e m o g e l i j k e a a n w e z i g h e i d v a n e e n v i r u s i n d i t b e r i c h t . O p a l o n z e r e c h t s v e r h o u d i n g e n , a a n b i e d i n g e n e n o v e r e e n k o m s t e n w a a r o n d e r A t o s O r i g i n g o e d e r e n e n / o f d i e n s t e n l e v e r t z i j n m e t u i t s l u i t i n g v a n a l l e a n d e r e v o o r w a a r d e n d e L e v e r i n g s v o o r w a a r d e n v a n A t o s O r i g i n v a n t o e p a s s i n g . D e z e w o r d e n u o p a a n v r a a g d i r e c t k o s t e l o o s t o e g e z o n d e n . T h i s e - m a i l a n d t h e d o c u m e n t s a t t a c h e d a r e c o n f i d e n t i a l a n d i n t e n d e d s o l e l y f o r t h e a d d r e s s e e ; i t m a y a l s o b e p r i v i l e g e d . I f y o u r e c e i v e t h i s e - m a i l i n e r r o r , p l e a s e n o t i f y t h e s e n d e r i m m e d i a t e l y a n d d e s t r o y i t . A s i t s i n t e g r i t y c a n n o t b e s e c u r e d o n t h e I n t e r n e t , t h e A t o s O r i g i n g r o u p l i a b i l i t y c a n n o t b e t r i g g e r e d f o r t h e m e s s a g e c o n t e n t . A l t h o u g h t h e s e n d e r e n d e a v o u r s t o m a i n t a i n a c o m p u t e r v i r u s - f r e e n e t w o r k , t h e s e n d e r d o e s n o t w a r r a n t t h a t t h i s t r a n s m i s s i o n i s v i r u s - f r e e a n d w i l l n o t b e l i a b l e f o r a n y d a m a g e s r e s u l t i n g f r o m a n y v i r u s t r a n s m i t t e d . O n a l l o f f e r s a n d a g r e e m e n t s u n d e r w h i c h A t o s O r i g i n s u p p l i e s g o o d s a n d / o r s e r v
Re: HCPGIR450W and HCPGIR453W after editing user direct
Alan, Indeed I should have said LOGOFF/LOGON instead of IPL the guest. The instruction Koray used was "IPL VM" to activate the changes. As far as I know we do not have to IPL VM every time the directory changes. And I can't even remember when we performed a POR. Regards, Berry. -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Alan Altmark Sent: vrijdag 5 november 2010 1:57 To: LINUX-390@VM.MARIST.EDU Subject: Re: HCPGIR450W and HCPGIR453W after editing user direct > Actually you didn't need to IPL VM. Once you put the directory online > it is available. So delete the IPL step from the instruction. Or > change the instruction, do not IPL VM, IPL the guest (either xautolog or logon). At LOGON time, certain parts of the user's directory entry are cached and other parts are not. Unless you are very familiar with those details, you will want to LOGOFF the guest and LOGON again to pick up the directory changes. IPL of a guest is not sufficient to pick up a directory change. Alan Altmark -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ ÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n k a n g e h e i m e i n f o r m a t i e b e v a t t e n e n k e l b e s t e m d v o o r d e g e a d r e s s e e r d e . I n d i e n d i t b e r i c h t n i e t v o o r u i s b e s t e m d , v e r z o e k e n w i j u d i t o n m i d d e l l i j k a a n o n s t e m e l d e n e n h e t b e r i c h t t e v e r n i e t i g e n . A a n g e z i e n d e i n t e g r i t e i t v a n h e t b e r i c h t n i e t v e i l i g g e s t e l d i s m i d d e l s v e r z e n d i n g v i a i n t e r n e t , k a n A t o s O r i g i n n i e t a a n s p r a k e l i j k w o r d e n g e h o u d e n v o o r d e i n h o u d d a a r v a n . H o e w e l w i j o n s i n s p a n n e n e e n v i r u s v r i j n e t w e r k t e h a n t e r e n , g e v e n w i j g e e n e n k e l e g a r a n t i e d a t d i t b e r i c h t v i r u s v r i j i s , n o c h a a n v a a r d e n w i j e n i g e a a n s p r a k e l i j k h e i d v o o r d e m o g e l i j k e a a n w e z i g h e i d v a n e e n v i r u s i n d i t b e r i c h t . O p a l o n z e r e c h t s v e r h o u d i n g e n , a a n b i e d i n g e n e n o v e r e e n k o m s t e n w a a r o n d e r A t o s O r i g i n g o e d e r e n e n / o f d i e n s t e n l e v e r t z i j n m e t u i t s l u i t i n g v a n a l l e a n d e r e v o o r w a a r d e n d e L e v e r i n g s v o o r w a a r d e n v a n A t o s O r i g i n v a n t o e p a s s i n g . D e z e w o r d e n u o p a a n v r a a g d i r e c t k o s t e l o o s t o e g e z o n d e n . T h i s e - m a i l a n d t h e d o c u m e n t s a t t a c h e d a r e c o n f i d e n t i a l a n d i n t e n d e d s o l e l y f o r t h e a d d r e s s e e ; i t m a y a l s o b e p r i v i l e g e d . I f y o u r e c e i v e t h i s e - m a i l i n e r r o r , p l e a s e n o t i f y t h e s e n d e r i m m e d i a t e l y a n d d e s t r o y i t . A s i t s i n t e g r i t y c a n n o t b e s e c u r e d o n t h e I n t e r n e t , t h e A t o s O r i g i n g r o u p l i a b i l i t y c a n n o t b e t r i g g e r e d f o r t h e m e s s a g e c o n t e n t . A l t h o u g h t h e s e n d e r e n d e a v o u r s t o m a i n t a i n a c o m p u t e r v i r u s - f r e e n e t w o r k , t h e s e n d e r d o e s n o t w a r r a n t t h a t t h i s t r a n s m i s s i o n i s v i r u s - f r e e a n d w i l l n o t b e l i a b l e f o r a n y d a m a g e s r e s u l t i n g f r o m a n y v i r u s t r a n s m i t t e d . O n a l l o f f e r s a n d a g r e e m e n t s u n d e r w h i c h A t o s O r i g i n s u p p l i e s g o o d s a n d / o r s e r v i c e s o f w h a t e v e r n a t u r e , t h e T e r m s o f D e l i v e r y f r o m A t o s O r i g i n e x c l u s i v e l y a p p l y . T h e T e r m s o f D e l i v e r y s h a l l b e p r o m p t l y s u b m i t t e d t o y o u o n y o u r r e q u e s t . A t o s O r i g i n N e d e r l a n
Re: HCPGIR450W and HCPGIR453W after editing user direct
Hi Sorry, are you sure modifying the active directory? Atte José María Fernández Domingo Tecnocom Norte -Mensaje original- De: Linux on 390 Port [mailto:linux-...@vm.marist.edu] En nombre de koray Enviado el: jueves, 04 de noviembre de 2010 20:32 Para: LINUX-390@VM.MARIST.EDU Asunto: HCPGIR450W and HCPGIR453W after editing user direct Hello all, We have 14 Sles Guests running on Z/VM 5.4. We edited the user direct file and changed the memory settings of Linux guests.For example; linux001 - 2048M 4096M linux002 - 2048M 4096M has changed to linux001 - 3072M 6144M linux002 - 1024M 2048M Now, i cant ipl my guest's. When i try to ipl from minidisk 100, linux 001 says: HCPGIR453W CP Entered, program interrupt loop. linux002 says: HCPGIR450W CP entered, disabled wait PSW 00020001 8000 001536B0 It seems disk mapping are broken but i'm totally sure that i only changed Memory settings, not touched minidisk settings. Need your help please. Regards -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
