Re: Other migration problems (was Unable to login with ssh)

2016-07-02 Thread Phil Tully 
One of the problems is parts of the proc filesystem populated by the hw can 
overlay memory since the hw response returns more data on a z13
Phil
Sent from my iPhone

> On Jul 2, 2016, at 4:31 PM, Alan Ackerman  wrote:
> 
> According to a presentation I saw at SHARE the problems include storage 
> overlays. I don't think you even want try it. 
> 
> Sent from my iPhone
> 
>> On Jun 29, 2016, at 4:20 PM, Grzegorz Powiedziuk  
>> wrote:
>> 
>> From what Alan and Mark said, I understand that not working ssh might have
>> been just a small result of bigger problem - data corruption. So
>> practically anything else might go wrong too.
>> Gregory
>> 
>> 2016-06-29 14:01 GMT-04:00 Duerbusch, Tom :
>> 
>>> I didn't want to hijack the original thread so
>>> 
>>> The conclusion on the original thread was that you need to be on a
>>> supported release of Suse when you go to a new z13.  This involved SSH and
>>> I assume crypto hardware.
>>> 
>>> We have been planing to go to a z13 this year.
>>> I've said that many times before as we are on a z890, and have planed to go
>>> to a z9, z10, z114, z12 and now z13.
>>> 
>>> We have SLES 9, SLES 10 and SLES 11 running.
>>> (After WAVV in 2011, I did manage to sunset our SLES 7 and SLES 8 guests)
>>> 
>>> I'm ok with not being able to use new features/functions that are on a
>>> z13/zVM 6, on the unsupported software, but I'm now concerned about what I
>>> might loose, or crash with the new hardware.
>>> 
>>> SSH isn't much of a problem, as there are so few people that actually log
>>> on to Linux or use SSH with Linux applications.
>>> 
>>> So, the question is:
>>> Is there any other problems that others have come across, when migrating
>>> unsupported SLES systems to a z13?
>>> 
>>> Thanks
>>> 
>>> Tom Duerbusch
>>> THD Consulting
>>> 
>>> --
>>> 
>>> --
>>> For LINUX-390 subscribe / signoff / archive access instructions,
>>> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
>>> visit
>>> http://www.marist.edu/htbin/wlvindex?LINUX-390
>>> --
>>> For more information on Linux on System z, visit
>>> http://wiki.linuxvm.org/
>> 
>> --
>> For LINUX-390 subscribe / signoff / archive access instructions,
>> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or 
>> visit
>> http://www.marist.edu/htbin/wlvindex?LINUX-390
>> --
>> For more information on Linux on System z, visit
>> http://wiki.linuxvm.org/
> 
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Other migration problems (was Unable to login with ssh)

2016-07-02 Thread Alan Ackerman 
According to a presentation I saw at SHARE the problems include storage 
overlays. I don't think you even want try it. 

Sent from my iPhone

> On Jun 29, 2016, at 4:20 PM, Grzegorz Powiedziuk  
> wrote:
> 
> From what Alan and Mark said, I understand that not working ssh might have
> been just a small result of bigger problem - data corruption. So
> practically anything else might go wrong too.
> Gregory
> 
> 2016-06-29 14:01 GMT-04:00 Duerbusch, Tom :
> 
>> I didn't want to hijack the original thread so
>> 
>> The conclusion on the original thread was that you need to be on a
>> supported release of Suse when you go to a new z13.  This involved SSH and
>> I assume crypto hardware.
>> 
>> We have been planing to go to a z13 this year.
>> I've said that many times before as we are on a z890, and have planed to go
>> to a z9, z10, z114, z12 and now z13.
>> 
>> We have SLES 9, SLES 10 and SLES 11 running.
>> (After WAVV in 2011, I did manage to sunset our SLES 7 and SLES 8 guests)
>> 
>> I'm ok with not being able to use new features/functions that are on a
>> z13/zVM 6, on the unsupported software, but I'm now concerned about what I
>> might loose, or crash with the new hardware.
>> 
>> SSH isn't much of a problem, as there are so few people that actually log
>> on to Linux or use SSH with Linux applications.
>> 
>> So, the question is:
>> Is there any other problems that others have come across, when migrating
>> unsupported SLES systems to a z13?
>> 
>> Thanks
>> 
>> Tom Duerbusch
>> THD Consulting
>> 
>> --
>> 
>> --
>> For LINUX-390 subscribe / signoff / archive access instructions,
>> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
>> visit
>> http://www.marist.edu/htbin/wlvindex?LINUX-390
>> --
>> For more information on Linux on System z, visit
>> http://wiki.linuxvm.org/
> 
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Other migration problems (was Unable to login with ssh)

2016-06-29 Thread Grzegorz Powiedziuk 
>From what Alan and Mark said, I understand that not working ssh might have
been just a small result of bigger problem - data corruption. So
practically anything else might go wrong too.
Gregory

2016-06-29 14:01 GMT-04:00 Duerbusch, Tom :

> I didn't want to hijack the original thread so
>
> The conclusion on the original thread was that you need to be on a
> supported release of Suse when you go to a new z13.  This involved SSH and
> I assume crypto hardware.
>
> We have been planing to go to a z13 this year.
> I've said that many times before as we are on a z890, and have planed to go
> to a z9, z10, z114, z12 and now z13.
>
> We have SLES 9, SLES 10 and SLES 11 running.
> (After WAVV in 2011, I did manage to sunset our SLES 7 and SLES 8 guests)
>
> I'm ok with not being able to use new features/functions that are on a
> z13/zVM 6, on the unsupported software, but I'm now concerned about what I
> might loose, or crash with the new hardware.
>
> SSH isn't much of a problem, as there are so few people that actually log
> on to Linux or use SSH with Linux applications.
>
> So, the question is:
> Is there any other problems that others have come across, when migrating
> unsupported SLES systems to a z13?
>
> Thanks
>
> Tom Duerbusch
> THD Consulting
>
> --
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Other migration problems (was Unable to login with ssh)

2016-06-29 Thread Duerbusch, Tom 
I didn't want to hijack the original thread so

The conclusion on the original thread was that you need to be on a
supported release of Suse when you go to a new z13.  This involved SSH and
I assume crypto hardware.

We have been planing to go to a z13 this year.
I've said that many times before as we are on a z890, and have planed to go
to a z9, z10, z114, z12 and now z13.

We have SLES 9, SLES 10 and SLES 11 running.
(After WAVV in 2011, I did manage to sunset our SLES 7 and SLES 8 guests)

I'm ok with not being able to use new features/functions that are on a
z13/zVM 6, on the unsupported software, but I'm now concerned about what I
might loose, or crash with the new hardware.

SSH isn't much of a problem, as there are so few people that actually log
on to Linux or use SSH with Linux applications.

So, the question is:
Is there any other problems that others have come across, when migrating
unsupported SLES systems to a z13?

Thanks

Tom Duerbusch
THD Consulting

--

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/