> Thanks. The document I am using to build this environment says that if I > do that then I will not be able to access the R/W DASD even from the ID i > used to build them since all systems will not see the DASD as R/O. If > there a way around that?
Your R/W guest should not update the dasd that others have linked to and are using. You run into filesystem buffer/consistency problems because the guests do not know that others are using the dasd too. Is your "basevol" volume listed in the boot parameters of the R/W guest? If it is, it probably shouldn't be (just add it to /proc/dasd/devices when you are doing maintenance and the other guests are not using it). > "dasd=1F0-200,201(ro),202-21F > > However note that this cannot be done from the guestvol system, since the > boot device is R/O. And if this is done from the basevol system you will > no longer be able to write to the boot device to maintain it in the > future. " Here they are saying it is impossible for guests to write a new ipl record (with 201(ro) or anything for that matter) from the guest system because VM won't let the guest write there. So (unless you are using Leland's patch to get the parms from somewhere else), you run zipl with the 201(ro) line targeted at the basevol from the guest that can write to the basevol, then when the RO guests ipl off the basevol the dasd driver sees in the kernel parms that the device should be ro. ~ Daniel ----------------------------------------------------------------------- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you. ---------------------------------------------------------------------- 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
