Patrik:
The short answer is yes, every partition needs it's own disk adapter and
disk units.
Now the longer answer is that those can be virtual disk adapters and disk
units hosted by the partition that has the physical disk adapter and disk
units.
First create the virtual SCSI adapters in the HMC for the hosting partition.
Those will end up with a resource name IE:CTL03.
Then create the virtual disk controller. See this:
PGM
VRYCFG CFGOBJ(SALS) CFGTYPE(*NWS) STATUS(*OFF) +
FRCVRYOFF(*YES)
monmsg cpf0000
DLTNWSD NWSD(SALS)
monmsg cpf0000
CRTNWSD NWSD(SALS) RSRCNAME(CTL03) TYPE(*GUEST +
*LINUXPPC) ONLINE(*YES) VRYWAIT(*NOWAIT) +
SHUTDTIMO(31) PARTITION(*NONE) PTNNBR(9) +
CODEPAGE(437) MSGQ(QGPL/SALS) POOL(*BASE) +
TCPPORTCFG(*NONE) TCPRTE(*NONE) +
TCPHOSTNAM(*NWSD) TCPDMNNAME(*SYS) +
TCPNAMSVR(*SYS) ALWDEVRSC(OPTVRT21) +
RSTDDEVRSC(*NONE) IPLSRC(*PANEL) +
IPLSTMF(*NONE) IPLPARM(*NONE) PWRCTL(*NO) +
SRVOPT(*NONE) TEXT('SALS DVD emulation')
VRYCFG CFGOBJ(SALSSTG) CFGTYPE(*NWS) STATUS(*OFF) +
FRCVRYOFF(*YES)
monmsg cpf0000
DLTNWSD NWSD(SALSSTG)
monmsg cpf0000
CRTNWSD NWSD(SALSSTG) RSRCNAME(CTL02) TYPE(*GUEST +
*LINUXPPC) ONLINE(*YES) VRYWAIT(*NOWAIT) +
SHUTDTIMO(31) PARTITION(*NONE) PTNNBR(9) +
CODEPAGE(437) MSGQ(QGPL/SALS) POOL(*BASE) +
TCPPORTCFG(*NONE) TCPRTE(*NONE) +
TCPHOSTNAM(*NWSD) TCPDMNNAME(*SYS) +
TCPNAMSVR(*SYS) RSTDDEVRSC(*ALLTAPE +
*ALLOPT) IPLSRC(*PANEL) IPLSTMF(*NONE) +
IPLPARM(*NONE) PWRCTL(*NO) SRVOPT(*NONE) +
TEXT('SALS Storage Emulation')
ENDPGM
That will create the network server descriptions needed.
Use the CRTNWSSTG to create the disk units:
CRTNWSSTG NWSSTG(SALS01)
NWSSIZE(40140)
FORMAT(*OPEN)
TEXT('35gB Storage for SALS')
Note: 35*1024=35480, but you have to leave room for virtualization and a
few other things that take about 12%, so I always use # Gig I want * 1024 *
1.12 = nwssize. Others may argue with the formula, but it works.
Add the disk units to the network storage by linking them. Easiest with
WRKNWSSTG. Follow the prompts.
Now create your new partition and you have storage. Clearly I did not show
you all the steps. I'm working on an open source version of a program that
would create the virtual devices on the HMC, build the partition, do the
above, then start the partition.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Patrik
Schindler
Sent: Monday, January 6, 2020 10:41 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: LPARs Type *OS in IBM i as Hypervisor,
Hello,
status quo is IBM i 7.2 in first LPAR of a 8203-E4A. When I want to create
additional LPARs (in HMC), according to the iVirtualization Link shown below
there needs to be a host SCSI adapter in the primary LPAR, and a client
adapter in the guest LPAR, with according ID configuration. This works fine
for one guest LPAR.
Before trying and investing a lot of time: Do I need to have a server SCSI
adapter in the primary LPAR for every further guest LPAR? Or can one adapter
be shared across LPARs. I have no idea where to look for this special kind
of information.
How many secondary LPARs does IBM i as a hypervisor allow to run? And, how
to overcome the four logical ports limit with an installed LHEA? (Displaying
the LHEA configuration of a LPAR profile to choose a logical port yields
four logical ports available.) It's really hard to find the right spot in
the huge amount of documentation from IBM. I failed to find it.
Thanks!
Link to iVirtualization:
https://www.ibm.com/developerworks/community/files/form/anonymous/api/librar
y/f57fde24-5f30-4295-91fb-e612c6a7a75a/document/0a050aca-3ac9-4e91-87dd-1603
2645a695/media
:wq! PoC
PGP-Key: DDD3 4ABF 6413 38DE -
https://www.pocnet.net/poc-key.asc
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
