vmcp cannot allocate memory

2017-10-18 Thread Michael MacIsaac
Hello list, We use vmcp extensively to issue CP commands. More and more I'm seeing this error: Error: Could not issue CP command: Cannot allocate memory I always use the --buffer=1M flag to be able to get the largest output. I've bumped up the VM size from 2 to 3 to 4GB, but still see it. We

Re: vmcp cannot allocate memory

2017-10-18 Thread Neale Ferguson
Fragmentation. Vmcp needs contiguous real storage. So if there is not a slab of 1MB in size hanging around then it will complain. On 10/18/17, 1:44 PM, "Linux on 390 Port on behalf of Michael MacIsaac" wrote: >Hello list, > >We use vmcp

Re: vmcp cannot allocate memory

2017-10-18 Thread Christian Borntraeger
Yes, this is memory fragmentation. Heiko recently did some changes that should improve the situation. This upstream change https://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git/commit/?h=features=cd4386a931b6310b05559d2e28efda04d30ab593 will change the allocation from below 2GB to

Re: vmcp cannot allocate memory

2017-10-18 Thread Neale Ferguson
An enhancement to DIAG 8 to use a buffer list like DIAG 250 does for disk I/O would circumvent the contiguous memory requirement. The Ry register already contains a flag byte that could be extended to indicate Rx+1 being a buffer list rather than the buffer. On 10/18/17, 2:13 PM, "Linux on 390

TERM=linux instead of TERM=dumb

2017-10-18 Thread Dell Harris
Hi, I'm trying to figure out why TERM is being set to linux instead of dumb on the GRUB_CMDLINE_LINUX_DEFAULT in the /etc/default/grub line of a system-z guest on install of SLES 12 SP2. TERM=dumb is set in the parmfile but after the install it's set to linux. Does anyone know of a way to

Re: TERM=linux instead of TERM=dumb

2017-10-18 Thread John Campbell
Well... Perhaps pawing through /etc/profile _might_ be edifying. You can cheat by: cd /etc find . -type f -print | while read F ; do grep TERM "${F}" && echo "${F}" ; done to find out where this can be getting set. It might even be somewhere under /etc/defaults but don't quote me on that.

Re: TERM=linux instead of TERM=dumb

2017-10-18 Thread Mark Post
>>> On 10/18/2017 at 04:51 PM, Dell Harris wrote: > Hi, > > I'm trying to figure out why TERM is being set to linux instead of dumb on > the GRUB_CMDLINE_LINUX_DEFAULT in the /etc/default/grub line of a system-z > guest on install of SLES 12 SP2. TERM=dumb is set in

Re: TERM=linux instead of TERM=dumb

2017-10-18 Thread Paul Flint
Greetings John Campbell and Dell Harris, I find that the output from the excellent line of bash provided below by Big John great entertainment. But before we disappear into troff (or sphinx :^), could I suggest a different approach if you are "man" enough... Try this: man term Much