(subject line updated) On Friday, 01/05/2007 at 01:15 CST, Tom Duerbusch <[EMAIL PROTECTED]> wrote: > It wasn't that the manuals stated that fact as much as it implied it. > > The manuals basically said that vswitch was a software version of > hipersockets. Fair enough and I took it futher. In my book, a software > version of hardware, a virtual version of something real, something that > emulates something else, all should be able to be use without any > changes.
Then something is wrong in the manuals. If you can send your comment to the e-mail address in the front of the offending book, we'll fix it. The z/VM 5.1 Connectivity manual contains an extensive write-up on virtual networking options, in case anyone else finds themselves wondering about all of this. > I took an existing zLinux machine, connected to a vswitch, and swapped > out the NICDEF for real hipersocket addresses. Didn't work at all. So, > I fell back to vswitch and added the hipersocket addresses and > configured them via yast. Worked a lot better. Yep, hipersockets is > quite a bit different than OSA or Vswitch. Unfortunately we allowed the OSA data transfer protocol name (QDIO) to become the attribute name rather than "OSA". I mean, doesn't just *everyone* know that OSA (OSD chpid) uses QDIO and HiperSockets (IQD) chpid use iQDIO (iQDIO..IQD..get it?). Obvious, eh? :-) This is what happens when you put programmers in charge of programming... Alan Altmark z/VM Development IBM Endicott ---------------------------------------------------------------------- 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
