We are running the vlan with 2.4.7 kernel, and it works great. No problems yet. Be
aware, some SUSE distributions don't have the kernel patch to enable hiper sockets, so
check that before you
install. The 2n'd question is up for debate. I think it is a matter of preference,
which should be based on the stability/longevity of the comparative products.
Regards
John Gustavson
Enterprise Central Software Services (ECSS)
570 Washington Street - 2nd floor
New York, New York, 10080-6802
Telephone: 1-212-647-3793
Fax: 1-212-647-3321
Email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
-----Original Message-----
From: Eric Lawler [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 15, 2002 11:42 AM
To: [EMAIL PROTECTED]
Subject: Linux under VM + Toolsets.
Hi,
We currently have a limited development Linux set-up of 4 guest virtual
machines, running under Z/VM 3.1.0. We use a Suse 2.2.16 kernel /
OS/390
gateway IP stack machine with onward connection to Linux machines via
virtual ctcs which are a little unreliable when we have to re logon the
Linux guests.
I have 2 questions :-
1. For another project we are investigating if it would be beneficial
to
have a 2.4 kernel under Z/VM 4.2 and VM TCP/IP with hipersockets and
virtual
lan etc. Do current users of these mechanisms find they are reliable
and
perform well ? Or would IUCV be recommended for example ? Comments
would be
appreciated.
2. Do shops who run Linux in production generally use VM mainly as a
hypervisor and use a Linux toolset to control and manage the Linux
guests,
eg. alert processing if a guests fails, security, and dasd backups. Or
is a
VM toolset generally used, or even a mix ? We would appreciate some
brief
descriptions of how installations do this and what toolsets they use.
Thanks again in advance, Eric Lawler.
Eric Lawler,
Infrastructure Support (Platforms),
Barclays Enable,
Ground Floor (A7), Block 10, Radbroke Hall, WA16 9EU (M).
Phone: 7-2000-3729 (Internal)
+44 (0)1565 613729 (External)
Email: [EMAIL PROTECTED]
Internet communications are not secure and therefore the Barclays Group
does not accept legal responsibility for the contents of this message.
Although the Barclays Group operates anti-virus programmes, it does not
accept responsibility for any damage whatsoever that is caused by
viruses being passed. Any views or opinions presented are solely those
of the author and do not necessarily represent those of the Barclays
Group. Replies to this email may be monitored by the Barclays Group
for operational or business reasons.
