We're no experts but we basically use the same minidisk addresses for the various linux guests. We also tend to put application products in their own filesystem on a separate VM minidisk. So our linux guests have basically the same minidisks for the SuSE linux filesystems. We didn't have a problem with limited dasd yet so each guest has 2 sets of system minidisks (2 levels of maintenance). We have a base linux guest where we install all system software. We have exec's which DDR maintenace to the other guests and perl scripts that copy appropriate files for a given guest depending on what application it runs (for example so that the correct daemons are started up). "McKown, John" wrote:
> I have a general administration / setup question for people who are running > multiple Linux/390 systems under z/VM. Do all your Linux instances use the > same virtual addresses for things like DASD, regardless of the actual device > address? Or do you find it "better" to make the virtual DASD address match > the actual device address? I'm tending towards making all Linux/390 > instances use the same set of virtual DASD addresses, which are not even > related to the "real" DASD addresses. I think this would be easier to > maintain and "clone" new instances. Do you even try to make the Linux DASD > addresses "look like" the actual device numbers, or do you simply have a > range of virtual DASD addresses that you assign to physical devices. I'm > using MDISK statements for Linux DASD. Basically, so far, I give each > instance (OK, I only have one so far), the entire device OTHER THAN the > first cylinder. Sorry, but I don't trust the Linux administrator to not > destroy the DASD label, so this protects it from any mistakes. Oh, I'm the > OS/390 and z/VM (new) sysprog. I am familar with Linux on Intel and did help > the Linux administrator set up the initial Linux/390 system because she is > not s390 literate. And I had actually done a SuSE s390 install at home under > Hercules/390. So I was the "expert". > > -- > John McKown > Senior Systems Programmer > UICI Insurance Center > Applications & Solutions Team > +1.817.255.3225 > > This message (including any attachments) contains confidential information > intended for a specific individual and purpose, and its' content is > protected by law. If you are not the intended recipient, you should delete > this message and are hereby notified that any disclosure, copying, or > distribution of this transmission, or taking any action based on it, is > strictly prohibited.
