VSWITCH is the answer, of course. But that's the next great leap through our company Internet Security group. Baby steps first. We have OSA rdevs available, and the need for three new zLinux guests in a hurry, of course.
VSWITCH is already being planned, but it has a longer timeline since it involves moving the cheese a great many more recalcitrant people. So... the question remains (if a reply from Alan is not already winding its way through the net at this late hour on the east coast) Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. "Marcy Cortes" <[EMAIL PROTECTED]> Sent by: "The IBM z/VM Operating System" <[email protected]> 04/23/2008 11:29 PM Please respond to "The IBM z/VM Operating System" <[email protected]> To [email protected] cc Subject Re: OSA rdev and vdev requirements for Linux guests. Wait, what are you doing attaching osa's to Linux? VSWITCH! Seriously, I think you use a lot more storage on the Linux guest and make him less likely to be idle. Marcy Cortes "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mike Walter Sent: Wednesday, April 23, 2008 9:25 PM To: [email protected] Subject: [IBMVM] OSA rdev and vdev requirements for Linux guests. Way back when, in the olden days, I seem to remember that the first OSA address of a triplet used by Linux guests had to be an even address. But then there are also vague memories of more recent information that as long as the first OSA vdev of a triplet seen by a guest is even, it does not matter if its rdev is odd. Is that true, or have I been sneaking sips of Adam's cough medicine? If the first vdev of the triplet being even is all that matters, do all the rdevs have to be in ascending sequential order? Or could we harvest all those lone, odd-numbered OSA rdevs? E.g. "7000, 7001, 7002" used, reclaim the abandoned 7003 rdev to be assigned as an even-numbered vdev, "7004, 7005, 7006" used, reclaim the abandoned 7007 rdev to be assigned as an even-numbered vdev, etc.)? And... where is this documented that I obviously overlooked? Of course if a restriction were removed, where would one find it documented except in old manuals and folklore? :-) Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
