z/VM RedHat Virtual Machine Memory abend

Hi s390x Gurus I´m new to Linux on z and we are conducting a POC test of Linux Red Hat with Oracle running under z/VM 5.4 RSU 1003 and a z/10 BC model A00 (IFL Only). If linux virtual machine is defined with 64G in directory we got an abend during startup (see below). Doing some tests I found

Re: CMM

You might want to look at: http://www.vm.ibm.com/perf/reports/zvm/html/530cmm.htm It talks about the difference between VMRM-CMM and CMMA and briefly shows how they are turned on.. Scott Rohling On Wed, Apr 20, 2011 at 2:07 PM, Dean, David

Re: CMM

Did you try "Developer Works"? Tom Duerbusch THD Consulting >>> "Dean, David (I/S)" 4/20/2011 3:07 PM >>> Project 1. VDISK implemented complete Project 2. CMM Will someone recommend a BASIC how-to guide for CMM on zlinux. I have googled and found many docs saying how gr

Re: CMM

>>> On 4/20/2011 at 04:07 PM, "Dean, David (I/S)" wrote: > Will someone recommend a BASIC how-to guide for CMM on zlinux. I have > googled and found many docs saying how great it is, but not how to do it. > I do not want the vmrm piece to make my decisions (yet). I need to > implement so I ca

CMM

Project 1. VDISK implemented complete Project 2. CMM Will someone recommend a BASIC how-to guide for CMM on zlinux. I have googled and found many docs saying how great it is, but not how to do it. I do not want the vmrm piece to make my decisions (yet). I need to implemen

Problems using channel-attached 3270 terminal

(Sending here, in case anyone here can help as well) I have a couple of 3270-mode terminals locally attached via a 3174-21L on my z890 running Debian/Squeeze in an LPAR. According to the 3270 terminal driver documentation, I should be able to enter ctrl-C, ctrl-D, etc, using ^C or ^D. I can su

Re: vdisk

Yes, this is how we do here. We have SWAPGEN in the PROFILE EXEC of the guest or a common disk that all guests read and each time the guest is logged on the SWAP VDISKS are defined and allocated. Works like a charm! Thank You, Terry Martin Lockheed Martin CMS - CITIC 3300 Lord Baltimore Drive,

Re: vdisk

Yes - each vdisk is assigned to the guest.. anything done to it won't affect other guests.Not sure what you mean by fixed block definitions being the same .. they can be the same or different if what you mean is formatting? Scott Rohling On Wed, Apr 20, 2011 at 8:56 AM, Dean, David (I/S) wro

Re: vdisk

> Thanks to all for the information. Now that I have your attention, is > it ok for the fixed block definitions be the same for all users, i.e. > the vdisk definition (the memory address) lives within the user > definition, and not the entire zvm? Yes. The number is not a address, but a size in

Re: Multiple Network Interfaces on RHEL6

> For anyone interested, after finding a blurb on a blog saying basically > that multi-homing is not supported on RHEL6 except in a bonding config, WTF? That is totally false. If you have multiple interfaces, you must use explicit routing to determine what packets flow over what network interfa

Re: vdisk

> Since it's a fresh disk every time, you'd have to do the mkswap every > time > you log in, so my guess is that's why you'd need the mkswap and > subsequent > swapon in the boot.local. The vdisk wouldn't be formatted when you get > it at > each fresh logon. I'll point out that running SWAPGEN bef

Re: vdisk

Thanks, my concern was to be sure that the vdisk was assigned to the guest and won't affect the others, which you clarified. We have this same definition for all users. MDISK 203 FB-512 V-DISK 409600 MR READ WRITE MULTIPLE MDISK 204 FB-512 V-DISK 2097152 MR READ WRITE MULTIPLE If it weren't fo

Re: vdisk

If you have the MDISK statement in each directory entry, it will be unique for each virtual machine. If you have the MDISK statement in the PROFILE, it will be common for all virtual machines that use that PROFILE. (but still separate memory) On 04/20/2011 09:56 AM, Dean, David (I/S) wrote: T

Re: vdisk

To clarify.. the vdisk is specified in number of 512 byte blocks. CP manages where these virtual disks start/end in memory -- you don't need to be concerned about managing them, if this is what you meant.You may want to consider setting system/user limits though, to ensure you don't use up a

Re: vdisk

Thanks to all for the information. Now that I have your attention, is it ok for the fixed block definitions be the same for all users, i.e. the vdisk definition (the memory address) lives within the user definition, and not the entire zvm? Resetting one user will have no affect on others? ---

Re: vdisk

Yes, it come up on boot. BUT is a (from msdos' times) ram drive. Shut down the computer, lose the contents. Reboot your linux, lose the swap signature on drive... Ask google for a exec called SWAPGEN. I use it, works fine, really fine. Mauro http://mauro.limeiratem.com - registered Linux User: 294

Re: vdisk

Exactly - vdisk is in memory and will be lost if the guest is logged off -- so must be formatted for swap and mounted as swap by Linux when the guest is started.. Scott Rohling On Wed, Apr 20, 2011 at 8:15 AM, RPN01 wrote: > Since it's a fresh disk every time, you'd have to do the mkswap every

Re: vdisk

Thanks all. -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mauro Souza Sent: Wednesday, April 20, 2011 10:18 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: vdisk Yes, it come up on boot. BUT is a (from msdos' times) ram drive. Shut down the computer

Re: Multiple Network Interfaces on RHEL6

For anyone interested, after finding a blurb on a blog saying basically that multi-homing is not supported on RHEL6 except in a bonding config, we changed to virtual interfaces. eth0 is still eth0 but eth1 is now eth0:0 eth2 is now eth0:1 and so-forth. Thank you for the reply. eric On 04/19/2

Re: vdisk

Since it's a fresh disk every time, you'd have to do the mkswap every time you log in, so my guess is that's why you'd need the mkswap and subsequent swapon in the boot.local. The vdisk wouldn't be formatted when you get it at each fresh logon. -- Robert P. Nix Mayo Foundation.~.

Re: vdisk

Ok, we have it working. Defined it in User Directory, formatted it for swap, added it to fstab, and added it to boot.local -> mkswap and swapon. Why did I have to add it boot.local? why does it not act like a normal DASD drive and come on at boot? -Original Message- From: Linux on 39