Creating an LPAR - the continuing saga......

[Pete Helgren <pete@xxxxxxxxxx>]

Thanks Larry,

OK!  That worked.  The partition booted to the SMS menu but I still have 
one additional question. So, I'll need to go back to an earlier post of 
yours about creating the SCSI adapters.  You recommended creating two 
(at least):

"Just slightly advanced but I like to create a PAIR of host adapters and 
PAIR of client adapters for each guest partition. One is used for DIsk, 
disk and only disk, never anything but disk. The other pair is used to 
share virtual optical and tape. You may not use Tape with Linux but you 
will use virtual optical to install the critter most likely. Having 
those separate means you can vary off the one used for optical without 
clobbering Linux."

So, I get the disk part:  It IS finding the NWSSTG which was assigned to 
the NWSD.  The NWSD is found because when I created it I pointed it to 
the CTL02 resource which is where the virtual SCSI adapter pointed.  The 
part I didn't quite get is that I created a second SCSI adapter, which 
is listed as CTL03, but how does the SCSI adapter get mapped to a 
virtual optical device?  CRTDEVOPT has a couple of options I haven't 
used before.  Do I need to create the virtual optical drive in a 
different way and reference that CTL03 resource?

Pete Helgren
www.petesworkshop.com
GIAC Secure Software Programmer-Java
AWS Certified Cloud Practitioner
Twitter - Sys_i_Geek IBM_i_Geek

On 1/23/2021 1:58 PM, Larry "DrFranken" Bolhuis wrote:
> You are on target.
>
> 0.25 / 0.5 / 1.0 - min/ desired/ max.
>
> Virtual processors are always whole numbers (though you see a decimal 
> point in there. :-) )  So 1.0 1.0 1.0 is correct for that.
>
> Uncapped is correct so that if i needs more than its 0.5 and Linux 
> isn't using it, it gets to borrow, and of course the same in reverse. 
> Part of the reason the 1 processor wont appear to be any issue.
>
> Weight can be left 128. But potentially i should be a tick higher, say 
> 192, because it does all the disk I/O so if Linux needs disk access i 
> does it. If it has to weight that's bad and more processor doesn't 
> help! Again though the reality is your low workloads, it probably will 
> make little difference.
>
>     - L