Ed, I think we need to look at your configuration a little deeper. You say that Linux can see all 6 of your real processors. By default VM will give just one virtual processor to a guest. How are you determining that you can get to all 6 processors with Linux? I think you will need to start by looking at the hardware Image profile to see what processors are assigned to the VM Partition? Under most circumstances most customers do not mix the CP's, IFL's and ZAAP's in the same partition unless they are running a VM Mode partition with z/OS as a guest of VM.
Regards, John Schnitzler Jr. jnsch...@us.ibm.com From: Ed Long <rdhm...@prodigy.net> To: LINUX-390@vm.marist.edu Date: 07/21/2010 05:19 PM Subject: Re: IFL's, VM, and Linux Sent by: Linux on 390 Port <LINUX-390@vm.marist.edu> Thanks for thinking about our problem. So does your construct COMMAND DEFINE CPU 00 IFL effectively tell VM to assign the first real IFL to this VM as CPU 00? On our system, the first real IFL is CPU 02 (00 and 01 are the CP's). Edward Long --- On Wed, 7/21/10, Mark Post <mp...@novell.com> wrote: From: Mark Post <mp...@novell.com> Subject: Re: IFL's, VM, and Linux To: LINUX-390@VM.MARIST.EDU Date: Wednesday, July 21, 2010, 5:02 PM >>> On 7/21/2010 at 01:21 PM, Ed Long <rdhm...@prodigy.net> wrote: > We have a z10 running VM 5.4 in LPAR #1. > The box has 2 half speed CP's, 2 IFL's, and 2 ZAAP's. > We want to modify a specific zLinux guest, call it zLinux1, to only run on > the IFL's. > So far, we can get it to see all 6 engines which is not good. > Sorry if this is obvous to some, what would be the best practice for doing > this? > Can we do it all in the Directory? Yes. > Can we do the configuration in such a way that it survives reboots and vm > IPL's? Yes. In the USER DIRECT entry for the guest, add COMMAND DEFINE CPU 00 IFL If the Linux system is not consuming more than ~ 80% of a real CPU, it should only have one virtual CPU defined. If it really needs more than that, then add another COMMAND DEFINE CPU xx IFL statement for each one. For this to take effect, you'll need to shutdown the Linux guest and log it off. You could issue the #CP DEFINE CPU 00 IFL command instead, but make sure your Linux guest is all the way down, as it will cause a virtual machine system reset and clear. Mark Post ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/ ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/ ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
<<inline: graycol.gif>>
