on its way. hopefully openable! thank you!
-Original Message-
From: Linux on 390 Port On Behalf Of Mark Post
Sent: Tuesday, June 11, 2019 10:09 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Devices for dracut in sles 12 SP4
On 6/11/19 1:05 PM, Marcy Cortes wrote:
> If you
On 6/11/19 1:05 PM, Marcy Cortes wrote:
> If you can't, I can email you a copy.
Please, do.
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message:
Maybe its not the cio-ignore stuff.
I just posted the whole long rescue/dracut console to the ticket.
Can you look at it ? If you can't, I can email you a copy.
-Original Message-
From: Linux on 390 Port On Behalf Of Mark Post
Sent: Tuesday, June 11, 2019 8:24 AM
To:
On 6/11/19 11:51 AM, Cohen, Sam wrote:
> I'm going to ask a religious questionif you're running under z/VM and
> (ideally) giving the virtual machine only what it needs, why would you use
> cio_ignore at all?
That's exactly why Ihno and I successfully lobbied to get the default
changed for
I'm going to ask a religious questionif you're running under z/VM and
(ideally) giving the virtual machine only what it needs, why would you use
cio_ignore at all?
Thanks,
Sam
(217) 862-9227 (office)
(602) 327-2134 (cell)
-Original Message-
From: Linux on 390 Port On Behalf Of
On 6/10/19 3:52 PM, Marcy Cortes wrote:
> Does anyone know how dracut is really supposed to be told about devices? I
> was under the impression that all devices were allowed unless explicity in a
> cio_ignore when running under z/VM.
That's been the default for new installations on z/VM for a
Hi,
It's never too early to volunteer to chair a session or two+. If you are
going to SHARE, and would like to help out your peers by volunteering to
chair sessions, please review the list below. If oyu have an open time slot
that aligns with session(s), or are planning to attend these, please
On Mon, 10 Jun 2019 17:47:20 +
Mark Bullis wrote:
> We attempted to upgrade 4 SUSE linux z/VM 6.4 guests this last weekend and 2
> of them failed with
>
> {FAILED] Failed to start Load Kernel Modules
>
> Many Out of Memory messages
>
> Kernel panic - not syncing: Out of memory and no
