Title: 2nd-Level VM Install Question

TIA. You do have to be careful when using duplicate volids. If you’re new to VM and plan to IPL this system under VM only than create a mini-disk for your second level guest starting at cyl 1. Cyl 0 label will not change. Also this way you can us the standard install process. You will be short one cyl but that should not be a problem. If you just need a copy of your VM system for second level testing it may by faster/easier to make a copy using DDR. Again you’ll use a mini-disk starting at cyl 1. After the copy just IPL the VM sysres on second level and user option FORCE instead of WARM. Add as many paging and spool volumes as needed. Again they can be offset by one cyl.

 

 Hans

 


From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] On Behalf Of KEETON Dave B
Sent: December 7, 2005 6:48 PM
To: [email protected]
Subject: 2nd-Level VM Install Question

 

In building a second level VM instance of VM510, under VM510, I see that INSTIIS wants to pin VOLIDs that are the same as my first level system. I understand that these volumes will only be attached to the second level guest user and are on different real devices but writing a non-unique label to multiple DASD volumes used in the same LPAR has me a little freaked. Is there a way to change the default VM510 VOLIDs or, since these are unique to the guest, am I just being paranoid?

TIA,

Dave Keeton
Systems Analyst
z/VM Linux Support
Oregon Dept. of Transportation
955 Center Street NE
Salem, OR 97301

Office: (503) 986-3199
FAX:    (503) 986-3242

Reply via email to