Re: Slow YAST Response
On Dec 8, 2015, at 9:34 AM, Michael Weiner wrote: > Has anyone experience a slow YAST response? I had this experience if my guest had insufficient storage. ISTR the transition from SLES10 to SLES11 meant we needed 384 MB storage, instead of 256 MB, in order to survive YaST2 during installation. The extra 128 MB meant the difference between an hours-long install, and a fraction-of-an-hour-long install. 256 MB was adequate for a minimum system _after_ the install, however (I never tried to use YaST2 outside of the install process). ok bear. -- until further notice -- 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: Slow YAST Response
No problems here, also on 11 sp3 (at very current maintenance). are you using the X version or the ncurses one? -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Michael Weiner Sent: Tuesday, December 08, 2015 9:35 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] Slow YAST Response Hello all. Has anyone experience a slow YAST response? For example, I am navigating through the partitioner and it is extremely slow. It takes a long time too load and a long time to do anything really. Any suggestions? I am running on z/VM SLES 11 SP3 -- Michael Weiner Systems Admin Infinity Systems Software, Inc. One Penn Plaza Suite 2010 New York, NY 10119 o: (646) 405-9300 c: (845) 641-0517 -- 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: FEDORA F23 and KDE
On Tue, 8 Dec 2015 14:04:15 -0800 Tom Huegel wrote: > When I try to do this: > [root@fedora ~]# dnf groupinstall "KDE Plasma Workspaces" > > I get this: > Last metadata expiration check performed 2:55:39 ago on Tue Dec 8 > 14:04:18 > 2015. > Error: nothing provides plasmashell >= 5.4 needed by > plasma-workspace-5.4.2-4.fc23.s390. > nothing provides pulseaudio-module-bluetooth needed by > bluedevil-5.4.2-1.fc23.s390. > package sddm-breeze-5.4.2-4.fc23.noarch requires plasma-workspace = > 5.4.2-4.fc23, but none of the providers can be installed. > nothing provides plasmashell >= 5.4 needed by > plasma-workspace-5.4.2-4.fc23.s390x. > nothing provides plasmashell >= 5.4 needed by > plasma-workspace-5.4.2-4.fc23.s390 > (try to add '--allowerasing' to command line to replace conflicting > packages) > > I searched but can't find any clue as how to fix it. it's a problem on our side, the KDE is missing couple packages built in the required versions. Our focus is more on the server side packages. But as I see there is a user, we will fix it. So, please, stay tuned :-) Dan -- 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/
FEDORA F23 and KDE
When I try to do this: [root@fedora ~]# dnf groupinstall "KDE Plasma Workspaces" I get this: Last metadata expiration check performed 2:55:39 ago on Tue Dec 8 14:04:18 2015. Error: nothing provides plasmashell >= 5.4 needed by plasma-workspace-5.4.2-4.fc23.s390. nothing provides pulseaudio-module-bluetooth needed by bluedevil-5.4.2-1.fc23.s390. package sddm-breeze-5.4.2-4.fc23.noarch requires plasma-workspace = 5.4.2-4.fc23, but none of the providers can be installed. nothing provides plasmashell >= 5.4 needed by plasma-workspace-5.4.2-4.fc23.s390x. nothing provides plasmashell >= 5.4 needed by plasma-workspace-5.4.2-4.fc23.s390 (try to add '--allowerasing' to command line to replace conflicting packages) I searched but can't find any clue as how to fix it. Any ideas? Thanks Tom -- 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/
Slow YAST Response
Hello all. Has anyone experience a slow YAST response? For example, I am navigating through the partitioner and it is extremely slow. It takes a long time too load and a long time to do anything really. Any suggestions? I am running on z/VM SLES 11 SP3 -- Michael Weiner Systems Admin Infinity Systems Software, Inc. One Penn Plaza Suite 2010 New York, NY 10119 o: (646) 405-9300 c: (845) 641-0517 -- 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: FEDORA 23 install issue
Dan/Jan, I tried Jan's suggestion and replaced root=live: https://dl.fedoraproject.org/pub/fedora-secondary/releases/23/Server/s390x/os/images/install.img with: inst.repo= https://dl.fedoraproject.org/pub/fedora-secondary/releases/23/Server/s390x/os/ Now it is working.. Thanks On Tue, Dec 8, 2015 at 8:43 AM, Dan Horák wrote: > On Tue, 8 Dec 2015 08:25:12 -0800 > Tom Huegel wrote: > > > Dan, > > That line is OK, it is just the display that looks funky. > > ah, then the mail client :-) > > But do you have more of the logs? I can't see an other error in the > parts you posted. > > > Dan > > > I get the error after several screens of this: > > [ [32m OK [0m] Started Show Plymouth Boot > > Screen. > > > > [ [32m OK [0m] Reached target > > Paths. > > > > [ [32m OK [0m] Reached target Basic > > System. > > > > [ 27.999173] dracut-initqueue[719]: % Total% Received % Xferd > > Average Speed TimeTime Time Current > > [ 27.999768] dracut-initqueue[719]: Dload Upload Total Spent > > Left Speed > > [ 52.072388] dracut-initqueue[719]: 0 00 00 0 > > 0 0 --:--:-- --:--:-- --:--:-- 0 0 00 > > 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 > > 0 0 00 0 0 0 --:--:-- 0:00:01 --:--: > > -- 0 0 00 00 0 0 0 --:--:-- > > 0:00:02 > > --:--:-- 0 0 00 00 0 0 > > 0 --:--:-- 0:00:03 --:--:-- 0 0 00 00 0 > > 0 0 --:--:-- 0:00:04 --:--:-- 0 0 00 > > 00 0 0 0 --:--:-- 0:00:05 --:--:-- 0 0 0 > > 0 00 0 0 0 --:--:-- 0:00:06 --:--:- > > - 0 0 00 00 0 0 0 --:--:-- > > 0:00:07 > > --:--:-- 0 0 260M0 491520 0 6083 0 > > 12:27:36 0:00:08 12:27:28 10080 0 260M0 784k0 0 > > 88874 0 0:51:10 0:00:09 0:51:01 162k 0 260M0 1616 > > k0 0 161k 0 0:27:30 0:00:10 0:27:20 336k 0 > > 260M0 2256k0 0 204k 0 0:21:39 0:00:11 0:21:28 > > 470k 0 260M0 2608k0 0 215k 0 0:20:37 0:00:12 > > 0:20:25 510k 1 260M1 2896k0 0 222k 0 > > > > On Tue, Dec 8, 2015 at 7:53 AM, Dan Horák wrote: > > > > > On Tue, 8 Dec 2015 07:22:21 -0800 > > > Tom Huegel wrote: > > > > > > > I am trying to do a z/VM install of F23 via a virtual reader IPL. > > > > This worked with F21. > > > > > > > > Here is the error. > > > > > > > > [ 565.043571] fedora.hds.com audit[1]: SERVICE_START pid=1 uid=0 > > > > auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-initqu > > > > eue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? > > > > addr=? terminal=? res=success' > > > > [ 565.043705] fedora.hds.com systemd[1]: Reached target Remote > > > > File Systems (Pre). > > > > [ 565.043840] fedora.hds.com systemd[1]: Starting Remote File > > > > Systems (Pre). > > > > [ 565.043964] fedora.hds.com systemd[1]: Reached target Remote > > > > File Systems. > > > > [ 565.044090] fedora.hds.com systemd[1]: Starting Remote File > > > > Systems. > > > > [ 565.044223] fedora.hds.com systemd[1]: Starting dracut > > > > pre-mount hook... > > > > [ 565.053115] fedora.hds.com systemd[1]: Started dracut pre-mount > > > > hook. > > > > [ 565.053155] fedora.hds.com audit[1]: SERVICE_START pid=1 uid=0 > > > > auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-pre-mo > > > > unt comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? > > > > addr=? terminal=? res=success' > > > > [ 565.053290] fedora.hds.com systemd[1]: Mounting > > > > /sysroot... > > > > > > > > [ 565.049012] fedora.hds.com kernel: audit: type=1130 > > > > audit(1449584485.950:15): pid=1 uid=0 auid=4294967295 > > > > ses=4294967295 subj=ker > > > > nel msg='unit=dracut-pre-mount comm="systemd" > > > > exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? > > > > res=success' > > > > [ 565.057205] fedora.hds.com mount[1449]: mount.nfs: Failed to > > > > resolve server live: No address associated with hostname > > > > [ 565.057779] fedora.hds.com systemd[1]: sysroot.mount: Mount > > > > process exited, code=exited status=32 > > > > [ 565.057911] fedora.hds.com systemd[1]: Failed to mount > > > > /sysroot. > > > > [ 565.058037] fedora.hds.com systemd[1]: Dependency failed for > > > > Initrd Root File System. > > > > [ 565.058164] fedora.hds.com systemd[1]: Dependency failed for > > > > Reload Configuration from the Real Root. > > > > [ 565.058297] fedora.hds.com systemd[1]: > > > > initrd-parse-etc.service: Job initrd-parse-etc.service/start > > > > failed with result 'dependenc y'. > > > > > > > > [ 565.058425] fedora.hds.com systemd[1]: > > > > initrd-parse-etc.service: Triggering OnFailure= dependencies. > > > > [ 565.058580] fedora.hds.com systemd[1]: initrd-root-fs.target: > > > > Job initrd-root-fs.target/start fail
Re: FEDORA 23 install issue
On Tue, 8 Dec 2015 08:25:12 -0800 Tom Huegel wrote: > Dan, > That line is OK, it is just the display that looks funky. ah, then the mail client :-) But do you have more of the logs? I can't see an other error in the parts you posted. Dan > I get the error after several screens of this: > [ [32m OK [0m] Started Show Plymouth Boot > Screen. > > [ [32m OK [0m] Reached target > Paths. > > [ [32m OK [0m] Reached target Basic > System. > > [ 27.999173] dracut-initqueue[719]: % Total% Received % Xferd > Average Speed TimeTime Time Current > [ 27.999768] dracut-initqueue[719]: Dload Upload Total Spent > Left Speed > [ 52.072388] dracut-initqueue[719]: 0 00 00 0 > 0 0 --:--:-- --:--:-- --:--:-- 0 0 00 > 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 > 0 0 00 0 0 0 --:--:-- 0:00:01 --:--: > -- 0 0 00 00 0 0 0 --:--:-- > 0:00:02 > --:--:-- 0 0 00 00 0 0 > 0 --:--:-- 0:00:03 --:--:-- 0 0 00 00 0 > 0 0 --:--:-- 0:00:04 --:--:-- 0 0 00 > 00 0 0 0 --:--:-- 0:00:05 --:--:-- 0 0 0 > 0 00 0 0 0 --:--:-- 0:00:06 --:--:- > - 0 0 00 00 0 0 0 --:--:-- > 0:00:07 > --:--:-- 0 0 260M0 491520 0 6083 0 > 12:27:36 0:00:08 12:27:28 10080 0 260M0 784k0 0 > 88874 0 0:51:10 0:00:09 0:51:01 162k 0 260M0 1616 > k0 0 161k 0 0:27:30 0:00:10 0:27:20 336k 0 > 260M0 2256k0 0 204k 0 0:21:39 0:00:11 0:21:28 > 470k 0 260M0 2608k0 0 215k 0 0:20:37 0:00:12 > 0:20:25 510k 1 260M1 2896k0 0 222k 0 > > On Tue, Dec 8, 2015 at 7:53 AM, Dan Horák wrote: > > > On Tue, 8 Dec 2015 07:22:21 -0800 > > Tom Huegel wrote: > > > > > I am trying to do a z/VM install of F23 via a virtual reader IPL. > > > This worked with F21. > > > > > > Here is the error. > > > > > > [ 565.043571] fedora.hds.com audit[1]: SERVICE_START pid=1 uid=0 > > > auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-initqu > > > eue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? > > > addr=? terminal=? res=success' > > > [ 565.043705] fedora.hds.com systemd[1]: Reached target Remote > > > File Systems (Pre). > > > [ 565.043840] fedora.hds.com systemd[1]: Starting Remote File > > > Systems (Pre). > > > [ 565.043964] fedora.hds.com systemd[1]: Reached target Remote > > > File Systems. > > > [ 565.044090] fedora.hds.com systemd[1]: Starting Remote File > > > Systems. > > > [ 565.044223] fedora.hds.com systemd[1]: Starting dracut > > > pre-mount hook... > > > [ 565.053115] fedora.hds.com systemd[1]: Started dracut pre-mount > > > hook. > > > [ 565.053155] fedora.hds.com audit[1]: SERVICE_START pid=1 uid=0 > > > auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-pre-mo > > > unt comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? > > > addr=? terminal=? res=success' > > > [ 565.053290] fedora.hds.com systemd[1]: Mounting > > > /sysroot... > > > > > > [ 565.049012] fedora.hds.com kernel: audit: type=1130 > > > audit(1449584485.950:15): pid=1 uid=0 auid=4294967295 > > > ses=4294967295 subj=ker > > > nel msg='unit=dracut-pre-mount comm="systemd" > > > exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? > > > res=success' > > > [ 565.057205] fedora.hds.com mount[1449]: mount.nfs: Failed to > > > resolve server live: No address associated with hostname > > > [ 565.057779] fedora.hds.com systemd[1]: sysroot.mount: Mount > > > process exited, code=exited status=32 > > > [ 565.057911] fedora.hds.com systemd[1]: Failed to mount > > > /sysroot. > > > [ 565.058037] fedora.hds.com systemd[1]: Dependency failed for > > > Initrd Root File System. > > > [ 565.058164] fedora.hds.com systemd[1]: Dependency failed for > > > Reload Configuration from the Real Root. > > > [ 565.058297] fedora.hds.com systemd[1]: > > > initrd-parse-etc.service: Job initrd-parse-etc.service/start > > > failed with result 'dependenc y'. > > > > > > [ 565.058425] fedora.hds.com systemd[1]: > > > initrd-parse-etc.service: Triggering OnFailure= dependencies. > > > [ 565.058580] fedora.hds.com systemd[1]: initrd-root-fs.target: > > > Job initrd-root-fs.target/start failed with result 'dependency'. > > > [ 565.058714] fedora.hds.com systemd[1]: initrd-root-fs.target: > > > Triggering OnFailure= dependencies. > > > [ 565.058843] fedora.hds.com systemd[1]: sysroot.mount: Unit > > > entered failed state. > > > [ 565.058967] fedora.hds.com systemd[1]: Stopped dracut > > > pre-pivot and cleanup hook. > > > > > > Here is my PRM file. I haven't been able to find any doc that > > > something has changed. > > > > > > ro ramdisk_size=4 cio_ignore=all,!0.0.0009 > > > vnc > > > rd.dasd=0.0.0250,25
Re: FEDORA 23 install issue
Hi, does it work if you replace: root=live:https://dl.fedoraproject.org/pub/fedora-secondary/releases/23/Server/s390x/os/images/install.img with: inst.repo=https://dl.fedoraproject.org/pub/fedora-secondary/releases/23/Server/s390x/os/ ? On 8.12.2015 16:22, Tom Huegel wrote: I am trying to do a z/VM install of F23 via a virtual reader IPL. This worked with F21. Here is the error. [ 565.043571] fedora.hds.com audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-initqu eue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 565.043705] fedora.hds.com systemd[1]: Reached target Remote File Systems (Pre). [ 565.043840] fedora.hds.com systemd[1]: Starting Remote File Systems (Pre). [ 565.043964] fedora.hds.com systemd[1]: Reached target Remote File Systems. [ 565.044090] fedora.hds.com systemd[1]: Starting Remote File Systems. [ 565.044223] fedora.hds.com systemd[1]: Starting dracut pre-mount hook... [ 565.053115] fedora.hds.com systemd[1]: Started dracut pre-mount hook. [ 565.053155] fedora.hds.com audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-pre-mo unt comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 565.053290] fedora.hds.com systemd[1]: Mounting /sysroot... [ 565.049012] fedora.hds.com kernel: audit: type=1130 audit(1449584485.950:15): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=ker nel msg='unit=dracut-pre-mount comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 565.057205] fedora.hds.com mount[1449]: mount.nfs: Failed to resolve server live: No address associated with hostname [ 565.057779] fedora.hds.com systemd[1]: sysroot.mount: Mount process exited, code=exited status=32 [ 565.057911] fedora.hds.com systemd[1]: Failed to mount /sysroot. [ 565.058037] fedora.hds.com systemd[1]: Dependency failed for Initrd Root File System. [ 565.058164] fedora.hds.com systemd[1]: Dependency failed for Reload Configuration from the Real Root. [ 565.058297] fedora.hds.com systemd[1]: initrd-parse-etc.service: Job initrd-parse-etc.service/start failed with result 'dependenc y'. [ 565.058425] fedora.hds.com systemd[1]: initrd-parse-etc.service: Triggering OnFailure= dependencies. [ 565.058580] fedora.hds.com systemd[1]: initrd-root-fs.target: Job initrd-root-fs.target/start failed with result 'dependency'. [ 565.058714] fedora.hds.com systemd[1]: initrd-root-fs.target: Triggering OnFailure= dependencies. [ 565.058843] fedora.hds.com systemd[1]: sysroot.mount: Unit entered failed state. [ 565.058967] fedora.hds.com systemd[1]: Stopped dracut pre-pivot and cleanup hook. Here is my PRM file. I haven't been able to find any doc that something has changed. ro ramdisk_size=4 cio_ignore=all,!0.0.0009 vnc rd.dasd=0.0.0250,251,252,253,254,255 rd.dasd=0.0.025f ip=172.17.51.126::172.17.50.1:255.255.254.0:fedora.hds.com:enccw0.0.0340:none rd.znet=qeth,0.0.0340,0.0.0341,0.0.0342,layer2=0,portno=0 http_proxy=http://thuegel:p...@xx.xx.xx.xx:8080 proxy=http://thuegel:p...@xx.xx.xx.xx:8080 root=live: https://dl.fedoraproject.org/pub/fedora-secondary/releases/23/Server/s 390x/os/images/install.img nameserver=xx.xx.xx.xx Has anyone seen this? Thanks Tom -- 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: FEDORA 23 install issue
Dan, That line is OK, it is just the display that looks funky. I get the error after several screens of this: [ [32m OK [0m] Started Show Plymouth Boot Screen. [ [32m OK [0m] Reached target Paths. [ [32m OK [0m] Reached target Basic System. [ 27.999173] dracut-initqueue[719]: % Total% Received % Xferd Average Speed TimeTime Time Current [ 27.999768] dracut-initqueue[719]: Dload Upload Total Spent Left Speed [ 52.072388] dracut-initqueue[719]: 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 00 0 0 0 --:--:-- 0:00:01 --:--: -- 0 0 00 00 0 0 0 --:--:-- 0:00:02 --:--:-- 0 0 00 00 0 0 0 --:--:-- 0:00:03 --:--:-- 0 0 00 00 0 0 0 --:--:-- 0:00:04 --:--:-- 0 0 00 00 0 0 0 --:--:-- 0:00:05 --:--:-- 0 0 0 0 00 0 0 0 --:--:-- 0:00:06 --:--:- - 0 0 00 00 0 0 0 --:--:-- 0:00:07 --:--:-- 0 0 260M0 491520 0 6083 0 12:27:36 0:00:08 12:27:28 10080 0 260M0 784k0 0 88874 0 0:51:10 0:00:09 0:51:01 162k 0 260M0 1616 k0 0 161k 0 0:27:30 0:00:10 0:27:20 336k 0 260M0 2256k0 0 204k 0 0:21:39 0:00:11 0:21:28 470k 0 260M0 2608k0 0 215k 0 0:20:37 0:00:12 0:20:25 510k 1 260M1 2896k0 0 222k 0 On Tue, Dec 8, 2015 at 7:53 AM, Dan Horák wrote: > On Tue, 8 Dec 2015 07:22:21 -0800 > Tom Huegel wrote: > > > I am trying to do a z/VM install of F23 via a virtual reader IPL. This > > worked with F21. > > > > Here is the error. > > > > [ 565.043571] fedora.hds.com audit[1]: SERVICE_START pid=1 uid=0 > > auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-initqu > > eue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? > > terminal=? res=success' > > [ 565.043705] fedora.hds.com systemd[1]: Reached target Remote File > > Systems (Pre). > > [ 565.043840] fedora.hds.com systemd[1]: Starting Remote File Systems > > (Pre). > > [ 565.043964] fedora.hds.com systemd[1]: Reached target Remote File > > Systems. > > [ 565.044090] fedora.hds.com systemd[1]: Starting Remote File > > Systems. > > [ 565.044223] fedora.hds.com systemd[1]: Starting dracut pre-mount > > hook... > > [ 565.053115] fedora.hds.com systemd[1]: Started dracut pre-mount > > hook. > > [ 565.053155] fedora.hds.com audit[1]: SERVICE_START pid=1 uid=0 > > auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-pre-mo > > unt comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? > > terminal=? res=success' > > [ 565.053290] fedora.hds.com systemd[1]: Mounting > > /sysroot... > > > > [ 565.049012] fedora.hds.com kernel: audit: type=1130 > > audit(1449584485.950:15): pid=1 uid=0 auid=4294967295 ses=4294967295 > > subj=ker > > nel msg='unit=dracut-pre-mount comm="systemd" > > exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? > > res=success' > > [ 565.057205] fedora.hds.com mount[1449]: mount.nfs: Failed to > > resolve server live: No address associated with hostname > > [ 565.057779] fedora.hds.com systemd[1]: sysroot.mount: Mount process > > exited, code=exited status=32 > > [ 565.057911] fedora.hds.com systemd[1]: Failed to mount > > /sysroot. > > [ 565.058037] fedora.hds.com systemd[1]: Dependency failed for > > Initrd Root File System. > > [ 565.058164] fedora.hds.com systemd[1]: Dependency failed for Reload > > Configuration from the Real Root. > > [ 565.058297] fedora.hds.com systemd[1]: initrd-parse-etc.service: > > Job initrd-parse-etc.service/start failed with result 'dependenc > > y'. > > > > [ 565.058425] fedora.hds.com systemd[1]: initrd-parse-etc.service: > > Triggering OnFailure= dependencies. > > [ 565.058580] fedora.hds.com systemd[1]: initrd-root-fs.target: Job > > initrd-root-fs.target/start failed with result 'dependency'. > > [ 565.058714] fedora.hds.com systemd[1]: initrd-root-fs.target: > > Triggering OnFailure= dependencies. > > [ 565.058843] fedora.hds.com systemd[1]: sysroot.mount: Unit entered > > failed state. > > [ 565.058967] fedora.hds.com systemd[1]: Stopped dracut pre-pivot and > > cleanup hook. > > > > Here is my PRM file. I haven't been able to find any doc that > > something has changed. > > > > ro ramdisk_size=4 cio_ignore=all,!0.0.0009 > > vnc > > rd.dasd=0.0.0250,251,252,253,254,255 > > rd.dasd=0.0.025f > > ip=172.17.51.126::172.17.50.1:255.255.254.0:fedora.hds.com: > enccw0.0.0340:none > > > > rd.znet=qeth,0.0.0340,0.0.0341,0.0.0342,layer2=0,portno=0 > > > > http_proxy=http://thuegel:p...@xx.xx.xx.xx:8080 > > proxy=http://thuegel:p...@xx.xx.xx.xx:8080 > > root=live: > > https://dl.fedoraproject.org/pub/fedora-secondary/releases/23/Server/s > > 390x/os/images
Re: Question on EDEV devides and DIRMAINT
On Tuesday, 12/08/2015 at 02:46 GMT, Bruce Hayden wrote: > Note that CPFMTXA refers to the blocks on FB-512 disks as "pages" and there > are 8 blocks in a page. So the reserved area at the start of a FB-512 > volume is 4 pages but 32 blocks. In EXTENT CONTROL, you'd start at 32, not > 4. > > But - EXTENT CONTROL allows a keyword "Start" for the beginning > allocation. It translates to 1 for ECKD and 32 for FB-512. So, just code > your regions as "START END" and you've allocated the entire pack. > > Note 1: DIRMAINT won't allocate minidisk starting below the "Start" value > anyway, so if you would code 0 or 4 (for FBA), no worries. > > Note 2: You'll probably want to create your own device type in the > :Defaults. section at the end of the file that specifies how many blocks > your LUNs have. Otherwise, Dirmaint will default to the very small 9336. > For instance, for my 10 GB LUNs on my test system, I have "BIGEDEV > 20971520" in the defaults section. (Maybe 10 GB isn't "big" any more..) Much appreciated, Bruce! I should have remembered about blocks v. pages. (sigh) And while DIRMAINT may treat '1' as '32', that doesn't help the humans learn about the difference between FBA and ECKD. Code it as 32. Alan Altmark Senior Managing z/VM and Linux Consultant Lab Services System z Delivery Practice IBM Systems & Technology Group ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 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: FEDORA 23 install issue
On Tue, 8 Dec 2015 07:22:21 -0800 Tom Huegel wrote: > I am trying to do a z/VM install of F23 via a virtual reader IPL. This > worked with F21. > > Here is the error. > > [ 565.043571] fedora.hds.com audit[1]: SERVICE_START pid=1 uid=0 > auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-initqu > eue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? > terminal=? res=success' > [ 565.043705] fedora.hds.com systemd[1]: Reached target Remote File > Systems (Pre). > [ 565.043840] fedora.hds.com systemd[1]: Starting Remote File Systems > (Pre). > [ 565.043964] fedora.hds.com systemd[1]: Reached target Remote File > Systems. > [ 565.044090] fedora.hds.com systemd[1]: Starting Remote File > Systems. > [ 565.044223] fedora.hds.com systemd[1]: Starting dracut pre-mount > hook... > [ 565.053115] fedora.hds.com systemd[1]: Started dracut pre-mount > hook. > [ 565.053155] fedora.hds.com audit[1]: SERVICE_START pid=1 uid=0 > auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-pre-mo > unt comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? > terminal=? res=success' > [ 565.053290] fedora.hds.com systemd[1]: Mounting > /sysroot... > > [ 565.049012] fedora.hds.com kernel: audit: type=1130 > audit(1449584485.950:15): pid=1 uid=0 auid=4294967295 ses=4294967295 > subj=ker > nel msg='unit=dracut-pre-mount comm="systemd" > exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? > res=success' > [ 565.057205] fedora.hds.com mount[1449]: mount.nfs: Failed to > resolve server live: No address associated with hostname > [ 565.057779] fedora.hds.com systemd[1]: sysroot.mount: Mount process > exited, code=exited status=32 > [ 565.057911] fedora.hds.com systemd[1]: Failed to mount > /sysroot. > [ 565.058037] fedora.hds.com systemd[1]: Dependency failed for > Initrd Root File System. > [ 565.058164] fedora.hds.com systemd[1]: Dependency failed for Reload > Configuration from the Real Root. > [ 565.058297] fedora.hds.com systemd[1]: initrd-parse-etc.service: > Job initrd-parse-etc.service/start failed with result 'dependenc > y'. > > [ 565.058425] fedora.hds.com systemd[1]: initrd-parse-etc.service: > Triggering OnFailure= dependencies. > [ 565.058580] fedora.hds.com systemd[1]: initrd-root-fs.target: Job > initrd-root-fs.target/start failed with result 'dependency'. > [ 565.058714] fedora.hds.com systemd[1]: initrd-root-fs.target: > Triggering OnFailure= dependencies. > [ 565.058843] fedora.hds.com systemd[1]: sysroot.mount: Unit entered > failed state. > [ 565.058967] fedora.hds.com systemd[1]: Stopped dracut pre-pivot and > cleanup hook. > > Here is my PRM file. I haven't been able to find any doc that > something has changed. > > ro ramdisk_size=4 cio_ignore=all,!0.0.0009 > vnc > rd.dasd=0.0.0250,251,252,253,254,255 > rd.dasd=0.0.025f > ip=172.17.51.126::172.17.50.1:255.255.254.0:fedora.hds.com:enccw0.0.0340:none > > rd.znet=qeth,0.0.0340,0.0.0341,0.0.0342,layer2=0,portno=0 > > http_proxy=http://thuegel:p...@xx.xx.xx.xx:8080 > proxy=http://thuegel:p...@xx.xx.xx.xx:8080 > root=live: > https://dl.fedoraproject.org/pub/fedora-secondary/releases/23/Server/s > 390x/os/images/install.img isn't there a new-line or spaces between the "live:" and "https://..."; strings? It must be one string, eventually split into 80 character lines. Or did just the mail client mangled it? Dan > nameserver=xx.xx.xx.xx > > Has anyone seen this? > Thanks > Tom > > -- > 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/
FEDORA 23 install issue
I am trying to do a z/VM install of F23 via a virtual reader IPL. This worked with F21. Here is the error. [ 565.043571] fedora.hds.com audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-initqu eue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 565.043705] fedora.hds.com systemd[1]: Reached target Remote File Systems (Pre). [ 565.043840] fedora.hds.com systemd[1]: Starting Remote File Systems (Pre). [ 565.043964] fedora.hds.com systemd[1]: Reached target Remote File Systems. [ 565.044090] fedora.hds.com systemd[1]: Starting Remote File Systems. [ 565.044223] fedora.hds.com systemd[1]: Starting dracut pre-mount hook... [ 565.053115] fedora.hds.com systemd[1]: Started dracut pre-mount hook. [ 565.053155] fedora.hds.com audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-pre-mo unt comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 565.053290] fedora.hds.com systemd[1]: Mounting /sysroot... [ 565.049012] fedora.hds.com kernel: audit: type=1130 audit(1449584485.950:15): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=ker nel msg='unit=dracut-pre-mount comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 565.057205] fedora.hds.com mount[1449]: mount.nfs: Failed to resolve server live: No address associated with hostname [ 565.057779] fedora.hds.com systemd[1]: sysroot.mount: Mount process exited, code=exited status=32 [ 565.057911] fedora.hds.com systemd[1]: Failed to mount /sysroot. [ 565.058037] fedora.hds.com systemd[1]: Dependency failed for Initrd Root File System. [ 565.058164] fedora.hds.com systemd[1]: Dependency failed for Reload Configuration from the Real Root. [ 565.058297] fedora.hds.com systemd[1]: initrd-parse-etc.service: Job initrd-parse-etc.service/start failed with result 'dependenc y'. [ 565.058425] fedora.hds.com systemd[1]: initrd-parse-etc.service: Triggering OnFailure= dependencies. [ 565.058580] fedora.hds.com systemd[1]: initrd-root-fs.target: Job initrd-root-fs.target/start failed with result 'dependency'. [ 565.058714] fedora.hds.com systemd[1]: initrd-root-fs.target: Triggering OnFailure= dependencies. [ 565.058843] fedora.hds.com systemd[1]: sysroot.mount: Unit entered failed state. [ 565.058967] fedora.hds.com systemd[1]: Stopped dracut pre-pivot and cleanup hook. Here is my PRM file. I haven't been able to find any doc that something has changed. ro ramdisk_size=4 cio_ignore=all,!0.0.0009 vnc rd.dasd=0.0.0250,251,252,253,254,255 rd.dasd=0.0.025f ip=172.17.51.126::172.17.50.1:255.255.254.0:fedora.hds.com:enccw0.0.0340:none rd.znet=qeth,0.0.0340,0.0.0341,0.0.0342,layer2=0,portno=0 http_proxy=http://thuegel:p...@xx.xx.xx.xx:8080 proxy=http://thuegel:p...@xx.xx.xx.xx:8080 root=live: https://dl.fedoraproject.org/pub/fedora-secondary/releases/23/Server/s 390x/os/images/install.img nameserver=xx.xx.xx.xx Has anyone seen this? Thanks Tom -- 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: Question on EDEV devides and DIRMAINT
Note that CPFMTXA refers to the blocks on FB-512 disks as "pages" and there are 8 blocks in a page. So the reserved area at the start of a FB-512 volume is 4 pages but 32 blocks. In EXTENT CONTROL, you'd start at 32, not 4. But - EXTENT CONTROL allows a keyword "Start" for the beginning allocation. It translates to 1 for ECKD and 32 for FB-512. So, just code your regions as "START END" and you've allocated the entire pack. Note 1: DIRMAINT won't allocate minidisk starting below the "Start" value anyway, so if you would code 0 or 4 (for FBA), no worries. Note 2: You'll probably want to create your own device type in the :Defaults. section at the end of the file that specifies how many blocks your LUNs have. Otherwise, Dirmaint will default to the very small 9336. For instance, for my 10 GB LUNs on my test system, I have "BIGEDEV 20971520" in the defaults section. (Maybe 10 GB isn't "big" any more..) On Tue, Dec 8, 2015 at 9:26 AM, Alan Altmark wrote: > > > First, note that EDEVs are limited to 1TB minus 1 page. (See the notes on > the MDISK statement in the CP Planning and Admin book.) > > Other than that, you treat FBA volumes just like 9336 from a prep > perspective. Use CPFMTXA. CPFMTXA will tell you that 4-END are PERM > space, so make sure your EXTENT CONTROL is "4 END", not "1 END". > > Just like using a VFB-512 mdisk on a 2nd level system. > > Alan Altmark > > Senior Managing z/VM and Linux Consultant > Lab Services System z Delivery Practice > IBM Systems & Technology Group > ibm.com/systems/services/labservices > office: 607.429.3323 > mobile; 607.321.7556 > 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/ > -- Bruce Hayden z/VM and Linux on z Systems ATS IBM, Endicott, NY -- 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: Question on EDEV devides and DIRMAINT
On Tuesday, 12/08/2015 at 02:13 GMT, "Will, Chris"
wrote:
> I have been investigating using EDEV devices (EMC SAN) for Linux guest
> deployment. What I would like to do is request say a 1TB LUN, assign it
to
> z/VM in a DIRMAINT pool, and then deploy 40G of space to the guests. I
see how
> to create EDEV devices and I see a few examples of 9336 type devices in
the
> extent control file but no examples of how we get from an EDEV device
("4000")
> to a 6 character label in the extent control file. I would assume this
would
> use cpfmtxa but not sure how to go about this.
First, note that EDEVs are limited to 1TB minus 1 page. (See the notes on
the MDISK statement in the CP Planning and Admin book.)
Other than that, you treat FBA volumes just like 9336 from a prep
perspective. Use CPFMTXA. CPFMTXA will tell you that 4-END are PERM
space, so make sure your EXTENT CONTROL is "4 END", not "1 END".
Just like using a VFB-512 mdisk on a 2nd level system.
Alan Altmark
Senior Managing z/VM and Linux Consultant
Lab Services System z Delivery Practice
IBM Systems & Technology Group
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
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/
Question on EDEV devides and DIRMAINT
I have been investigating using EDEV devices (EMC SAN) for Linux guest
deployment. What I would like to do is request say a 1TB LUN, assign it to
z/VM in a DIRMAINT pool, and then deploy 40G of space to the guests. I see how
to create EDEV devices and I see a few examples of 9336 type devices in the
extent control file but no examples of how we get from an EDEV device ("4000")
to a 6 character label in the extent control file. I would assume this would
use cpfmtxa but not sure how to go about this.
Chris Will
The information contained in this communication is highly confidential and is
intended solely for the use of the individual(s) to whom this communication is
directed. If you are not the intended recipient, you are hereby notified that
any viewing, copying, disclosure or distribution of this information is
prohibited. Please notify the sender, by electronic mail or telephone, of any
unintended receipt and delete the original message without making any copies.
Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are
nonprofit corporations and independent licensees of the Blue Cross and Blue
Shield Association.
--
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/
