Quoting Johansen.Klaus KYJ k...@kmd.dk:
I tried out CMM1/VMRM earlier, but it kept reducing our guests until
they stopped answering and died. cpuplugd could be a fine way to let the
linux guests adjust themselves.
I don't recall the number, but there is an APAR that corrects that.
Leland
On Thu, Feb 12, 2009 at 9:02 PM, Johansen.Klaus KYJ k...@kmd.dk wrote:
4)
Is it possible to monitor the number of pages a guest has assigned to
the cmm1 page pool at CP level? That is, the dynamic guest size seen
from CP point of view (not proc/sys/vm/cmm_pages) - For example from
Perfkit?
On Thu, Feb 12, 2009 at 09:02:42PM +0100, Johansen.Klaus KYJ wrote:
1)
The man (5) page for cpuplugd mentions that the acpr variable is The
amount of page cache reads (as listed in vmstat in the bi and bo
fields). According to the man page for vmstat bi and bo is Blocks
received from/sent to
-Original Message-
Behalf Of Rob van der Heij
Sent: Friday, February 13, 2009 1:54 PM
It's very hard to fill in the blanks. As long as you drive
the cmm_pages from VM (which is imho the only place where you
have relevant metrics to provide the proper setting) you will
have to
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On
Behalf Of Hans-Joachim Picht
It is a good idea to integrate the cached variable from
/proc/meminfo into the cpuplugd rule set. I will integrate
this functionality into the next release.
Very cool,
On Fri, Feb 13, 2009 at 3:22 PM, Johansen.Klaus KYJ k...@kmd.dk wrote:
If you want to drive cmm_pages according to current memory/storage
restraint then yes, VM is the only place with relavant metrics. VM does
on the onther hand not know much about what happens inside the guest
(cmm2 not
I IPLed the install process.
Connected using SSH.
Started yast and went through the process to enable the DASD.
Then connected on another SSH session and mounted my boot disk as /mnt
cat /mnt/etc/sysconfig/hardware/hwcfg-bus-ccw-0.0.1d00
STARTMODE='auto'
MODULE=''
MODULE_OPTIONS=''
No LAYER2
I'm seeing the same thing. Except once the install is complete my NIC does
not start when I IPL from the boot disk. Have you successfully installed a
SLES10 using LAYER 2?
On Fri, Feb 13, 2009 at 12:08 AM, Tobias Doerkes tdoer...@hotmail.comwrote:
Hi list,
anyone out there using layer2
On 2/11/2009 at 10:48 PM, in message
499371c9026d00068...@sinclair.provo.novell.com, Mark Post
mp...@novell.com wrote:
On 2/11/2009 at 8:24 PM, Frank Swarbrick frank.swarbr...@efirstbank.com
wrote:
-snip-
The other reason is performance. Apparently there have been some tests to
move
On 2/12/2009 at 5:58 AM, in message
f255efe0ecf08c4a9c1db6aff423541709a9a...@ch2wpmail1.na.ds.ussco.com, Chase,
John jch...@ussco.com wrote:
-Original Message-
From: Linux on 390 Port On Behalf Of Frank Swarbrick
[ snip ]
I probably shouldn't open my mouth without having all of
On 2/13/2009 at 12:38 PM, Jihad K Kawkabani
jihad_k_kawkab...@progressive.com
wrote:
I cross posted this to IBMVM and Linux on S390.
Noticing a pause during the installation of SLES10 SP2 to a guest
configured with a VSWITCH
with VLANs. I have layer2 support set in the parm file and
On 2/13/2009 at 12:08 AM, Tobias Doerkes tdoer...@hotmail.com wrote:
Hi list,
anyone out there using layer2 support during SLES10 autoinstall in parmfile?
layer2=1 works fine so far, but the system always asks for the MAC. Is there
a parameter to specifiy one in the parmfile?
Yes,
On Friday, 02/13/2009 at 12:48 EST, Mark Post mp...@novell.com wrote:
This problem with using Layer 2 during installation seems to be coming
up more
often now, so I asked one of my contacts in Germany about it. He said
the
OSAHWaddr parameter is what you need to put into the parmfile to
On 2/13/2009 at 1:01 PM, Alan Altmark alan_altm...@us.ibm.com wrote:
-snip-
Eh? The OSA (real or virtual) already has a MAC address. You aren't
required to ifconfig a MAC address to bring up an OSA with Layer 2, so why
does the install want one? (The drivers extract the burned-in or
To the prompt I only hit the ENTER key without entering any MAC Address,
and the process goes on, that means it took the default value. If I enter
the MAC Address in the Parmfile, I would have to make sure it is unique.
Thanks and Regards,
Jihad K. Kawkabani
IT Systems Engineer Consultant
Voice:
On 2/13/2009 at 1:16 PM, Jihad K Kawkabani
jihad_k_kawkab...@progressive.com
wrote:
To the prompt I only hit the ENTER key without entering any MAC Address,
and the process goes on, that means it took the default value. If I enter
the MAC Address in the Parmfile, I would have to make sure
On Friday, 02/13/2009 at 01:15 EST, Mark Post mp...@novell.com wrote:
On 2/13/2009 at 1:01 PM, Alan Altmark alan_altm...@us.ibm.com
wrote:
-snip-
Eh? The OSA (real or virtual) already has a MAC address. You aren't
required to ifconfig a MAC address to bring up an OSA with Layer 2, so
why
I cross posted this to IBMVM and Linux on S390.
Noticing a pause during the installation of SLES10 SP2 to a guest
configured with a VSWITCH
with VLANs. I have layer2 support set in the parm file and after IPLing
from the reader, the guest
is stuck at the MAC address prompt. Hitting the enter
On 2/13/2009 at 1:35 PM, Alan Altmark alan_altm...@us.ibm.com wrote:
-snip-
Agreed, but a manually set MAC address is not *needed* on ANY platform.
EVERY nic has burned-in MAC that can be used.
You're assuming that the installer uses that information to set the MAC
address. I don't know
On 02/13/2009 07:35 PM, Alan Altmark wrote:
On Friday, 02/13/2009 at 01:15 EST, Mark Post mp...@novell.com
wrote:
On 2/13/2009 at 1:01 PM, Alan Altmark
alan_altm...@us.ibm.com wrote:
-snip-
Eh? The OSA (real or virtual) already has a MAC address. You
aren't required to ifconfig a MAC
ends
Thanks for any help.
__ Information from ESET NOD32 Antivirus, version of virus signature
database 3852 (20090213) __
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
On Friday, 02/13/2009 at 02:10 EST, Steffen Maier
ma...@linux.vnet.ibm.com wrote:
As far as I was told, certain versions of qeth device drivers required
the setting of a MAC address with real OSAs, because all virtual
machines would otherwise take the one MAC address of the OSA and would
end
We have installed a SLES 10 SP 2 with a layer=2 vswitch. One thing that I
noticed, but did not spend a great deal of time researching, is that once any
version of SLES is IPL'd, there are certain remnants in the system that prevent
it from IPL'ing clean a second time. We got around this by
Hmm, then I wonder why my SLES10 SP2 install is failing? I had no issues
installing until I switched to a LAYER2 vswitch. A logoff and logon of the
guest did not correct this problem.
On Fri, Feb 13, 2009 at 3:09 PM, Shedlock, George gshedl...@aegonusa.comwrote:
We have installed a SLES 10
FYI - adding a null value like this
OSAHWaddr=
or
OSAHWaddr=''
in the LINUX PARMLINE did not stop the prompt for MAC address
On Fri, Feb 13, 2009 at 12:46 PM, Mark Post mp...@novell.com wrote:
On 2/13/2009 at 12:38 PM, Jihad K Kawkabani
jihad_k_kawkab...@progressive.com
wrote:
I cross
On 2/13/2009 at 3:30 PM, Mark Pace mpac...@gmail.com wrote:
FYI - adding a null value like this
OSAHWaddr=
or
OSAHWaddr=''
in the LINUX PARMLINE did not stop the prompt for MAC address
Yes, it looks like you have to d a q nic and fill in the value. Sounds like
a job for Rexx and Xedit.
Speaking of SLES11... I was recently asked if I knew of any SLES11 Beta
testers for System z. I said I didn't, so I thought I'd ask if anyone out
there (aside from IBM folks) is testing. I don't know what confidentiality
requirements Novell puts on people doing that sort of testing, so
On 2/13/2009 at 10:41 AM, Mark Pace mpac...@gmail.com wrote:
-snip-
No LAYER2 support so I edit the file and add QETH_LAYER2_SUPPORT='1'
IPL from the boot disk and get the same problem.
Do you see the OSA activating during the boot process? This type stuff:
qeth: loading qeth S/390
Marcy
- Original Message -
From: Linux on 390 Port LINUX-390@VM.MARIST.EDU
To: LINUX-390@VM.MARIST.EDU LINUX-390@VM.MARIST.EDU
Sent: Fri Feb 13 14:50:12 2009
Subject: [LINUX-390] Any SLES11 Beta Testers Out There?
Speaking of SLES11... I was recently asked if I knew of any SLES11 Beta
When booting the ramdisk at install those messages are there. When booting
from the new created boot disk, no. Here is everthing relative to
networking at boot.
No qeth file only contained what was in the previous email.
cat /mnt/etc/sysconfig/hardware/hwcfg-bus-ccw-0.0.1d00
STARTMODE='auto'
Filling in the correct value
OSAHWaddr=02-00-85-00-00-09
Did satisfy the PARMLINE.
On Fri, Feb 13, 2009 at 3:46 PM, Mark Post mp...@novell.com wrote:
On 2/13/2009 at 3:30 PM, Mark Pace mpac...@gmail.com wrote:
FYI - adding a null value like this
OSAHWaddr=
or
OSAHWaddr=''
in the
I actualy did enter a bogus MAC address, but it did contain the correct MAC
Prefix, in the parm file and it did pick up the REAL assigned MAC Address
from VM, and the installation went on its merry way
Thanks all...
Regards,
Jihad K. Kawkabani
IT Systems Engineer Consultant
Voice:
On 2/13/09 2:06 PM, Steffen Maier ma...@linux.vnet.ibm.com wrote:
As far as I was told, certain versions of qeth device drivers required
the setting of a MAC address with real OSAs, because all virtual
machines would otherwise take the one MAC address of the OSA and would
end up talking with
Mark,
Speaking of SLES11... I was recently asked if I knew of any SLES11 Beta
testers for System z.
I said I didn't, so I thought I'd ask if anyone out there (aside from
IBM folks) is testing.
I wouldn't go as far as to say I'm (we're) testing, but we do have a copy
of RC3 installed.
We did
Hello, list,
I'm being laid off, so I was wondering if anyone knew of any openings.
I've been doing application development and support on z/OS UNIX for
the last 12 years and on x86 Linux (C/C++, Java, shell scripts, Rexx, ...)
and department-level x86 Linux sysadmin work the last eight years.
I
On 2/13/2009 at 4:02 PM, Mark Pace mpac...@gmail.com wrote:
When booting the ramdisk at install those messages are there. When booting
from the new created boot disk, no. Here is everthing relative to
networking at boot.
No qeth file only contained what was in the previous email.
cat
Hi ,
LLADDR=macaddr in the parmfile should be able to proceed with
installation
On Fri, Feb 13, 2009 at 10:38 AM, Tobias Doerkes tdoer...@hotmail.comwrote:
Hi list,
anyone out there using layer2 support during SLES10 autoinstall in
parmfile?
layer2=1 works fine so far, but the system
37 matches
Mail list logo
