Move Slackware guest from a Slackware hosted Virtualbox to Windows hosted Virtualbox?
I hope the title wasn't confusing. At our office we need to set up a webserver. Nothing fancy, it needs to run Apache with Owncloud so that we have full control over the data and backups that we've been using Dropbox to sync and make available to people at home or in the field. I have been asked to help, but the problem is that I have limited time available in the office to help the "default" IT guy at work get this going on windows which the target machine in the office runs, and winning people over to linux is just not happening. Setting up the server alone is above the pay grade of the office manager and in all honesty he has limited time in the office to figure it out too.
Our solution is likely to run Virtualbox on the machine in the office since it does nothing productive, yet has 6 cores and 12GB RAM. Since I have my own apache/owncloud setup at home and won't have any problems setting things up on Slackware I want to just install Slack in Vbox on my own Slack machine, get everything going, and just be able to copy the Slack.vdi over to to a thumb drive and copy it over to a Vbox installation on the Windows machine at work.
My question is: does that seem feasible? Are there any roadblocks that anyone sees to this working? Lets please avoid the obvious flames against running linux as the guest, etc. I already threw all that at them when they asked me to help, and telling the poor kid trying to get IIS and PHP going that it takes exactly 1 second to get apache running in Slackware only met with "but you'd be typing a bunch of commands." lol
As long as both VirtualBox installs use the same emulated hardware configurations and run the same VirtualBox software versions, you should be able to import the drive flawlessly.
Just create a new Slackware Linux virtual system, import the drive when asked, reset the hardware configuration to match the original install, and it should fire right up without incident. Everything in the system has to match the original system, but you can get away with tuning the system CPU cores, video RAM, remote access ports, shared folders, and system RAM, but that's it because the rest could cause instabilities.
|All times are GMT -5. The time now is 01:28 AM.|