zfcp Yum install
by Bernie VK2KAD
Hi all
I wanted to install zfcp but I'm getting the following - not sure how to get
around this or what is causing it - I have network connectivity as seen by
the ping.
-bash-4.0# yum install zfcp
Setting up Install Process
No package zfcp available.
Nothing to do
-bash-4.0#
-bash-4.0#
-bash-4.0# ping www.google.com
PING google.navigation.opendns.com (208.67.216.230) 56(84) bytes of data.
64 bytes from 208.67.216.230: icmp_seq=1 ttl=49 time=193 ms
64 bytes from 208.67.216.230: icmp_seq=2 ttl=49 time=194 ms
64 bytes from 208.67.216.230: icmp_seq=3 ttl=49 time=191 ms
^C
--- google.navigation.opendns.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2848ms
rtt min/avg/max/mdev = 191.927/193.105/194.094/1.028 ms
-bash-4.0#
Thanks
Bern
14 years, 7 months
Fedora 11 s390x emulator
by David Smith
Back on 6/18, Karsten Hopp posted the following message to
fedora-devel-list:
<https://www.redhat.com/archives/fedora-devel-list/2009-June/msg01635.html>
The Fedora s390x team has published a f11 s390x hercules emulator image.
Since that message was sent, there was a second image published, called
'f11-s390x-20090716.img.bz2' that you'll find in
<http://secondary.fedoraproject.org/pub/alt/spins/S390/>.
I've taken that image, booted it, and done some systemtap testing with
it. Here's what I've found.
- Setup: Once your host system setup is done, setting the the s390x
guest image is normal for any f11 system. You'll need to use yum to
install the various packages systemtap needs for development and test.
Note that there isn't a s390x yum debuginfo repository, so you'll have
to download the kernel's debuginfo packages from the s390x project's
koji instance: <http://s390.koji.fedoraproject.org/koji/>
- Speed: As you can imagine, the emulated s390x system is slow, very
slow. But, with patience, it is usable. Note that yum seems to be
extremely slow.
- Systemtap: Systemtap seems to generally work on the emulated s390x
system. I've worked with kernel is 2.6.29.5-191.fc11.s390x (after a yum
update), so it is much more recent than a rhel5 kernel.
I was never able to get a full systemtap testsuite run completed. The
first problem I ran into was I kept getting timeouts. After an increase
of 20x on all timeout values, I didn't get timeouts anymore, but the
testsuite would just hang after awhile.
So, from a systemtap point of view, what could you use this for?
- an easy way to test for compilation errors on an s390x
- a good way to test an individual systemtap testcase/feature
If anyone has any questions, please let me know.
--
David Smith
dsmith(a)redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)
14 years, 7 months
current state of (F11) installation
by Steffen Maier
Hi all,
under the following prerequisites one specific installation path of F11
(taken from Karsten's pungi tree dated 20080804) now works until the
shutdown of the installation system, i.e. when anaconda passes control
back to linuxrc.s390:
- all DASDs offline (I have a non-existant devno in conf file)
- activate one zFCP-attached SCSI disk from within parm/conf file
- partition a small swap partition and the rest of /dev/sda as rootfs
with ext3
- on top of Karsten's already modified
anaconda-11.5.0.59-1.fc11.kh.1.s390x, you need the following patches
I posted to anaconda-devel (and most of which are also upstream):
* for initrd.img:
* suggest disabled X11-forwarding for ssh login in linuxrc.s390
* make IPv4 configuration in linuxrc.s390 compatible with NM in loader
* Handle activation of DASDs in linuxrc.s390 since loader no longer
works
* Correctly inform the user once about obsolete parm/conf file
options on s390
* for updates.img:
* correctly activate zFCP LUN on s390
* correctly deactivate zFCP LUN on s390
* prevent getting started up or shutdown again while already in such
state
* Log zFCP errors in addition to displaying dialog box
Adding the one SCSI disk interactively in Anaconda works, but
iw/autopart_type.py:self.bootcombo doesn't get updated and thus reports
an error "Must select a drive to use as ""the bootable device." and
won't continue. This whole mechanism including the UI dropdown box is
meaningless and even misleading for s390x since the zipl bootloader
always has to go on the disk device where /boot lives.
At the end of anaconda, when packages and the bootloader have been
installed, the reboot doesn't work because /sbin/shutdown is no longer
in initrd.img:
> [2009-08-16 20:22:05,812] WARNING: Storage.writeKS not completely implemented
> 00: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop from
> CPU 02.
> 01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop from
> CPU 02.
> /init: line 92: /sbin/shutdown: No such file or directory
> /init: line 92: exec: /sbin/shutdown: cannot execute: No such file or directory
> Kernel panic - not syncing: Attempted to kill init!
> Kernel BUG at 0000000000000002 [verbose debug info unavailable]
> illegal operation: 0001 [#1] SMP
> Modules linked in: xfs exportfs vfat fat ext2 zfcp scsi_transport_fc scsi_tgt xt
> s lrw gf128mul sha256_generic cbc dm_crypt dm_round_robin dm_multipath linear ra
> id10 raid456 async_xor async_memcpy async_tx xor raid1 raid0 dasd_fba_mod dasd_d
> iag_mod iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi squashfs cramfs qet
> h_l3 ipv6 qeth qdio ccwgroup dasd_eckd_mod dasd_mod
> CPU: 2 Not tainted 2.6.29.5-191.fc11.s390x #1
> Process init (pid: 1, task: 000000003fe98000, ksp: 000000003fe97c58)
> Krnl PSW : (null) 0000000000000002 (0x2)
> R:0 T:0 IO:0 EX:0 Key:0 M:0 W:0 P:0 AS:0 CC:0 PM:0 EA:0
> Krnl GPRS: 0000000000000000 0000000000001000 000000003fe97c90 0000000000000000
> 00000000006aa62e ffffffff00000001 0000000000000000 00000000000003e0
> 000000000005793c 00000000006aa62e 0000000000000000 000000003fe97be0
> 0000000000634b88 0000000000419608 0000000000023e5e 000000003fe97be0
> Krnl Code:>0000000000000002: 0000 unknown
> 0000000000000004: 0000 unknown
> 0000000000000006: 0000 unknown
> 0000000000000008: 0000 unknown
> 000000000000000a: 0000 unknown
> 000000000000000c: 0000 unknown
> 000000000000000e: 0000 unknown
> 0000000000000010: 0000 unknown
> Call Trace:
> ([<0000000000000040>] 0x40)
> [<0000000000023e5e>] on_panic_notify+0x52/0x70
> [<0000000000415708>] notifier_call_chain+0x48/0x9c
> [<00000000004157ca>] atomic_notifier_call_chain+0x32/0x44
> [<000000000040f4c6>] panic+0xd6/0x204
> [<0000000000057070>] do_exit+0xa8/0x884
> [<000000000005790e>] do_group_exit+0xc2/0xf0
> [<000000000005798a>] SyS_exit_group+0x4e/0x60
> [<0000000000029086>] sysc_noemu+0x10/0x16
> [<000002000010e20a>] 0x2000010e20a
> Last Breaking-Event-Address:
> [<0000000000023dd4>] stop_run+0xec/0x124
> <4>---[ end trace fc7da2acd33fb952 ]---
> Fixing recursive fault but reboot is needed!
You can manually trigger the reboot using the magic sysrq key sequence:
^-b
The VM guest then reboots (reIPL) correctly:
> 00: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop from
> CPU 02.
> 01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop from
> CPU 02.
> 02: HCPLDI2816I Acquiring the machine loader from the processor controller.
> 02: HCPLDI2817I Load completed from the processor controller.
> 02: HCPLDI2817I Now starting the machine loader.
> 00: HCPGSP2630I The virtual machine is placed in CP mode due to a SIGP stop and
> store status from CPU 02.
> 01: HCPGSP2630I The virtual machine is placed in CP mode due to a SIGP stop and
> store status from CPU 02.
> 02: MLOEVL012I: Machine loader up and running (version v1.4).
> 02: MLOPDM003I: Machine loader finished, moving data to final storage location.
> Initializing cgroup subsys cpuset
> Initializing cgroup subsys cpu
> Linux version 2.6.29.5-191.fc11.s390x (mockbuild(a)zedora3.z900.redhat.com) (gcc v
> ersion 4.4.0 20090506 (Red Hat 4.4.0-4) (GCC) ) #1 SMP Wed Jun 24 15:02:47 EDT 2
> 009
> setup: Linux is running as a z/VM guest operating system in 64-bit mode
> setup: Address spaces switched, mvcos available
> Zone PFN ranges:
> DMA 0x00000000 -> 0x00080000
> Normal 0x00080000 -> 0x00080000
> Movable zone start PFN for each node
> early_node_map[1] active PFN ranges
> 0: 0x00000000 -> 0x00040000
> Built 1 zonelists in Zone order, mobility grouping on. Total pages: 258560
> Kernel command line: root=UUID=8ee05092-a8e0-4081-8076-0a9dec7ea2fc
> ...
> Freeing unused kernel memory: 224k freed
> Mounting proc filesystem
> Mounting sysfs filesystem
> Creating /dev
> Creating initial device nodes
> scsi0 : zfcp
> scsi1 : zfcp
> qdio: 0.0.3c1b ZFCP on SC 14 using AI:1 QEBSM:1 PCI:1 TDD:1 SIGA: W AO
However, the initrd code seems to come to a halt when activating the
SCSI disk with the rootfs. Since mkinitrd is replaced with dracut for
F12, IMHO it doesn't make much sense trying to fix mkinitrd.
On using one DASD instead of a SCSI disk, I get errors when entering the
partitioner about unfulfilled constraints of parted. I suspect this to
be due to DASD support in parted, since SCSI worked as stated above.
Steffen
Linux on System z Development
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Erich Baier
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
14 years, 7 months
VNCserver
by Bern Saward
Hi all
I am making progress with my F11 running on Hercules - I can now access the
Internet and install packages with yum.
First I installed Midnight Commander - works a treat, then I installed
TigerVNC - and added xauth as it was a missed dependency.
I can connect to vncserver but all I get is a black screen - it has a big X
cursor, and a window with 3 check boxes that say
Accept clipboard from viewers
Send clipboard to viewers
Send primary selection to viewers
But that is where it all ends - all I can do is check/uncheck the
checkboxes. I have no idea how to get a window up and going - not really
an s390x question but as an old mainframer I need some direction with
getting results from Linux.
All ideas/suggestions appreciated
Bern - VK2KAD
14 years, 7 months
Problem running spin with hercules
by Jim Stephens
I am having the same problem running the spin from
http://secondary.fedoraproject.org/pub/alt/spins/S390/ that I had
previously with the current update of 17 Jul.
I tried the hercules snapshots of 2/10, 12/31 and 10/29. The problem is
due to an error with diag 224 causing the Fedora 11 kernel to crash, and
panic when trying to getting ready to run init. I pull the ivansoft
snapshots of the above dates. There was a change to the source on 10/29
made by Ivan which seemed to be an attempt to fix something in the diag.
I tried 1 and 2 cpus, and when the fedora disk boots up, it has two
linux kernels, and I tried all combinations in a matrix.
I would be interested if anyone can supply an exact hercules snapshot
date that builds on the amd64, or x86 platforms, and runs this
snapshot. The only thing cited in any reports I have found cite a
version based on an rpm, which does not trace back to the hercules
source date pull, or a platform, again which does not track back to the
hercules source.
To the hercules group, it would be nice if the actual source pull date
was embedded somewhere and was available by a command, or in the
banner. Now that hercules uses SVN, the revision is unique and would
track to a particular source as well. Currently it shows the build date,
which is unfortunately the date I pulled and built the source, and does
not uniquely identify when the source was pulled from SVN. This
identifier would more exactly track which source is needed have a
particular set of symptoms.
An example of the traceback panic info I am seeing is below. The exact
numbers may be slightly different, but the hypfs is the same.
Thanks
Jim
Call
Trace: +
( <00000000006714f4>! hypfs_diag_init+0x34/0x1dc)
<0000000000671428>! hypfs_init+0x48/0xe0
<0000000000012106>! do_one_initcall+0x86/0x180
<00000000006645b4>! kernel_init+0x3ec/0x460
<000000000001c1d2>! kernel_thread_starter+0x6/0xc
<000000000001c1cc>! kernel_thread_starter+0x0/0xc
Last Breaking-Event-Address:
<0000000000035048>! diag204_get_buffer+0x134/0x138
Call Trace:
( <00000000fffbaec6>! 0xfffbaec6)
<0000000000023e5e>! on_panic_notify+0x52/0x70
<0000000000415708>! notifier_call_chain+0x48/0x9c
<00000000004157ca>! atomic_notifier_call_chain+0x32/0x44
<000000000040f4c6>! panic+0xd6/0x204
<0000000000057070>! do_exit+0xa8/0x884
<000000000001736c>! default_trap_handler+0x0/0x78
<0000000000012d26>! do_no_context+0x132/0x13c
<0000000000414854>! do_protection_exception+0x29c/0x378
<000000000002908c>! sysc_return+0x0/0x8
<000000000067150a>! hypfs_diag_init+0x4a/0x1dc
( <00000000006714f4>! hypfs_diag_init+0x34/0x1dc)
<0000000000671428>! hypfs_init+0x48/0xe0
<0000000000012106>! do_one_initcall+0x86/0x180
<00000000006645b4>! kernel_init+0x3ec/0x460
<000000000001c1d2>! kernel_thread_starter+0x6/0xc
<000000000001c1cc>! kernel_thread_starter+0x0/0xc
Last Breaking-Event-Address:
<0000000000023dd4>! stop_run+0xec/0x124
<4>--- end trace 561bb236c8008520 !---
14 years, 7 months
How can I add another CTC
by Bernie VK2KAD
I am trying to work out how to define another CTC to Fedora. I added a
second CTCA in my Herc config file at address 610/611,
I was hoping Fedora would autodetect the new CTC - not so. So then I added
a definition in /etc/sysconfig/network-scripts for CTC2 - this I did by
copying CTC1 and making the changes I wanted. I saw this in dmesg - not
sure what is happening here.
ctcm: CTCM driver initialized
ctc0 (ctcm): not using net_device_ops yet
net ctc0: setup OK : r/w = ch-0.0.0600/ch-0.0.0601, protocol : 0
udev: starting version 139
udev: renamed network interface ctc0 to ctc1
My aim is to have one CTC pointing to my loopback device for local IP access
and the other CTC configured to talk to my NIC so I can get to the out-side
world.
Rgds Bern
14 years, 7 months