On Tue, Dec 8, 2009 at 6:16 AM, Alan Altmark <[email protected]> wrote: > On Monday, 12/07/2009 at 10:47 EST, Shane Ginnane <[email protected]> > wrote: > >> Hands up all those using vdisk for swap ... > > Set up a minidisk for another swap partition at a lower priority and > specify it on resume= so that that Linux writes itself to minidisk, not to > VDISK.
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. After looking at this a few years ago, my impression was that suspend / resume really is a "client thing" but most of us run "servers" instead.The fact that you need to IPL for a resume spoils the first few cases where I would see value for it. It might avoid disappointment if the developers would explain the usage scenario that led to the design and restrictions. My personal guess is that the motivation was a customer with many not-often-used Linux LPARs and not willing to use z/VM to manage it. And as a poor man's "dozing guest migration" you would run into all the other restrictions that affect you when z/VM would be able to do it. For most scenarios, performance will be a factor. Somehow my feeling is that a well-configured z/VM paging subsystem can do the job quicker than Linux. I'm also thinking that in many cases a shutdown and IPL is faster, cheaper and more reliable. But it really depends no what you want to do with it. Rob -- Rob van der Heij Velocity Software http://www.velocitysoftware.com/ ---------------------------------------------------------------------- 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
