Networking is where you are most likely to have to make changes. Involve your
network engineering team early and often. Don't get stuck using the ed editor
to make changes to networking files from the 3270 console after you've moved
the image to the new lpar.
Varying the disks off of LPAR 1 and then varying them on LPAR 2 makes the
assumption that both LPARs share the same DASD. This is often, but not
always the case. Do your two LPARs share the same DASD (and use the same
rdev's - which is almost always the case when they are shared)? If so,
On Friday, 02/25/2011 at 11:57 EST, David Boyes dbo...@sinenomine.net
wrote:
Does anyone have source code for LP3820?
If it's the same LP3820 that we have in IBM, the original was available
externally via the OS/2 Developer's Connection. When I'm next in my
office I'll check it out - I have
We do this quite often. We have 4 VM's and guests can be moved freely to
any of these LPARs. It depends if you need other DASD as well.
If you can share DASD then make sure the DASD is available on both VM's.
Shutdown (logoff) the guest in one LPAR and start it in the other LPAR.
The directory
On 2/26/2011 09:29, Berry van Sleeuwen wrote:
We do this quite often. We have 4 VM's and guests can be moved freely to
any of these LPARs. It depends if you need other DASD as well.
If you can share DASD then make sure the DASD is available on both VM's.
Shutdown (logoff) the guest in one LPAR
On Friday, 02/25/2011 at 10:55 EST, Michael Forte/Poughkeepsie/IBM@IBMUS
wrote:
Hi members of the outstanding z/VM community!
I need advice or a pointer to documentation (if available?
presentations,
official publications, Redbooks...) on how to move a Linux guest from
one z/VM
LPAR to
