Do you have the cpu hotplug daemon running?  Run "/etc/init.d/cpuplugd
status" to check.  It will vary on and off cpus automatically.  You
can turn it off with "/etc/init.d/cpuplugd stop" and "chkconfig
cpuplugd off" to not start it at boot time.

On Fri, Aug 27, 2010 at 10:11 AM, Victor Echavarry Diaz
<[email protected]> wrote:
> We have guest with two cpu's. A couple of days ago after create new guest 
> with 2 cpu's, the second CPU put the guest in cp mode and the system become 
> slow and sometimes hangs the system. This is some info about what is happen.
>
> VM directory
> PROFILE LINUXPRF
>    IPL CMS PARM AUTOCR
>    OPTION QUICKDSP
>    MACHINE XA 2
>  *  MACHINE ESA 2
>    COMMAND SET VCONFIG MODE LINUX
>    COMMAND DEFINE CPU 0 TYPE IFL
>  *  COMMAND DEFINE CPU 1 TYPE IFL
>  *  CPU 0
>  *  CPU 1
>
>
> USER L20BP L20BP 2048M 2048M G
>  INCLUDE LINUXPRF
> *CPU 1
>  COMMAND DEFINE CPU 1 TYPE IFL
> *
>
> l20bp:~ # vmcp q virtual cpus
> vmcp q virtual cpus
> CPU 00  ID  FF01CF8C20978000 (BASE) IFL  CPUAFF ON
> l20bp:~ # vmcp define cpu 1
> vmcp define cpu 1
> CPU 01 defined
> l20bp:~ # vmcp q virtual cpus
> vmcp q virtual cpus
> CPU 00  ID  FF01CF8C20978000 (BASE) IFL  CPUAFF ON
> CPU 01  ID  FF01CF8C20978000 STOPPED IFL  CPUAFF ON
> l20bp:~ #
> vmcp begin cpu 1
> vmcp begin cpu 1
> 01: HCPGIR453W CP entered; program interrupt loop
> l20bp:~ #
> vmcp q virtual cpus
> vmcp q virtual cpus
> CPU 00  ID  FF01CF8C20978000 (BASE) IFL  CPUAFF ON
> CPU 01  ID  FF01CF8C20978000 IFL  CPUAFF ON
> l20bp:~ #
>
> IPL the system.
>
> LOGON L20BP
>  ICH70001I L20BP    LAST ACCESS AT 09:42:49 ON FRIDAY, AUGUST 27, 201
> HCPLGN196I Secondary user not in CP directory
> NIC 0340 is created; devices 0340-0342 defined
> NIC 0360 is created; devices 0360-0362 defined
> z/VM Version 5 Release 4.0, Service Level 1001 (64-bit),
> built on IBM Virtualization Technology
> There is no logmsg data
> FILES:   NO RDR,   NO PRT,   NO PUN
> LOGON AT 09:46:15 EDT FRIDAY 08/27/10
> MODE = LINUX
> HCPCPU1453E CPU 00 is not defined because it already exists.
> 00: CPU 01 defined
> z/VM V5.4.0    2010-02-22 09:43
> 00: Please choose (default will boot in 10 seconds):
> 00: Booting default (ipl)...
> Linux version 2.6.16.60-0.21-default (ge...@buildhost) (gcc version 4.1.2 
> 200701
> 15 (SUSE Linux)) #1 SMP Tue May 6 12:41:02 UTC 2008
> We are running under VM (64 bit mode)
> Detected 2 CPU's
> Boot cpu address  0
> Built 1 zonelists
>
> Kernel command line: root=/dev/dasdb1   TERM=dumb BOOT_IMAGE=0
> PID hash table entries: 4096 (order: 12, 131072 bytes)
> Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
> Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
> Memory: 2043904k/2097152k available (4671k kernel code, 0k reserved, 2089k 
> data,
>  212k init)
> Security Framework v1.0.0 initialized
> .
> .
> .
> Mount-cache hash table entries: 256
> checking if image is initramfs... it is
> Freeing initrd memory: 3311k freed
> cpu 0 phys_idx=0 vers=FF ident=01CF8C machine=2097 unused=8000
> cpu 1 phys_idx=1 vers=FF ident=01CF8C machine=2097 unused=8000
> Brought up 2 CPUs
> migration_cost=1000
> NET: Registered protocol family 16
>
> After IPL
> l20bp:~ # vmcp q virtual cpus
> CPU 00  ID  FF01CF8C20978000 (BASE) IFL  CPUAFF ON
> CPU 01  ID  FF01CF8C20978000 IFL  CPUAFF ON
>
> 20bp login: 01: HCPGSP2629I The virtual machine is placed in CP mode due to a 
> S
> IGP stop from
>  CPU 01.
> Processor 1 spun down
> Aug 27 09:50:31 l20bp kernel: Processor 1 spun down
>
>
> l20bp:~ # vmcp q virtual cpus
> CPU 00  ID  FF01CF8C20978000 (BASE) IFL  CPUAFF ON
> CPU 01  ID  FF01CF8C20978000 IFL  CPUAFF ON
> l20bp:~ # vmcp q virtual cpus
> CPU 00  ID  FF01CF8C20978000 (BASE) IFL  CPUAFF ON
> CPU 01  ID  FF01CF8C20978000 STOPPED IFL  CPUAFF ON
> You have new mail in /var/mail/root
>
> ZIPL.conf
>
> # Modified by YaST2. Last modification on Mon Feb  8 15:54:33 UTC 2010
> [defaultboot]
> defaultmenu = menu
>
>
> :menu
>    default = 1
>    prompt = 1
>    target = /boot/zipl
>    timeout = 10
>    1 = ipl
>    2 = Failsafe
>
> ###Don't change this comment - YaST2 identifier: Original name: ipl###
> [ipl]
>    image = /boot/image
>    target = /boot/zipl
>    ramdisk = /boot/initrd,0x1000000
>    parameters = "root=/dev/dasdb1   TERM=dumb possible_cpus=4"
>
> ###Don't change this comment - YaST2 identifier: Original name: failsafe###
>
> Does anybody know what this is happen. On VM the processor looks ok.
>
> Regards,
>
> Víctor Echavarry
> System Programmer
> Technology Systems & Operations Division
> EVERTEC
>
>
>
>
>
>
>
> -----------------------------------------
> CONFIDENTIALITY NOTE: This email communication and its attachments
> contain information that are proprietary and confidential to
> EVERTEC, INC., its affiliates or its clients.  They may not be
> disclosed, distributed, used, copied or modified in any way without
> EVERTEC, Inc.’s authorization. If you are not the intended
> recipient of this email, you are not an authorized person.  Please
> delete it and notify the sender immediately. EVERTEC, Inc. and its
> affiliates do not assume any liability for damages resulting from
> emails that have been sent or altered without their consent.
> Moreover, EVERTEC, Inc. has taken precautions to safeguard its
> email communications, but cannot assure that such is the case and
> disclaim any responsibility attributable thereto.
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [email protected] 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/
>



-- 
Bruce Hayden
z/VM and Linux on System z ATS
IBM, Endicott, NY

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] 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/

Reply via email to