Ethan Quach wrote: > > Glenn Lagasse wrote: >>> In install_VM you show a loop that monitors state with regard to the >>> VM. If the VM is hung, what can we do here in terms of shutting down >>> the VM? >>> >> >> This is where the vm_timeout comes in. When the timeout expires, we'll >> forcibly shut down the vm and tell the user that vm creation failed. >> Though why it failed is going to be tricky to explain. >> > > So is this more like an overall "time limit" for the vm to finish? > 'timeout' to me has a connotation that something is being > measured from a point when no progress appears to be made -- > like a sleeping process or something. Is it possible to come up > with some heuristic, or state to measure from, for this timeout? > > > thanks, > -ethan > > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
I've had off-line discussions with various members of the team regarding the VMC "time limit" and user notification of installation progress. The summary is: VMC will not implement a "MAX Run" timer. Instead VMC will enables ssh access to the VBox client doing the VMC install and we will document how the user can log in from the VBox host and monitor the installation. This would be a lot like the AI experience with SSH enabled. Joe
