On 12/23/08 8:28 AM, "Bauer, Bobby (NIH/CIT) [E]" <baue...@mail.nih.gov> wrote:
> At least one presentation indicates using the DIAG driver instead of the FBA > drive is more efficient. How do I do this? We are using Redhat 5.2 on VM 5.4 > Is there a good concise, complete write up of how to add and use V-DISK? I've > cobbled together what I have from several different sources. Rob talked about the changes inside the Linux guest (minimal), but the basic steps are: 0. Create a common minidisk to hold tools like SWAPGEN, VMARC, etc, if you haven't already done so. It is good practice to use a separate userid (see below) from any of the IBM-supplied ones so you don't mix your stuff and IBM stuff. Format it and copy common handy tools onto it. I use TEMPLATE 198 in the examples below. 1. Create a 1 cyl minidisk for the Linux guest userid at virtual address 191. If you want, you can create a larger disk on a different userid and share it between multiple guests R/O ; this is a religious preference whether you have one big disk or lots of little 1 cyl ones on individual IDs. The disk should be R/O to the Linux guest as it should never need to update it itself. Virtual address 191 is important as that is where CMS will look for it's stuff. You can also use a SFS directory, although that has some issues of it's own that add to the complexity of managing your environment. If you use minidisks, the entry in the guest CP directory should look something like: (for the dedicated disk for each user): MDISK 191 3390 vvvvvv start end RR rpwd wpwd mpwd (for the shared R/O disk for all guests): LINK TEMPLATE xxx 191 RR Where TEMPLATE is the userid that is acting as a ID to use to hold common configuration information. That's just what I use, any userid is OK, although I'd recommend something that is not in the standard IBM set (ie, don't hang it off MAINT) because you'll want to migrate this id from release to release. 2. If your directory manager doesn't automatically format the new minidisk, link it in write mode from your userid (eg LINK GUEST1 191 199 MR wrpw) and format it using the CMS format command. 3. Create a PROFILE EXEC on the newly formatted minidisk. A simple example might look like this (comments in /* */, note quotes): ;-- Start: PROFILE EXEC /* REXX */ /* a REXX comment must be the first line to force CMS to use REXX parsing */ /* set virtual address of the linux boot volume */ /* replace cuuu with virtual address */ linuxipl = 'cuuu' /* set name of virtual machine to receive console logs */ conid = 'LOGGER' /* find out who I am */ me = userid() /* access the handy tools disk described in step 0 */ Say 'PROFILE: Accessing Tools Disk' 'VMLINK TEMPLATE 198' /* Run SWAPGEN to create your Linux swap disks as many times as necessary */ /* substitute valid swapgen parms for the xxxxxxx */ /* make sure you use by-path entries in /etc/fstab to avoid these */ /* things changing dasd mappings */ Say 'PROFILE: Creating Swap Disks' 'SWAPGEN xxxxxxxx' 'SWAPGEN xxxxxxxx' /* Do any other setup you want to do before Linux starts, eg */ /* define switches, couple NICs to the right GLAN/VSWITCH etc */ /* example: 'CP COUPLE 340 SYSTEM VSWITCH1' */ Say 'PROFILE: Performing User Environment Setup' 'CP SET RUN ON' 'CP SPOOL CONSOLE TO' conid 'START CLASS C EOF NAME' me 'CONLOG' /* All is in readiness; drop the big bomb on CMS and go */ /* to Linux IPL */ Say 'PROFILE: Transferring control to Linux IPL' '#CP IPL' linuxipl /* exit -- pointless because CMS just got destroyed by the */ /* previous line, but I'm pedantic */ exit rc ;-- End: PROFILE EXEC 4. RELEASE fm ( DETACH to release the 191 minidisk you created. 5. Update the CP directory for the guest to IPL CMS PARM AUTOCR if it isn't already that way. 6. Shut down the Linux guest and log it completely off. 7. Log onto the Linux guest and watch it come up from the console. You should see CMS start up and the PROFILE messages come out on the console, then the normal Linux IPL. The above outline should give you the basics. I don't claim the PROFILE EXEC code is perfect -- I'm sure the peanut gallery will have comments -- but it ought to give you the basic idea. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
