David Boyes wrote:
Dave Jones said:
I seem to recall that a number of years ago an IBM-er (Romney White,
perhaps) suggested a "stun" capability for VM. This would allow you to
stun a guest, do something to the system (maybe even move the guest to
another, similarly configured system) and have it start back up where
it
left off. The problem, as I understand it, is that capturing all of
the
state information about a running guest is non-trivial.
Not only suggested, but actually implemented in VM SSI (back in the
VM/SP days). The SWITCH command would move a virtual machine within a
SSI cluster of machines. It took an immense number of CP mods to make
this work.
Yeah, it was a number of years ago, before I became as involved as I am
now with the VM community. I heard about it 2nd or 3rd hand.
Perry Ruiter and I took a look at this again in 2000, and pretty much
concluded that it would be unmaintainable to try to do this level of
modification again. Things have changed too much in CP to reuse the old
code, and the sysprog skills to implement it just don't exist any more.
That's a shame.....I think being able to do a guest "stun" would have
some serious benefits for h/a and d/r situations. Of course, given
enough time and money, anything is possible. ;-)
DJ
-- db
----------------------------------------------------------------------
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
----------------------------------------------------------------------
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
