On Friday, 04/07/2006 at 10:30 AST, David Kreuter <[EMAIL PROTECTED]> wrote: > Seems to me CP already has most of this code path anyway. The free > storage limit detection will stop a machine in its tracks after the > second violation. It puts the errant machine into CP READ stopped state. > In the distant past I made some presentations on this - I'll dig > around. How deep and true this stopped state is - don't know - but > likely its a reasonable stoppage.
Freezing a virtual machine is easy - just don't dispatch it. SET RUN OFF and go into CP READ. But the virtual machine's architectural state is pretty much irrelevant to the issue as it relates to backups. It's an application issue. You have to get an application to: - accept an external 'pause' signal - stop accepting new work - complete in-flight work - sync all disks - respond to the 'pause' with a 'ready' - wait for a 'resume' signal while still queuing incoming work (e.g. you can't stop the IP stack) With snapshot-like technologies, you can take a few liberties and shortcuts, but the app still has to know what's going on and cooperate. And sometimes, the only cooperatin' app I know is a shutdown app, if you know what I mean. Alan Altmark z/VM Development IBM Endicott ---------------------------------------------------------------------- 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
