Don, good point on the MAC address reset. I learned about Virtual Box's "Export/Import" functions at ByteWORKS, where we used them on our fleet of classroom machines.
In the past I just moved the .vdi files too ... and in one instance (funnily enough, it was also a Win2K machine) I ran into the same problem Tim did. Theresa On Fri, 2010-09-03 at 13:40 -0500, Don Ellis wrote: > Thanks, Theresa. I was going to suggest that, but you got to it first! > I have had the same experience, and Export/Import just seems so > tedious and complicated. But, it's the only thing that works. > > Another item: If an imported appliance is going to be on the same > network, and running at the same time, it would be good to reset the > MAC address for that new instance. Seems like that should be > automatic, but it isn't. > > --Don Ellis > > > On Wed, Sep 1, 2010 at 11:34 AM, Theresa Kehoe <[email protected]> wrote: > > Tim, > > > > Does VirtualBox 3.0 have an option under the File menu to Export > > Appliance? (I'm running 3.2.x, which does) If it does, try exporting > > the working virtual box. Note it doesn't like to export to a network > > share, at least with Linux, so just export it to something like your > > desktop or your /home/Documents directory. Once it's exported (if I > > recall correctly, it creates a total of three files), then you can copy > > all those files to your new machine. From the new machine, you then > > select File/Import Appliance from VirtualBox. > > > > Of course, this is assuming that VirtualBox 3.0 HAS the Export/Import > > Appliance functionality. > > > > Theresa > > > > > > On Tue, 2010-08-31 at 21:37 -0500, Tim Beckendorf wrote: > >> Greetings, > >> > >> I have a .vdi file created in VirtualBox 3.0 on Ubuntu 8.04. I would > >> like to use the file on a new machine but have run into some > >> difficulties. I released the file from the host on the original machine, > >> then I copied it to the new machine in the proper directory. I attached > >> it to the newly created operating system (windows 2000) but now when I > >> try to boot it, I get the windows blue screen with the message > >> "INACCESSIBLE_BOOT_DEVICE". The file works on the original machine, so > >> what can I do to allow it to work properly on the new machine? > >> > >> Tim > >> > -- Central West End Linux Users Group (via Google Groups) Main page: http://www.cwelug.org To post: [email protected] To subscribe: [email protected] To unsubscribe: [email protected] More options: http://groups.google.com/group/cwelug
