Hello from Gregg C Levine This issue has me some what confused. I know from my own experience regarding Linux, and Intel based systems that the clock configuration is one of the strangest, and can cause confusion, among staff members, and even customers. How does Linux observe the behavior of the system clock when running under VM? Or even installed in an LPAR? Also could that be considered native mode? ------------------- Gregg C Levine [EMAIL PROTECTED] ------------------------------------------------------------ "The Force will be with you...Always." Obi-Wan Kenobi "Use the Force, Luke."� Obi-Wan Kenobi (This company dedicates this E-Mail to General Obi-Wan Kenobi ) (This company dedicates this E-Mail to Master Yoda )
> -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Jim Sibley > Sent: Wednesday, September 10, 2003 1:44 PM > To: [EMAIL PROTECTED] > Subject: Re: [LINUX-390] z/VM 4.3.0 VM63282 / Qdrop apar > > Ron wrote: > > >Have you found any improvement ticking the clock in > LPAR, > >and if there is a difference? Is that because of LPAR > or > >because of other things (e.g. number of virtual CPUs > >or whatever)? > > I have seen the improvement under VM with the clocking > stopped. I don't anyone here who has looked at the > LPAR case with the clocking stopped; its always been > on and no-one has complained, even the performance > people who buts large loads on the OSA cards. Its > doesn't seem to be a big deal under LPAR in that all > the attendant VM wakeup and paging for each EC is not > necessary. > > >PS It should be enough to set the sysctl.conf once > >unless > >you boot the same system one day in LPAR and the > other > >day in a virtual machine. > > I set the vm differences in boot.local for several > reasons. > > 1) I can have a standard build that I can give to > either an LPAR requestor or VM EC requestor. Any > differences are then determined at IPL time rather > than having to make modifications for each user. If > its native, all they get is a message from boot.local. > If its VM, they get the hertz time turned off and the > insmod of the extint module for shutdown notification. > I can then add things, such as the fix packs to a > single system, rather than having to put them on a VM > and an LPAR version. > > Operationally, I have about 20-30 Lpars (peak 45) and > about 30-50 EC machines (peak 250) at any give time > spread over 5 differenct CEC's with over 100 different > respacks of various releases (SuSE 7, SuSE7+SP1, > SuSE8, SuSE8+SP2, SuSE8+SP3 (in beta), RH 7.1, RH 7.2, > RHEL3 (in beta), and the SuSE systems come in both > 31bit and 64bit versions. Having a VM version and an > LPAR version would double my collection! > > 2) Some of my users do want to boot under VM and in > LPAR to compare performance. > > 3) Sometimes I have to physically isolate some of the > LPAR machines; only my build LPAR can access them. So > I have to be able to IPL my build machines in either > LPAR or as an EC, depending on what I have to work on > and repair. I would rather have a single build system > that will accomodate wither VM or Native rather than > having to have two build respacks. > > ===== > Jim Sibley > Implementor of Linux on zSeries in the beautiful Silicon Valley > > "Computer are useless.They can only give answers." Pablo Picasso > > __________________________________ > Do you Yahoo!? > Yahoo! SiteBuilder - Free, easy-to-use web site design software > http://sitebuilder.yahoo.com
