Since VDISKs is z/VM are implemented as FBA devices, it is not difficult
to write an app that can backup the contents of a Linux swap disk to a
CMS file and restore it back to a VDISK. Once in a CMS file, the swap
disk can be moved around to other user ids, sent across the Net, etc.
without much effort. SWAPGEN could be enhanced to provide this swap
space backup and restore function without a great deal of effort, I think.

A z/VM Linux guest user id might have several of these swap files
available on it's 191 CMS minidisk, allowing a user to select which
flavor of Linux they'd like resumed to meet their specific needs.

Have a good one.

On 12/08/2009 08:54 AM, Rob van der Heij wrote:
On Tue, Dec 8, 2009 at 2:55 PM, Alan Altmark<[email protected]>  wrote:
On Tuesday, 12/08/2009 at 05:28 EST, Rob van der Heij
<[email protected]>  wrote:

But the swap space already in use by the time you suspend must also be
retained. You could address that by "swapoff -a" before you suspend
but the ride gets more bumpy.

True, but for the purpose of freeze-drying a Linux image, the data could
be read from the VDISK after hibernate is complete and placed in cryogenic
suspension, to be reanimated at need.  (Lukewarm standby?)  If you're
looking for quick suspend-move-resume, then, as you suggest, you wait for
Live Guest Relocation and avoid the whole suspend/resume part of the
equation.  :-)

Oh, but if you don't plan to move your frozen penguins, then freeze
them into VDISK and let VM page out those VDISK pages when it makes
sense. Just hope the ice water does not cause SWAPGEN to wipe out the
VDISK (but the same applies to the swap on ECKD permafrost platters)

PS I fear that by Friday this analogy has gone way bad ;-)

--
Dave Jones
V/Soft
www.vsoft-software.com
Houston, TX
281.578.7544

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to