The way things are going , the string and 2 coffee cans is looking pretty good ;-)
VSWITCH looks like the way to go .. The process seems straight forward .. My problem here is that we don't have any "free OSA address" on this image.. Q OSA FREE A free OSA was not found. Can these be added ? Steve Gentry <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[email protected]> 02/24/2005 01:07 PM Please respond to Linux on 390 Port To: [email protected] cc: Subject: Re: Redhat 3 under VM Did you attach those addresses to you Linux machine? The dedicate method (statements go in your user directory for the linux machine) DEDICATE E108 E108 DEDICATE E109 E109 DEDICATE E10A E10A DEDICATE E10B E10B these address are based on what I sent you in an earlier email The attach method. ATTACH E108 linux_guest E108 ATTACH E109 linux_guest E109 ATTACH E10A linux_guest E10A ATTACH E10B linux_guest E10B In both scenarios above, these addresses cannot be attached to any other machine, in your case most likely TCPIP Having reading Adams email, I guess we should start from the the beginning. How do you want to access the osa card? directly? via TCPIP? VSWITCH like Adam mentioned? String and two coffee cans? (I don't know what the device type is for these. <g>) Respectfully, Steve G. Larry Pickering <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[email protected]> 02/24/2005 12:55 PM Please respond to Linux on 390 Port To: [email protected] cc: Subject: Re: Redhat 3 under VM Steve I detached them for TCPIP but Linux was still unable to find the devices.. It dosen't make any sense that you would have to basically take VM off the network to run Linux .. I'm able to see the devices now from my guest id .. q osa Ready; T=0.01/0.01 12:50:49 OSA 0A00 ON OSA 0A00 SUBCHANNEL = 0000 0A00 QDIO-ELIGIBLE QIOASSIST NOT AVAILABLE OSA 0A01 ON OSA 0A01 SUBCHANNEL = 0001 0A01 QDIO-ELIGIBLE QIOASSIST NOT AVAILABLE OSA 0A02 ON OSA 0A02 SUBCHANNEL = 0002 0A02 QDIO-ELIGIBLE QIOASSIST NOT AVAILABLE Ready; T=0.01/0.01 12:50:49 Steve Gentry <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[email protected]> 02/24/2005 12:11 PM Please respond to Linux on 390 Port To: [email protected] cc: Subject: Re: Redhat 3 under VM Not necessarily true. You can DEDICATE the osa addresses to the linux machine, thus bypassing VM TCPIP entirely. Devices (addrs) can only be DEDICATEd to one machine. If TCPIP has them, then you will have to detach them from TCPIP and attach them or use DEDICATE statements in the linux machine user directory. If you intended to get to the osa device via TCPIP, then I don't think you've got your linux parm file set up correctly. I never could get linux to work going through TCPIP and then out. That's why I have the osa addresses dedicated to my linux machine. Larry Pickering <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[email protected]> 02/24/2005 12:04 PM Please respond to Linux on 390 Port To: [email protected] cc: Subject: Re: Redhat 3 under VM Steve I have those parms coded... I believe that Linux under VM will use VM's TCPIP .. Steve Gentry <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[email protected]> 02/24/2005 11:43 AM Please respond to Linux on 390 Port To: [email protected] cc: Subject: Re: Redhat 3 under VM Are you perhaps missing: CHANDEV=qeth0,0xE108,0xE109,0xE10A NETTYPE=eth QETHPARM=add_parms,0x10,0xE108,0xE10A,portname:CHPID01 And the associated DEDICATE statements? Are you expecting your RHEL3 to talk directly to the osa card or are you going through TCPIP first? Larry Pickering <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[email protected]> 02/24/2005 10:43 AM Please respond to Linux on 390 Port To: [email protected] cc: Subject: Redhat 3 under VM Hello , I'm trying to get Redhat Enterprise Linux 3 running on our ADCD z/VM 4.4 system .. When I load Linux I get "no such device" when it trys to connect to our OSA card... Anyone run into this problem before ? Linux version 2.4.21-20.EL ([EMAIL PROTECTED]) (gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-42)) #1 SMP Wed Aug 18 20:32:45 EDT 2004 We are running under VM (64 bit mode) On node 0 totalpages: 32768 zone(0): 32768 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: ROOT=/dev/ram0 ro ip=off DASD=191,200,201 CMSDASD=191 CMSCONFFILE=inst.parm PEERID=TCPIP IPADDR=10.1.15.200 NETWORK=10.1.1.1 NETMASK=255.255.0.0 GATEWAY=10.1.1.1 BROADCAST=10.1.255.255 MTU=1492 HOSTNAME=RH01.CYBERMATION.COM Highest subchannel number detected (hex) : 0009 Calibrating delay loop... 231.83 BogoMIPS Page-cache hash table entries: 32768 (order: 6, 256 KB) Page-pin hash table entries: 8192 (order: 3, 32 KB) Dentry cache hash table entries: 16384 (order: 6, 256 KB) Inode cache hash table entries: 8192 (order: 5, 128 KB) Buffer cache hash table entries: 8192 (order: 4, 64 KB) Memory: 113864k/131072k available (2383k kernel code, 0k reserved, 991k data, 32 0k init) Mount cache hash table entries: 256 (order: 0, 4096 bytes) debug: Initialization complete POSIX conformance testing by UNIFIX Detected 1 CPU's Boot cpu address 0 cpu 0 phys_idx=0 vers=FF ident=0539FA machine=2066 unused=0000 Starting migration thread for cpu 0 init_mach : starting machine check handler Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket mach_handler : ready mach_handler : waiting for wakeup Starting kswapd VFS: Disk quotas vdquot_6.5.1 aio_setup: num_physpages = 8192 aio_setup: sizeof(struct page) = 104 pty: 2048 Unix98 ptys configured NET4: Frame Diverter 0.46 RAMDISK driver initialized: 256 RAM disks of 16384K size 1024 blocksize md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. Initializing Cryptographic API NET4: Linux TCP/IP 1.0 for NET4.0 IP: routing cache hash table of 256 buckets, 6Kbytes TCP: Hash tables configured (established 2048 bind 4096) Linux IP multicast router 0.06 plus PIM-SM Initializing IPsec netlink socket NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. RAMDISK: Compressed image found at block 0 Freeing initrd memory: 5761k freed VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 40k freed Starting the zSeries initrd to configure networking. Version is 1.01 Enter which kind of network device do you intend to use (e.g. ctc, escon, iucv, eth, hsi, tr): eth Enter parameters you need to pass to the channel device layer. This includes the I/O ports of your ctc, escon, qeth, hsi and lcs devices. (e.g. "ctc0,0x600,0x601" will activate the ctc0 interface at I/O ports 0x600,0x601) Hipersocket interfaces need to be configured like qeth devices, p.e. qeth0,0x3000,0x3001,0x3002 Additional parameters for QETH devices such as the portname should be entered at the next prompt, not here ! qeth0,0xa00,0xa01,0xa02 Each OSA-Express feature in QDIO mode must be associated with a port name Enter additional parameters for your QETH device (e.g. "add_parms,0x10,{lo_devno,hi_devno},portname:port_name") Press enter if you don't want to enter additional parameters add_parms,0x10,0xa00,0xa02,portname:osdport1 qdio: loading QDIO base support version 2 ($Revision: 1.145 $/$Revision: 1.57 $) qeth: loading qeth S/390 OSA-Express driver ($Revision: 1.337 $/$Revision: 1.113 $/$Revision: 1.42 $:VLAN) qeth: allocated 0 spare buffers /tmp/qeth.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg SIOCSIFADDR: No such device eth0: unknown interface: No such device SIOCSIFMTU: No such device SIOCSIFNETMASK: No such device SIOCSIFBRDADDR: No such device eth0: unknown interface: No such device Enter your DNS server(s), separated by colons (:): 10.1.1.1 Enter your DNS search domain(s) (if any), separated by colons (:): lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 127.0.0.1 0.0.0.0 255.255.255.255 UH 0 0 0 lo Starting portmap. Journalled Block Device driver loaded Starting telnetd and sshd to allow login over the network. Connect now to 10.1.15.200 to start the installation. Thanks Larry ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
