Alexey Eremenko wrote: >> Hi, >> Sorry if this has been covered before but I couldn't see anything in >> the archives or the user manual. My first attempt to port a virtual >> machine from one Linux host to another by tarring up the contents of >> .VirtualBox and copying the resulting tar file across and untarring it >> was successful but are there any gotchas I should be aware of? Is this >> the way to do it or are there better ways? Is this supported at all? >> >> I'm looking at this as a means of providing access to Microsoft Office >> for staff members who prefer to have a Linux desktop machine. Wine >> doesn't seem to work, CrossOver Linux works but costs (and Access >> doesn't work at the moment) but I'm really impressed by the usability >> and speed of VirtualBox. Is there any other way of doing this that >> I've overlooked? > > Hi Mark > > Actually it is dead easy. Just copy your Virtual Hard Disk from one > physical computer to another. It has a .vdi extension so search for ( > *.vdi ) files on your system, and copy Windows XP.vdi to all computers > that you want Windows running on. > > Generally there should be no major problems. > > There could be small problems: > > a) saved state will get lost (so shutdown properly, before you copy) > b) Don't install software that requires specific CPU instructions, > such as SSE. (as not all computers have it) > c) Recommended: Install MS Office before you copy the vdi files. > d) your MAC address will change, but that's not big deal. > > On the target machine, re-create the VM from scratch, and use the > copied vdi file as Hard Disk.
Alexey, Thanks for this. I hadn't thought about creating the VM from scratch but it seems a cleaner way of doing things rather than copying a whole .VirtualBox directory structure. -- Mark Whidby Faculty of Engineering and Physical Sciences _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
