On Wed, Nov 18, 2009 at 3:47 AM, Alexey Eremenko <[email protected]> wrote: > On Wed, Nov 18, 2009 at 10:42 AM, Geoff Galitz <[email protected]> wrote: >> >>> > Seriously - doing this would defeat the whole purpose of >>> > virtualization. >> >> Not necessarily. Sometimes the purpose of virtualization is integration >> rather than segregation. My primary workstation is Vista Business with an >> Ubuntu 9.04 VM running in windowless mode with a shared folder for my source >> code and documents. >> >> This allows me to use to my favored tools in both environments with little >> overhead. Speaking directly to the original question, I use TortoiseSVN on >> the Vista side to manage my code and test client connectivity and then I use >> the Ubuntu side to compile it and build the documentation via hyperlatex. >> This is all done with a single shared folder that points to my source code. >> >> Adding SSH or some other remote access tool and you can indeed run commands >> on the host. >> > > I think the other way around should have less potential security risks. > The is manage guests from host. > > See: > http://www.virtualbox.org/ticket/893 > > What do you think ? > -- > -"Technologov" >
I'm interested in this discussion so I'm piping in... It seems to me that the solution in 893 is only partially interesting. I can definitely see the scripting advantages to the 893 solution and I definitely think its worth the time to implement. With networking enabled vrdp and a host of other technologies are available and my problem/exception isn't interesting any more. Using the proposed guest exec function I can do anything I need to do, edit network configuration files, start services, etc. The only thing I can't do efficiently is debug scripts designed to automate these tasks. I think it would be cool to open a dumb terminal window into the guest os on the host and then be able to be interactive with the guest till I have a chance to debug my scripts and make sure they do what they need to do. Then I can automate whatever and let it go. This should be a reasonably straight forward task for all the *nixes (including the BSDs) But when the Guest OS is Windows I doubt something like this would work. If the host is also Windows not having this terminal is not such a big deal Windows has the winrm.cmd tool designed to remotely manage headless servers but it requires networking to function and wouldnt be available on a linux host. Just my $0.02 Rance _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
