Didn't thought about that!
Thanks again.
Roberto.
El dom., 25 de ago. de 2019 a la(s) 11:49, Mark Post (mp...@suse.com)
escribió:
> On 8/25/19 2:04 AM, Roberto Ibarra Magdaleno wrote:
> > To bad that this shop doesn't have SUSE.
>
> Go to https://scc.suse.com/ and create a no-cost account. Then
On 8/25/19 2:04 AM, Roberto Ibarra Magdaleno wrote:
> To bad that this shop doesn't have SUSE.
Go to https://scc.suse.com/ and create a no-cost account. Then go to
https://download.suse.com/Download?buildid=xbuTZMVIYxE~ and sign in with
that account to download SLES15 SP1 for Z. Use the rescue
Hello Mark,
Thanks a lot, you have been a great help. I did took out the cio_ignore
parameter but the rescue system, strictly speaking, never jumped out. About
the !, as I told you it didn't work, but funny that in the zipl.conf file
it do was an ! an it has no problem!
To bad that this shop
Hello Steffen,
You have been a major help! It worked finally, not as documented but here
it goes how step by step:
1. Created a RESCUE PRM file in MDISK 191:
root=/dev/ram0 ro ip=off ramdisk_size=4
repo=ftp://172.27.20.33
CMSDASD=191 CMSCONFFILE=redhat.conf
2. The REDHAT
On 8/21/19 6:50 PM, Roberto Ibarra Magdaleno wrote:
> Hello Mark,
>
-snip-
> I’m not familiar with RH configuration files either, sincerely? I prefer
> SUSE =]
In that case, IPL a SUSE installation kernel and initrd and use the
rescue system from there. Or, if you have a currently running SUSE
Hi Roberto,
On 8/22/19 12:34 AM, Roberto Ibarra Magdaleno wrote:
Tried this configuration:
root=/dev/ram0 ro ip=off ramdisk_size=4
rescue
and still booting installer, not a rescue system:
Starting sshd to allow login over the
network.
Connect now to 172.27.20.19 and log in as user
Hello Mark,
> I'm hoping that right bracket is a typo, since it should be an
>exclamation point.
That “]” is what the system translated when I transferred de .RPM file from
the ISO. Changed to “!” and the VM didn’t IPLed the installer (from the
reader with the rescue.exec).
>As Steffen
Hello Steffen,
Tried this configuration:
root=/dev/ram0 ro ip=off ramdisk_size=4
rescue
and still booting installer, not a rescue system:
…
Starting sshd to allow login over the
network.
Connect now to 172.27.20.19 and log in as user install to start the
installation
.
E.g. using: ssh
On 8/20/19 7:20 PM, Roberto Ibarra Magdaleno wrote:
> Hello everyone again, Mark,
>
>
> I tried to IPL in rescue mode by doing these 2 configuration files:
>
> RESCUE PRM A1
>
> root=/dev/ram0 ro ip=off ramdisk_size=4 cio_ignore=all,]0.0.0009
I'm hoping that right bracket is a
Hi Roberto,
On 8/21/19 1:20 AM, Roberto Ibarra Magdaleno wrote:
I tried to IPL in rescue mode by doing these 2 configuration files:
RESCUE PRM A1
root=/dev/ram0 ro ip=off ramdisk_size=4 cio_ignore=all,]0.0.0009
inst.rescue
This looks like upstream (and RHEL7 or RHEL8) syntax
Hello everyone again, Mark,
I tried to IPL in rescue mode by doing these 2 configuration files:
RESCUE PRM A1
root=/dev/ram0 ro ip=off ramdisk_size=4 cio_ignore=all,]0.0.0009
inst.rescue
CMSDASD=191 CMSCONFFILE=redhat.conf
REDHAT CONF A1
DASD="200-206"
HOSTNAME="linux8"
Hello Mark,
Tried adding the DASDs in the IPL command, same result:
*CP I 200 PARM RD_DASD=0.0.0205
RD_DASD=0.0.0206 *
zIPL v1.8.2-28.el6 interactive boot
menu
0. default
(linux)
1.
linux
Note: VM users please use 'Ñcp vi vmsg
'
Please choose (default
Roberto:
There are two things you can try:
The right way is to boot the system off CD, mount all the devices, do a chroot
to your disks, fix /etc/zipl.conf, do "mkinitrd ; zipl", and then shut
everything down. Suse describes it in detail at
https://www.suse.com/support/kb/doc/?id=7018376
Yes, but it doesn’t help when you don’t have another user ID at your
disposal or don’t have the privileges.
(In 2019, one should remove SET SECUSER and SET OBSERVER from class G to
prevent a user from giving his or her console to another ID.)
Regards,
Alan Altmark
IBM
> On Aug 16, 2019, at
True, but I left it so the user could specify VMSG or PVMSG. I also missed the
SEND CP rather than just SEND in the 1st instance.
On 8/16/19, 13:27, "Linux on 390 Port on behalf of Michael Harding"
wrote:
A little more complicated...
I think you want 'VINPUT VMSG'
Then, if your
A little more complicated...
I think you want 'VINPUT VMSG'
Then, if your guest has a directory console statement so it has other than
SYSC, you get: "HCPPCX6531E The operating system will not accept commands
from the service processor." Of course in that case a simple send works but
you still
Correction:
/* */
parse arg Target Command
upper Target
CPRc = DIAGRC(8,'SEND CP' Target 'VINPUT' Command)
parse var CPRC Rc Message
if (Rc <> 0) then
say Message
exit Rc
--
For LINUX-390 subscribe / signoff / archive
On 8/16/19 9:32 AM, Dan Horák wrote:
> I think the kernel cmdline parameters are case sensitive, so using
> something like
> #cp vi vmsg 1 rd_DASD=210 rd_DASD=211
> on the console to manually select the boot entry might fix the problem
It's might easier and less guess-intensive if you put that
In the interim a simple REXX program? (Assuming you have a SECUSER or a
privileged user)
/* */
parse arg Target Command
upper Target
CPRc = DIAGRC(8,'SEND' Target 'VINPUT' Command)
parse var CPRC Rc Message
if (Rc <> 0) then
say Message
exit Rc
On 8/16/19, 12:47, "Linux on 390 Port on
Alan wrote:
>I've been thinking for some time that we might want to consider revisiting
>that for the VINPUT command. It's a command specifically designed to
>deliver data to a guest, not CP and not someone else's console. As such,
>it should be left to the guest to do the translation if it
On Friday, 08/16/2019 at 01:55 GMT, "Dan Horák" wrote:
> On Fri, 16 Aug 2019 08:38:20 -0500
> Roberto Ibarra Magdaleno wrote:
>
> > Hi Dan,
> >
> > Tried that mixed case from the VM session console but it convert it to
> > upper case.
> > Suggestion?
>
> hm, maybe the upper-casing is a feature
On Fri, 16 Aug 2019 08:38:20 -0500
Roberto Ibarra Magdaleno wrote:
> Hi Dan,
>
> Tried that mixed case from the VM session console but it convert it to
> upper case.
> Suggestion?
hm, maybe the upper-casing is a feature of your session console, but I
would give a try DASD= instead of rd_DASD=.
Hi Dan,
Tried that mixed case from the VM session console but it convert it to
upper case.
Suggestion?
Regards.
Roberto.
On Fri, 16 Aug 2019, 08:32 Dan Horák, wrote:
> On Thu, 15 Aug 2019 20:48:17 -0500
> Roberto Ibarra Magdaleno wrote:
>
> > Hello all,
> >
> > I defined 2 new z/VM 6.2.0
On Thu, 15 Aug 2019 20:48:17 -0500
Roberto Ibarra Magdaleno wrote:
> Hello all,
>
> I defined 2 new z/VM 6.2.0 minidisks for a RHEL 6.0 VM to grow / FS,
> everything went right except I forgot to Persistently Setting DASDs
> Online with /etc/zipl.conf and zipl. Got "Refusing activation of
>
Not sure if it is in RHEL 6.0, but look at /etc/dasd.conf file putting your
device address' in this file we allow them to be online and available at IPL
time
Larry Davis
-Original Message-
From: Linux on 390 Port On Behalf Of Roberto Ibarra
Magdaleno
Sent: Thursday, August 15, 2019
Hello all,
I defined 2 new z/VM 6.2.0 minidisks for a RHEL 6.0 VM to grow / FS,
everything went right except I forgot to Persistently Setting DASDs Online
with /etc/zipl.conf and zipl. Got "Refusing activation of partial LV
lv_root. Use --partial to override." in next IPL. Since the kernel is not
26 matches
Mail list logo
