Greetings; (Posted to VMESA-L and VSE-L and LINUX-390)
- - Now in its sixth year! - - Includes VSE and linux/390!
I have set up a public service web page at
http://www.eskimo.com/~wix/vm/
for posting positions available and wanted for VM, VSE and linux/390.
Please visit the web
On Wed, 22 Dec 2004 14:45:12 -0600, Adam Thornton
[EMAIL PROTECTED] wrote:
pull a number out of the air, about 15 largely-similar Linux guests,
it's probably worth at least taking a good hard look at.
The largely similar is the tough part. Once you agreed on what the
server should look like,
1. Test : zipl.conf without vmpoff=LOGOFF
shell command poweroff does not work for both, VM recognizes shutdown
of
GUEST2, but no logoff
2. Test : zipl.conf with vmpoff=LOGOFF
shell command poweroff works for both, VM recognizes shutdown of
GUEST2,
but no logoff
The guest were running
On Thu, 23 Dec 2004 08:29:33 -0500, Daniel Jarboe
[EMAIL PROTECTED] wrote:
shell command poweroff does not work for both, VM recognizes shutdown
You are getting things confused. The poweroff command does need the
vmpoff= option. If you put LOGOFF there it will issue that command
whether you're
To Tobias: It sounds like you did not install the Linux patch Peter
Oberparleiter described in his post of 13 December. (
http://www10.software.ibm.com/developerworks/opensource/linux390/linux-2.4.21-s390-07-june2003.shtml
)
Did you? That patch includes a change to the way Linux quiesces
Last question I hope. I've since created an /etc/zfcp.conf file with the
following.
0xa210 0x1:0x5005076300d08276 0x0:0x502f
0xa310 0x1:0x5005076300c28276 0x0:0x502f
I ran mk_initrd and zipl. Upon reboot a I noticed the following in the
logs,
sd:
YOu went wrong on the zfcp.conf configuration. you will notice that where you
put in the 0x1: you need to have a 0x01 and where you put in the LUN # of 0x0:
you need to have 0x00:, it is very picky. If you have one thing wrong it won't
work.
-Cameron
-Original Message-
From: Linux on
Doug,
The primary concern for running Domino in a 1-way configuraiton
is to avoid a background or mgmt Domino task from taking over the
system. The thought being that a second processor allows one to allow
other work to run. Depending on the heaviness of your Domino users,
you maybe be able to run
can you post the dmesg output please.
-Cameron
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Wiggins, Mark
Sent: Thursday, December 23, 2004 09:33
To: LINUX-390@VM.MARIST.EDU
Subject: Re: FCP question
Still getting same error. Changed to
0xa210
Hi Michael,
I'm not aware of any changes in the qeth driver that would have affected
the HiperSockets initialization (but I'm no expert on the Linux
implementation). It sounds like you are keeping your Linux users
up-to-date. What level of CP are you running (and what Guest LAN
maintenance
Guys,
I've a very big problem!!! I'm configured a VLAN into
my Linux System (SLES8 64 bit). After that...
Someone close the tcpip stack running on a z/OS
sharing the same device address.
After that, my address and the address of the z/OS is
unreachable!!!
We was able to solve only after a Power
On Thursday, 12/23/2004 at 06:47 CET, Max [EMAIL PROTECTED] wrote:
Guys,
I've a very big problem!!! I'm configured a VLAN into
my Linux System (SLES8 64 bit). After that...
Someone close the tcpip stack running on a z/OS
sharing the same device address.
After that, my address and the address
Hi all,
i know that the vmpoff=LOGOFF is not relevant for poweroff , but there was a
suggestion to give it a try. And so i tried.
But to answer the question regarding the patch: No, i did not try the patch,
because we are running a test and do not have the possibility to retrieve an
update (we are
Here's what I think is the pertinent information
Here's my current zfcp.conf file
0xa210 0x01:0x5005076300d08276 0x00:0x502f
0xa310 0x01:0x5005076300c28276 0x00:0x502f
And here's the dmesg,
debug: qdio_trace: new level 2
zfcp: zfcp_module_init: driver version 0x3003c
On Thu, 23 Dec 2004 14:40:17 -0500, Romanowski, John (OFT)
[EMAIL PROTECTED] wrote:
This works whether the guest is running connected or disconnected.
You're not sure about that are you? I am pretty sure I tried it...
--
Rob van der Heij rvdheij @ gmail.com
On Thu, 23 Dec 2004 20:44:12 +0100, Rob van der Heij [EMAIL PROTECTED] wrote:
This works whether the guest is running connected or disconnected.
You're not sure about that are you? I am pretty sure I tried it...
Ok, my mistake. When you 'signal shutdown' the guest CP will only
logoff the
Ok, I guess I'll say never mind... I was just talking to one of the
Linux guys and told me that it looked to him as though LVM played an
important role in all of this. I went through the process of creating an
LVM vol and it looks as though that worked. Anyway, thank you (Cameron
Seader) for your
yes LVM does play a role in all of this, have you read the Redbook on FCP
configuration.
-Cameron
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Wiggins, Mark
Sent: Thursday, December 23, 2004 13:17
To: LINUX-390@VM.MARIST.EDU
Subject: Re: FCP question
I'm not aware of any changes in the qeth driver that would have affected
the HiperSockets initialization (but I'm no expert on the Linux
implementation). It sounds like you are keeping your Linux users
up-to-date. What level of CP are you running (and what Guest LAN
maintenance level is
19 matches
Mail list logo
