> > What I meant is that an idle CMS user has a very small > footprint and as VM > will bring in the resources when you press enter. Even logging on and > starting CMS does not take very long in most shops. > Oops, misunderstood. I gotcha now.
> > How about if your developer had a website where he could > request startup of > his Linux guest (probably secured with userid and password) ? Yepper, considered that approach and might still go that route. > If you really talk about developers who need to logon to a > Linux system, > would they care for a specific system? Could they not logon > to any of the > available systems and have their home directory mounted there? I was thinking more of guests running particular services, like Apache that a developer may need only in a blue moon. For every "Production" guest, we will have an (almost) exact "Test" guest. We just don't want to run them all the time. > I'm thinking you might be able to do with a Linux virtual router and > userland port forwarding that autologs the guest under the covers. > Now this is a thought. I hadn't considered Linux mananging it. I'll mull it over from this angle. Darn good idea. > Maybe we should discuss this on the Linux-VM mailing list > instead, that is > where most of the penguins hang out. > That'd be fine. I just figure it'd be VM that would handle the work. But, it might very well be "pure" Linux with a little VM behind the scenes as you mentioned. Consider it forwarded... Thanks for the ideas. Leland
